Set up a Microsoft Azure DevOps connector

Capabilities

Resource	Sync	Provision
Accounts
Service accounts
Service principals
Projects
Groups
Personal access tokens
Project roles (opt-in)
Project role assignments (opt-in)
Teams (opt-in)
Organization (opt-in)
Licenses (opt-in)

The Azure DevOps connector supports automatic account provisioning. This connector does not support account deprovisioning. You must deprovision accounts directly in Azure DevOps. Some Azure DevOps groups are managed in Microsoft Entra (formerly Azure AD), not in Azure DevOps. These groups appear in Azure DevOps and their members are visible, but membership changes are made in Entra. For Entra-managed groups, the connector accepts add and remove requests and reports them as successful without changing membership in Azure DevOps or Entra. These groups are assumed to be managed elsewhere — in the Entra admin center, through another C1 connector that integrates with Entra, or by another process. Reporting requests as successful prevents access reviews and just-in-time access requests from stalling on changes the connector does not perform. To have C1 manage Entra group membership through this connector, enable Entra group membership provisioning during setup. Requirements:

OAuth or client secret authentication. Personal Access Tokens do not support changes to Entra group membership.
The GroupMember.ReadWrite.All Microsoft Graph application permission on the Entra app registration, with admin consent in the tenant.

See Configure the Azure DevOps connector below for setup steps.

Project RBAC (opt-in)

By default, Azure DevOps project-scoped security groups (such as “Contributors” and “Project Administrators”) are synced as flat group resources alongside org-level groups. When you enable Use project RBAC roles, project-scoped groups are also represented as structured Project Role Assignment resources — for example, “Contributor on Project X.” This provides a clearer view of project-level access during access reviews and just-in-time requests, with the role and project scope visible directly on the entitlement. Enabling this option also enables provisioning: C1 can grant and revoke project role assignments, adding or removing members from the underlying Azure DevOps security group.

When Use project RBAC roles is enabled, project-scoped groups continue to sync as flat group resources as well, alongside the new Project Role Assignment resources. Org-level groups are unaffected and continue to sync as normal group resources. No additional Azure DevOps permissions are required beyond those already configured for group sync and provisioning.

Project roles are scoped to a single project. A role with the same name in two different projects, such as “Contributors” in both Project A and Project B, appears as two separate roles, each with its own membership.

Use project RBAC roles cannot be enabled together with Enable incremental sync. Incremental sync does not yet update Project Role Assignment resources between full syncs, so the connector rejects this configuration rather than syncing stale data.

Legacy group identity resolution is disabled by default. Incremental sync still processes GUID-based group creation events, but skips group events whose identifier uses the legacy Microsoft.TeamFoundation.Identity;... format. Enable Legacy group identity resolution only if you need those events; it calls the Azure DevOps Identities API and requires vso.identity in addition to the vso.auditlog scope required by incremental sync.

Gather Azure DevOps credentials

Configuring the connector requires you to pass in credentials generated in Azure DevOps. Gather these credentials before you move on.

A user with Project Collection Administrator role at the organization level and Project Administrator role at the project level must perform this task.

You can authenticate the Azure DevOps connector in three ways: OAuth (interactive sign-in), a service principal with a client secret (machine-to-machine), or a personal access token. Follow the relevant set of instructions below to create your preferred set of credentials.

Option 1: Register a web application

In Azure DevOps, navigate to App registrations and create a new app.

Give the new app a name and select the Accounts in any organizational directory option.

Enter https://accounts.conductor.one/oauth/callback as a Web redirect URI.

Click Register.

Carefully copy and save the application (client) ID.

Click Certificates & secrets and create a new secret.

Carefully copy and save the secret Value (not the secret ID).

Finally, click API permissions and select Azure DevOps.

Give the app the following permissions based on your needs:For sync-only (read) access:

