> ## Documentation Index > Fetch the complete documentation index at: https://docs.stackone.com/llms.txt > Use this file to discover all available pages before exploring further. # Azure DevOps OAuth 2.0 (Microsoft Entra ID) connector profile – StackOne setup guide > Set up the OAuth 2.0 (Microsoft Entra ID) connector profile for Azure DevOps in StackOne. One-time admin setup required before your users can link Azure DevOps accounts via Hub. You need administrator access to your Microsoft Entra ID tenant (Azure Active Directory) to register applications and grant API permissions.
Select Actions to adjust the guide
Some actions may require additional configuration in the provider to be accessible. Choose the actions you need and the guide will be updated.
Action
Scope(s)
Loading actions...
Dynamic Guide URL
Scopes Selected

          

            
Separator

Register a Microsoft Entra ID application

Create an app registration in Microsoft Entra ID to enable OAuth 2.0 authentication with Azure DevOps.

Sign in to the Microsoft Entra admin center.

  • In the left sidebar, go to App registrations.
  • Click New registration.

Fill in the application details.

  • Enter a Name (e.g., StackOne Azure DevOps Integration).
  • Under Supported account types, select Accounts in any organizational directory (Any Microsoft Entra ID tenant - Multitenant).
  • Leave the Redirect URI blank for now — you'll configure it in the next step.
  • Click Register.

Add the StackOne OAuth callback URL so Microsoft Entra ID can return the authorization code to StackOne.

  • From your app's Overview page, select Authentication (Preview) from the left sidebar under Manage. If you are using the older UI, this may appear as Authentication.
  • Under Redirect URI configuration, click Add Redirect URI, then select Web.
  • Enter the StackOne OAuth callback URL: `https://api.stackone.com/connect/oauth2/azuredevops/callback`
  • Click Configure to save.
  • Note: If you are using the older UI, under Platform configurations click Add a platform, select Web, enter the URI above, and click Configure.
Enables actions: Add Build Tag, Add Membership, Add Pull Request Label, Add User Entitlement, Add Work Item Comment, Create Build Definition, Create Classification Node, Create Dashboard Widget, Create Environment, Create Feed, Create Or Update Wiki Page, Create Pipeline, Create Policy Configuration, Create Project, Create Pull Request, Create Pull Request Reviewer, Create Pull Request Status, Create Pull Request Thread, Create Push, Create Query, Create Release, Create Release Definition, Create Repository, Create Service Endpoint, Create Team, Create Variable Group, Create Wiki, Create Work Item, Delete Classification Node, Delete Environment, Delete Policy Configuration, Delete Project, Delete Pull Request Reviewer, Delete Query, Delete Repository, Delete Service Endpoint, Delete Team, Delete User Entitlement, Delete Variable Group, Delete Wiki, Delete Wiki Page, Delete Work Item, Delete Work Item Comment, Delete Work Item Tag, Download Attachment, Get Agent Pool, Get Backlog, Get Build, Get Build Changes, Get Build Definition, Get Build Log, Get Build Logs, Get Build Timeline, Get Build Work Items, Get Classification Nodes, Get Commit, Get Dashboard, Get Environment, Get Feed, Get Feed Permissions, Get Item, Get Iteration, Get Pipeline, Get Pipeline Artifact, Get Pipeline Log, Get Pipeline Run, Get Policy Configuration, Get Project, Get Project Properties, Get Pull Request, Get Pull Requests By Project, Get Query, Get Release, Get Repository, Get Service Endpoint, Get Team, Get Tree, Get User, Get User Entitlement, Get Variable Group, Get Wiki, Get Wiki Page, Get Work Item, Get Work Item Comment, Get Work Item Tag, Get Work Item Type, List Agent Pools, List Agents, List Approvals, List Backlogs, List Boards, List Branch Statistics, List Build Artifacts, List Build Definitions, List Build Tags, List Builds, List Commits, List Dashboards, List Deployments, List Environment Deployment Records, List Environments, List Feeds, List Fields, List Forks, List Groups, List Items, List Iteration Work Items, List Iterations, List Memberships, List Merge Bases, List Pipeline Logs, List Pipeline Runs, List Pipelines, List Policy Configurations, List Policy Evaluations, List Projects, List Pull Request Commits, List Pull Request Iterations, List Pull Request Labels, List Pull Request Reviewers, List Pull Request Statuses, List Pull Request Threads, List Pull Request Work Items, List Pull Requests, List Pushes, List Queries, List Refs, List Release Definitions, List Releases, List Repositories, List Service Endpoints, List Team Members, List Teams, List Test Plans, List Test Results, List Test Runs, List User Entitlements, List Users, List Variable Groups, List Widgets, List Wikis, List Work Item Comments, List Work Item Relation Types, List Work Item Revisions, List Work Item Tags, List Work Item Type Fields, List Work Item Types, List Work Item Updates, List Work Items By IDs, Preview Pipeline, Query Work Items (WIQL), Queue Build, Run Pipeline, Search Code, Search Queries, Search Work Items, Set Feed Permissions, Set Project Properties, Update Approval, Update Classification Node, Update Environment, Update Feed, Update Policy Configuration, Update Project, Update Pull Request, Update Pull Request Reviewer, Update Pull Request Thread, Update Query, Update Refs, Update Repository, Update Team, Update User Entitlement, Update Variable Group, Update Wiki, Update Work Item, Update Work Item Comment, Update Work Item Tag, Upload Attachment

Grant the application access to Azure DevOps APIs.

  • In your app, click API permissions in the left sidebar.
  • Click Add a permission.
  • Select Azure DevOps from the list of APIs.
  • Select Delegated permissions.
  • Select the required scopes for your use case.
  • Click Grant admin consent for \[Your Organization] to authorize these permissions across the tenant.

Generate a client secret for authentication.

  • Click Certificates & secrets in the left sidebar.
  • Click New client secret.
  • Enter a description and select an expiration period.
  • Click Add.
  • Copy the Value immediately and store securely — it is only shown once.

Collect the required credentials from the app overview.

  • Click Overview in the left sidebar.
  • Copy the Application (client) ID.
## Creating the StackOne Connector Profile To create the Connector Profile in StackOne for Azure DevOps: Login to StackOne and navigate to [Connector Profiles](https://app.stackone.com/connector_profiles)
  • Click + Connector Profile
  • Search for and select Azure DevOps
  • Select Type as OAuth 2.0 (Microsoft Entra ID)
  • Fill out the fields using details retrieved from your provider:
    • Client ID
    • Client Secret
    • Scopes (Optional)
  • (Optional) Select Actions to be enabled for this Connector Profile
  • Click Create profile
 Congratulations! The new Connector Profile will now show up in your project ready to be used. You can now continue to Link Accounts for Azure DevOps.