Set up a Microsoft Azure connector

ConductorOne provides identity governance and just-in-time provisioning for Azure. Integrate your Azure instance with ConductorOne to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access.

This connector is in beta. This means it’s undergoing ongoing testing and development while we gather feedback, validate functionality, and improve stability. Beta connectors are generally stable, but they may have limited feature support, incomplete error handling, or occasional issues.
We recommend closely monitoring workflows that use this connector and contacting our Support team with any issues or feedback.

Capabilities

Resource	Sync	Provision
Accounts	ℹ️
Groups	ℹ️
Managed identities	ℹ️
Azure roles	✅	✅
Resource groups	✅
Subscriptions	✅

ℹ️ This connector pulls account, group, and managed identity information from the Entra ID connector. You’ll configure this relationship when setting up the connector.

Gather Azure credentials

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

A user with the Global Administrator permission in Azure must perform this task.

Create a new Entra application

In the Entra admin center, navigate to App registrations.
Click + New registration.
Give the application a name, such as “ConductorOne”, and select the supported account type relevant to your Entra installation. You do not need to set a redirect URL.
Click Register.
The new app is created. Carefully copy and save the Application (client) ID and the Directory (tenant) ID shown on the application summary page.
Next, we’ll generate a client secret for this app. Click Certificates & secrets.
Click + New client secret.
Give the client secret a description and set its expiration.
Click Add.
The client secret is generated. Carefully copy and save the Secret Value.

Assign Azure RBAC permissions to the application

Repeat this process for each subscription you want to sync to ConductorOne. Alternately, you can grant a Management Group scope encompassing all the desired subscriptions.

In the Azure portal’s search bar, type “Subscriptions” and select the relevant Azure subscription.
In the left-hand menu of your subscription, select Access control (IAM).
Click + Add > Add role assignment.
On the Role tab, search for and select the Reader role.
If you want to use the ConductorOne connector to provision Azure roles, also grant the User Access Administrator role.
Click Next.
On the Members tab, ensure User, group, or service principal is selected for Assign access to.
Click + Select members.
In the Select members pane, search for and select the name of your App Registration.
Click Select at the bottom of the pane.
Click Review + assign at the bottom.
Allow time for the new role to propagate. Azure role assignments can take several minutes (typically five to 15, sometimes up to 30) to fully propagate.

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

Configure the Azure connector

To complete this task, you’ll need:
The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of Azure credentials generated by following the instructions above

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 and click Add.
Choose how to set up the new Azure 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.
Paste the application (client) ID into the Azure client ID field.
Paste the client secret into the Azure client secret field.
Paste the directory (tenant) ID into the Azure tenant ID field.
Click Save.
Finally, tell the connector where to find the identities that will be used for this app in ConductorOne.
1. In the Shared identity source area of the page, click Edit.
2. Select your AWS v2 connector.
3. Optional. Limit the identities pulled from the connector you selected to only those with a certain entitlement by setting the entitlement.
4. 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 connector is now pulling access data into ConductorOne.

Follow these instructions to use the Azure connector, hosted and run in your own environment. Contact ConductorOne’s support team to download the latest version of the connector and get detailed setup instructions.

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 connector

In ConductorOne, navigate to Connectors > Add connector.
Search for Baton and click Add.
Choose how to set up the new Azure 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.
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 connector deployment:

Secrets configuration

# baton-microsoft-azure-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-microsoft-azure-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Azure credentials
  BATON_ENTRA_CLIENT_ID: <Azure application (client) ID>
  BATON_ENTRA_CLIENT_SECRET: <Azure client secret>
  BATON_ENTRA_TENANT_ID: <Azure directory (tenant) ID>
  BATON_EXTERNAL_SYNC_MODE: true
  BATON_EXTERNAL_RESOURCE_C1Z: <The path to the c1z file to sync external Baton resources with>
  BATON_EXTERNAL_RESOURCE_ENTITLEMENT_ID_FILTER: <Optional. The entitlement that external users, groups must have access to sync external Baton resources>

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

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

Deployment configuration

# baton-microsoft-azure.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-microsoft-azure
  labels:
    app: baton-microsoft-azure
spec:
  selector:
    matchLabels:
      app: baton-microsoft-azure
  template:
    metadata:
      labels:
        app: baton-microsoft-azure
        baton: true
        baton-app: microsoft-azure
    spec:
      containers:
      - name: baton-microsoft-azure
        image: ghcr.io/conductorone/baton-microsoft-azure:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-microsoft-azure-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 connector to. Azure data should be found on the Entitlements and Accounts tabs.

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