user_impersonation (required - Azure DevOps only allows delegated permissions)
vso.profile
vso.graph
vso.tokenadministration (required to sync personal access tokens)
vso.auditlog (required if you enable incremental sync)
vso.identity (optional — required only when Legacy group identity resolution is enabled)

For full provisioning (read/write) access:

user_impersonation (required - Azure DevOps only allows delegated permissions)
vso.profile
vso.graph_manage
vso.memberentitlementmanagement_write
vso.tokenadministration (required to sync personal access tokens)
vso.auditlog (required if you enable incremental sync)
vso.identity (optional — required only when Legacy group identity resolution is enabled)

Click Add permissions.

Optional — only required for Entra group membership provisioning.If you want C1 to grant and revoke memberships on Entra-sourced Azure DevOps groups (descriptor prefix aadgp.), grant this same Entra app the Microsoft Graph application permission GroupMember.ReadWrite.All with admin consent.In the Entra portal, on this app registration:

Click API permissions > Add a permission.
Choose Microsoft Graph (not Azure DevOps).
Choose Application permissions (not Delegated).
Select GroupMember.ReadWrite.All and click Add permissions.
Click Grant admin consent for <tenant> at the top of the permissions list.

This is the least-privilege Microsoft Graph permission for member-only writes; the broader Group.ReadWrite.All is not required. Without it, Entra group membership provisioning will fail with a clear “missing GroupMember.ReadWrite.All” error at the first grant or revoke attempt.

Carefully copy and save your Azure tenant ID and organization URL.

Done. Next, move on to the connector configuration instructions.

Option 2: Register a service principal (client secret)

This option authenticates as a service principal using the OAuth 2.0 client credentials grant — no user interaction required. It supports all sync capabilities including PAT sync, license sync, and account provisioning. Entra group membership provisioning is also supported when the SP holds the GroupMember.ReadWrite.All Microsoft Graph permission.

In the Microsoft Entra admin center, navigate to App registrations and click New registration.

Give the app a name, select Accounts in this organizational directory only, leave the redirect URI blank, and click Register.

On the overview page, copy and save the Application (client) ID and the Directory (tenant) ID.

Click Certificates & secrets > New client secret. Set a description and expiry, then click Add. Copy and save the secret Value immediately — it is not shown again.

No Azure DevOps API permission is required. Azure DevOps does not expose application permissions in Entra — for the Azure DevOps API the Application permissions option is disabled, and the service principal does not need one. The connector uses the OAuth 2.0 client credentials grant against the Azure DevOps resource; the service principal is authorized by being added to your organization in the steps below.

Optional — only required for Entra group membership provisioning.Click API permissions > Add a permission > Microsoft Graph > Application permissions > select GroupMember.ReadWrite.All > click Add permissions. Then click Grant admin consent for <tenant> and confirm — the status column must show a green checkmark.

In Azure DevOps, navigate to Organization Settings > Users > Add users. Search for your app by name, assign Basic access level, and add it to the relevant projects.

Go to Organization Settings > Security > Permissions > Project Collection Administrators > Members > Add, and add the service principal. This grants it the access needed to read all org-level resources.

Done. Next, move on to the connector configuration instructions.

Option 3: Create a personal access token

Personal Access Token authentication does not support Entra group membership provisioning. With PAT auth, grant and revoke requests against Entra-sourced groups (descriptor prefix aadgp.) are silent no-ops — the connector accepts the request and returns success without making any API call. If you need C1 to actually grant or revoke memberships on Entra-sourced Azure DevOps groups, configure the connector with OAuth (Option 1) or a client secret (Option 2) instead.

In Azure DevOps, navigate to your users settings (the person icon in the top menu bar) and select personal access tokens.

Click + New Token.

Give the new token a name, such as “C1”, then select the relevant organization and set an expiration date.

Under Scopes, select Custom defined and set the relevant set of scopes: To give the connector READ (sync only) permissions:

