Set up an Azure DevOps connector

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.

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

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:

user_impersonation (Azure DevOps only allows delegated permissions)
vso.graph_manage
vso.memberentitlementmanagement_write
vso.profile

Click Add permissions.

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

That’s it! Next, move on to the connector configuration instructions.

Option 2: Create a personal access token

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 “ConductorOne”, 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) 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

Click Create.

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

That’s it! 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 ConductorOne
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 ConductorOne.

In ConductorOne, navigate to Admin > 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 ConductorOne)
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 ConductorOne users. Setting multiple owners is allowed. If you choose someone else, ConductorOne 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 and click either OAuth or Username and password. 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.
Click Save.
Click Login with OAuth.
Log in and authorize ConductorOne with your Salesforce instance.
You will then be redirected back to the Salesforce setup page in ConductorOne, where you’ll see an authorization message. 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.
Click Save.

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

That’s it! Your Azure DevOps connector is now pulling access data into ConductorOne.

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 ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.

Step 1: Set up a new Azure DevOps connector

In ConductorOne, navigate to 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 ConductorOne)
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

# baton-azure-devops-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-azure-devops-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne 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 ConductorOne 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

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

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

Check that the connector data uploaded correctly. In ConductorOne, click Applications. 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.

That’s it! Your Azure DevOps connector is now pulling access data into ConductorOne.

Welcome

Build connectors

Configure connectors

Deploy connectors

Upload connector data

Connector library

Set up an Azure DevOps connector

Capabilities

Gather Azure DevOps credentials

Option 1: Register a web application

Option 2: Create a personal access token

Configure the Azure DevOps connector

Step 1: Set up a new Azure DevOps connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

Welcome

Build connectors

Configure connectors

Deploy connectors

Upload connector data

Connector library

​Capabilities

​Gather Azure DevOps credentials

​Option 1: Register a web application

​Option 2: Create a personal access token

​Configure the Azure DevOps connector

​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

Gather Azure DevOps credentials

Option 1: Register a web application

Option 2: Create a personal access token

Configure the Azure DevOps connector

Step 1: Set up a new Azure DevOps connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector