Set up a Microsoft Azure DevOps connector

C1 provides identity governance and just-in-time provisioning for Microsoft Azure DevOps. Integrate your Azure DevOps instance with C1 to run user access reviews (UARs) and enable just-in-time access requests.

Capabilities

Resource	Sync	Provision
Accounts
Service accounts
Service principals
Projects
Groups

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 authentication. Personal Access Tokens do not support changes to Entra group membership.
• The GroupMember.ReadWrite.All permission on the Entra app registration, with admin consent in the tenant.

See Configure the Azure DevOps connector below for setup steps.

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 by registering a web app and signing in with OAuth, or by using a personal access token. Follow the relevant set of instructions below to create your preferred set of credentials.

Option 1: Register a web application

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

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

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

4. Click Register.

5. Carefully copy and save the application (client) ID.

6. Click Certificates & secrets and create a new secret.

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

8. Finally, click API permissions and select Azure DevOps.

9. 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

   For full provisioning (read/write) access:

   • user_impersonation (required - Azure DevOps only allows delegated permissions)
   • vso.profile
   • vso.graph_manage
   • vso.memberentitlementmanagement_write
10. Click Add permissions.

11. 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:

    1. Click API permissions > Add a permission.
    2. Choose Microsoft Graph (not Azure DevOps).
    3. Choose Application permissions (not Delegated).
    4. Select GroupMember.ReadWrite.All and click Add permissions.
    5. 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.

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

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

Option 2: 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) instead.

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

2. Click + New Token.

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

4. 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) 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) 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
5. Click Create.

6. 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

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

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

2. Search for Azure DevOps and click Add.

3. 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
4. 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.

5. Click Next.

6. Find the Settings area of the page and click Edit.

7. Select your method of authenticating to Azure DevOps and click either OAuth or Username and password. If you chose OAuth:

   1. Enter your organization URL, Azure tenant ID, OAuth client ID, and OAuth client secret in the relevant fields.
   2. Optional. Check the boxes if you want to Sync teams or Sync organizations.
   3. 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.
   4. 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 (see Step 9 of Option 1). Per Microsoft, changes may take up to 1 hour to appear in the Azure DevOps Members view.
   5. Click Save.
   6. Click Login with OAuth.
   7. Log in and authorize C1 with your Azure DevOps instance.
   8. You will then be redirected back to the Azure DevOps setup page in C1, where you’ll see an authorization message. If you chose Personal access token:
   9. Paste your Azure DevOps organization URL in the format https://dev.azure.com/{Your_Organization} into the Organization URL field.
   10. Paste the token into the Personal Access Token field.
   11. Optional. Check the boxes if you want to Sync teams or Sync organizations.
   12. 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.
   13. Click Save.
8. 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.

Self-hosted

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

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

2. Search for Baton and click Add.

3. 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
4. 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.

5. Click Next.

6. In the Settings area of the page, click Edit.

7. 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

# 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_ORGANIZATION_URL: <Your Azure DevOps organization URL, formed like https://dev.azure.com/{Your_Organization}>
  BATON_PAT: <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 grant sources
  BATON_SKIP_UNUSED_ROLES: true

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

  # Optional: include to provision membership on Entra-sourced groups via Microsoft Graph.
  # Requires OAuth authentication (BATON_PAT-only deployments cannot use this)
  # AND 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

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: ghcr.io/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

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

2. 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.