Graph: Read - Enables all Graph API read operations (users, groups, service principals, memberships, storage keys, descriptors, subject queries)
Project and Team: Read - Enables all Core API read operations (projects, teams, team members)
Token Administration: Read & manage - Required to sync personal access tokens (vso.tokenadministration) To give the connector READ/WRITE (sync and provision) permissions:
Graph: Read & manage - Enables all Graph API read and write operations (users, groups, service principals, memberships, storage keys, descriptors, subject queries)
Member Entitlement Management: Read & write - Enables all Entitlements API read and write operations (list, create, and update user entitlements and licenses)
Project and Team: Read - Enables all Core API read operations (projects, teams, team members)
Token Administration: Read & manage - Required to sync personal access tokens (vso.tokenadministration) To enable incremental sync (optional):
Audit Log: Read - Required if you want to enable the incremental sync feature, which syncs only changes since the last sync (vso.auditlog)
Identity: Read - Required only if you also enable Legacy group identity resolution to resolve legacy group descriptors via the Identities API (vso.identity). This setting defaults to off and is separate from Graph: Read.

Click Create.

The new token is created. Carefully copy and save the token.

Done. Next, move on to the connector configuration instructions.

Configure the Azure DevOps connector

To complete this task, you’ll need:

The Connector Administrator or Super Administrator role in C1
Access to the set of Azure DevOps credentials generated by following the instructions above

Cloud-hosted
Self-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

In C1, navigate to Integrations > Connectors and click Add connector.

Search for Azure DevOps and click Add.

Choose how to set up the new Azure DevOps connector:

Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with C1)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app

Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed. If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.

Click Next.

Find the Settings area of the page and click Edit.

Select your method of authenticating to Azure DevOps. If you chose OAuth:

Enter your organization URL, Azure tenant ID, OAuth client ID, and OAuth client secret in the relevant fields.
Optional. Check the boxes if you want to Sync teams or Sync organizations.
Optional. Check Enable incremental sync to allow the connector to read audit logs and capture updates between full syncs. Requires the Audit Log: Read permission.
Optional. Check Enable legacy group identity resolution to process legacy group audit events. This setting defaults to off and requires vso.identity.
Optional. Check Enable Entra group membership provisioning to grant and revoke memberships on Entra-sourced groups via Microsoft Graph. Requires the GroupMember.ReadWrite.All Microsoft Graph application permission with admin consent. Per Microsoft, changes may take up to 1 hour to appear in the Azure DevOps Members view.
Optional. Check Use project RBAC roles to enable the Sparse ACL model for project access. Project-scoped groups are also synced as structured Project Role Assignment resources, with role and project context visible on each entitlement. See Project RBAC for details.
Click Save.
Click Login with OAuth.
Log in and authorize C1 with your Azure DevOps instance.
You will then be redirected back to the Azure DevOps setup page in C1, where you’ll see an authorization message. If you chose Client secret:
Enter your Azure DevOps organization URL, tenant ID, client ID, and client secret from Option 2.
Optional. Check the boxes if you want to Sync teams or Sync organizations.
Optional. Check Enable incremental sync to allow the connector to read audit logs and capture updates between full syncs. Requires the Audit Log: Read permission on the service principal.
Optional. Check Enable legacy group identity resolution to process legacy group audit events. This setting defaults to off and requires vso.identity.
Optional. Check Enable Entra group membership provisioning to grant and revoke memberships on Entra-sourced groups via Microsoft Graph. The same client ID and secret are used. Requires the GroupMember.ReadWrite.All Microsoft Graph application permission with admin consent. Per Microsoft, changes may take up to 1 hour to appear in the Azure DevOps Members view.
Optional. Check Use project RBAC roles to enable the Sparse ACL model for project access. See Project RBAC for details.
Click Save. If you chose Personal access token:
Paste your Azure DevOps organization URL in the format https://dev.azure.com/{Your_Organization} into the Organization URL field.
Paste the token into the Personal Access Token field.
Optional. Check the boxes if you want to Sync teams or Sync organizations.
Optional. Check Enable incremental sync to allow the connector to read audit logs and capture updates between full syncs. Requires the Audit Log: Read permission.
Optional. Check Enable legacy group identity resolution to process legacy group audit events. This setting defaults to off and requires Identity: Read (vso.identity).
Optional. Check Use project RBAC roles to enable the Sparse ACL model for project access. See Project RBAC for details.
Click Save.

The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your Azure DevOps connector is now pulling access data into C1.

Follow these instructions to use the Azure DevOps connector, hosted and run in your own environment.When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

Resources

Official download center: For stable binaries (Windows/Linux/macOS) and container images.

Step 1: Set up a new Azure DevOps connector

In C1, navigate to Integrations > Connectors > Add connector.

Search for Baton and click Add.

Choose how to set up the new Azure DevOps connector:

Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with C1)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app

Click Next.

In the Settings area of the page, click Edit.

Click Rotate to generate a new Client ID and Secret. Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Azure DevOps connector deployment:

Secrets configuration

Choose one of the following secrets configurations based on your authentication method.Option A — Personal access token:

# baton-azure-devops-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-azure-devops-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>

  # Azure DevOps credentials
  BATON_AUTH_METHOD: azure-devops-group-pat
  BATON_ORGANIZATION_URL: <Your Azure DevOps organization URL, formed like https://dev.azure.com/{Your_Organization}>
  BATON_PERSONAL_ACCESS_TOKEN: <Azure DevOps personal access token>

  # Optional: include if you want C1 to provision access using this connector
  BATON_PROVISIONING: "true"

  # Optional: include if you want to sync teams or organization (license) data
  BATON_SYNC_ORGANIZATION: "true"

  # Optional: include to read audit logs and capture updates between full syncs (requires Audit Log: Read permission)
  BATON_ENABLE_INCREMENTAL_SYNC: "true"

  # Optional, defaults to false; requires Identity: Read (vso.identity)
  # BATON_ENABLE_LEGACY_GROUP_IDENTITY_RESOLUTION: "true"

  # Optional: enable the Sparse ACL model for project access (see Project RBAC above).
  # Cannot be combined with BATON_ENABLE_INCREMENTAL_SYNC (mutually exclusive).
  # BATON_USE_PROJECT_RBAC: "true"

Option B — Service principal (client secret):

# baton-azure-devops-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-azure-devops-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>

  # Azure DevOps credentials
  BATON_AUTH_METHOD: azure-devops-group-client-secret
  BATON_ORGANIZATION_URL: <Your Azure DevOps organization URL, formed like https://dev.azure.com/{Your_Organization}>
  BATON_AZURE_DEVOPS_TENANT_ID: <Entra tenant ID>
  BATON_CLIENT_SECRET_CLIENT_ID: <App registration client ID>
  BATON_CLIENT_SECRET_CLIENT_SECRET: <App registration client secret>

  # Optional: include if you want C1 to provision access using this connector
  BATON_PROVISIONING: "true"

  # Optional: include if you want to sync teams or organization (license) data
  BATON_SYNC_ORGANIZATION: "true"

  # Optional: include to read audit logs and capture updates between full syncs (requires Audit Log: Read permission)
  BATON_ENABLE_INCREMENTAL_SYNC: "true"

  # Optional, defaults to false; requires Identity: Read (vso.identity)
  # BATON_ENABLE_LEGACY_GROUP_IDENTITY_RESOLUTION: "true"

  # Optional: include to provision membership on Entra-sourced groups via Microsoft Graph.
  # Requires the GroupMember.ReadWrite.All Microsoft Graph application permission
  # with admin consent on the Entra app registration. See the OAuth setup section above.
  BATON_ENABLE_ENTRA_GROUP_PROVISIONING: "true"

  # Optional: enable the Sparse ACL model for project access (see Project RBAC above).
  # Cannot be combined with BATON_ENABLE_INCREMENTAL_SYNC (mutually exclusive).
  # BATON_USE_PROJECT_RBAC: "true"

Option C — OAuth:

# baton-azure-devops-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-azure-devops-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>

  # Azure DevOps credentials
  BATON_AUTH_METHOD: azure-devops-group-oauth
  BATON_ORGANIZATION_URL: <Your Azure DevOps organization URL, formed like https://dev.azure.com/{Your_Organization}>
  BATON_AZURE_DEVOPS_TENANT_ID: <Entra tenant ID>
  BATON_OAUTH2_CLIENT_CRED_GRANT_CLIENT_ID: <OAuth app client ID>
  BATON_OAUTH2_CLIENT_CRED_GRANT_CLIENT_SECRET: <OAuth app client secret>

  # Optional: include if you want C1 to provision access using this connector
  BATON_PROVISIONING: "true"

  # Optional: include if you want to sync teams or organization (license) data
  BATON_SYNC_ORGANIZATION: "true"

  # Optional: include to read audit logs and capture updates between full syncs (requires Audit Log: Read permission)
  BATON_ENABLE_INCREMENTAL_SYNC: "true"

  # Optional, defaults to false; requires Identity: Read (vso.identity)
  # BATON_ENABLE_LEGACY_GROUP_IDENTITY_RESOLUTION: "true"

  # Optional: include to provision membership on Entra-sourced groups via Microsoft Graph.
  # Requires the GroupMember.ReadWrite.All Microsoft Graph application permission
  # with admin consent on the Entra app registration. See the OAuth setup section above.
  BATON_ENABLE_ENTRA_GROUP_PROVISIONING: "true"
  BATON_ENTRA_CLIENT_ID: <Graph app client ID>
  BATON_ENTRA_CLIENT_SECRET: <Graph app client secret>

  # Optional: enable the Sparse ACL model for project access (see Project RBAC above).
  # Cannot be combined with BATON_ENABLE_INCREMENTAL_SYNC (mutually exclusive).
  # BATON_USE_PROJECT_RBAC: "true"

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-azure-devops.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-azure-devops
  labels:
    app: baton-azure-devops
spec:
  selector:
    matchLabels:
      app: baton-azure-devops
  template:
    metadata:
      labels:
        app: baton-azure-devops
        baton: "true"
        baton-app: azure-devops
    spec:
      containers:
      - name: baton-azure-devops
        image: public.ecr.aws/conductorone/baton-azure-devops:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-azure-devops
        envFrom:
        - secretRef:
            name: baton-azure-devops-secrets

Step 3: Deploy the connector

Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

Check that the connector data uploaded correctly. In C1, click Apps. On the Managed apps tab, locate and click the name of the application you added the Azure DevOps connector to. Azure DevOps data should be found on the Entitlements and Accounts tabs.

Done. Your Azure DevOps connector is now pulling access data into C1.

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up a Microsoft Azure DevOps connector

Capabilities

Project RBAC (opt-in)

Gather Azure DevOps credentials

Option 1: Register a web application

Option 2: Register a service principal (client secret)

Option 3: Create a personal access token

Configure the Azure DevOps connector

Resources

Step 1: Set up a new Azure DevOps connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

​Capabilities

​Project RBAC (opt-in)

​Gather Azure DevOps credentials

​Option 1: Register a web application

​Option 2: Register a service principal (client secret)

​Option 3: Create a personal access token

​Configure the Azure DevOps connector

​Resources

​Step 1: Set up a new Azure DevOps connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Project RBAC (opt-in)

Gather Azure DevOps credentials

Option 1: Register a web application

Option 2: Register a service principal (client secret)

Option 3: Create a personal access token

Configure the Azure DevOps connector

Resources

Step 1: Set up a new Azure DevOps connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector