Set up a Microsoft Dynamics 365 - Finance & Operations connector

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
Roles

The Microsoft Dynamics 365 - Finance & Operations connector supports automatic account provisioning. The user for whom a new account is provisioned must have an existing Entra account with a valid license. This connector does not support account deprovisioning. You must deprovision accounts directly in Microsoft Dynamics 365 - Finance & Operations.

Gather Microsoft Dynamics 365 - Finance & Operations credentials

Configuring the connector requires you to pass in credentials generated in Microsoft Dynamics 365 - Finance & Operations. Gather these credentials before you move on.

A user who is an Application Administrator (or similar admin role) in Microsoft Entra ID and a System Administrator in Microsoft Dynamics 365 - Finance & Operations must perform this task.

Look up your Microsoft Dynamics 365 - Finance & Operations environment URL

Log into the Power Platform Admin Center.

On the left side of the screen, click Manage > Environments.

Click the name of the environment you want to integrate with ConductorOne.

On the environment’s details page, carefully copy and save the URL of the environment.

Create a new Entra application

In the Entra ID 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 (typically Accounts in this organizational directory only (Default Directory only - Single tenant)). 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.

Give the new Entra app API permissions

Click API permissions.

Click + Add permissions and click the APIs my organization uses tab.

Search for “Dynamics ERP”.

Give the app all three available permissions:

AX.FullAccess
CustomService.FullAccess
Odata.FullAccess

Click Add permissions.

Navigate to Identity > Applications > Enterprise applications > All applications.

Click Grant admin consent for … at the top of the permissions list, and confirm your action.

Create a client secret

Next, we’ll generate a client secret for your app. Navigate to the app and click Certificates & secrets.

Click + New client secret.

Give the client secret a description and set its expiration.

Click Add.

The client secret is shown in the VALUE field. Carefully copy and save the Secret Value.

Link the new application to your Finance & Operations user

Make sure you have a Finance & Operations user with the System administrator role complete this task.

Add a new register to the table, filling in:

The app’s client ID
Your user ID
A name that identifies this entry, such as “C1 integration”

Click OK.

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

Configure the Microsoft Dynamics 365 - Finance & Operations connector

To complete this task, you’ll need:

The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of Microsoft Dynamics 365 - Finance & Operations 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 Microsoft Dynamics 365 - Finance & Operations and click Add.

Choose how to set up the new Microsoft Dynamics 365 - Finance & Operations 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.

Enter the Microsoft Dynamics 365 - Finance & Operations credentials into the relevant fields.

Optional. If desired, click to enable Sync only enabled role assignments. When this option is enabled, ConductorOne will ignore all roles that do not have the enabled status.

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 Microsoft Dynamics 365 - Finance & Operations connector is now pulling access data into ConductorOne.

Follow these instructions to use the Microsoft Dynamics 365 - Finance & Operations connector, hosted and run in your own environment. Contact ConductorOne’s support team to download the latest version of the connector.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 Microsoft Dynamics 365 - Finance & Operations connector

In ConductorOne, navigate to Connectors > Add connector.

Search for Baton and click Add.

Choose how to set up the new Microsoft Dynamics 365 - Finance & Operations 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 Microsoft Dynamics 365 - Finance & Operations connector deployment:

Secrets configuration

# baton-microsoft-dynamics-fo-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-microsoft-dynamics-fo-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Microsoft Dynamics 365 - Finance & Operations-specific credentials
  BATON_ENVIRONMENT_URL: <Environment URL of your Microsoft Dynamics 365 - Finance & Operations instance>
  BATON_DYNAMICS_CLIENT_ID: <Client ID of the Entra app created to authenticate with the Dataverse API>
  BATON_DYNAMICS_CLIENT_SECRET: <Client secret of the Entra app created to authenticate with the Dataverse API>
  BATON_TENANT_ID: <Tenant ID for your account>

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

  # Optional: include if you only want ConductorOne to sync enabled roles 
  BATON_SYNC_ONLY_ENABLED_ROLE_ASSIGNMENTS: true

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

Deployment configuration

# baton-microsoft-dynamics-fo.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-microsoft-dynamics-fo
  labels:
    app: baton-microsoft-dynamics-fo
spec:
  selector:
    matchLabels:
      app: baton-microsoft-dynamics-fo
  template:
    metadata:
      labels:
        app: baton-microsoft-dynamics-fo
        baton: true
        baton-app: microsoft-dynamics-fo
    spec:
      containers:
      - name: baton-microsoft-dynamics-fo
        image: ghcr.io/conductorone/baton-microsoft-dynamics-fo:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-microsoft-dynamics-fo
        envFrom:
        - secretRef:
            name: baton-microsoft-dynamics-fo-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 Microsoft Dynamics 365 - Finance & Operations connector to. Microsoft Dynamics 365 - Finance & Operations data should be found on the Entitlements and Accounts tabs.

That’s it! Your Microsoft Dynamics 365 - Finance & Operations connector is now pulling access data into ConductorOne.

Welcome

Build connectors

Configure connectors

Deploy connectors

Upload connector data

Connector library

Set up a Microsoft Dynamics 365 - Finance & Operations connector

Capabilities

Gather Microsoft Dynamics 365 - Finance & Operations credentials

Look up your Microsoft Dynamics 365 - Finance & Operations environment URL

Create a new Entra application

Give the new Entra app API permissions

Create a client secret

Link the new application to your Finance & Operations user

Configure the Microsoft Dynamics 365 - Finance & Operations connector

Step 1: Set up a new Microsoft Dynamics 365 - Finance & Operations 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 Microsoft Dynamics 365 - Finance & Operations credentials

​Look up your Microsoft Dynamics 365 - Finance & Operations environment URL

​Create a new Entra application

​Give the new Entra app API permissions

​Create a client secret

​Link the new application to your Finance & Operations user

​Configure the Microsoft Dynamics 365 - Finance & Operations connector

​Step 1: Set up a new Microsoft Dynamics 365 - Finance & Operations connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather Microsoft Dynamics 365 - Finance & Operations credentials

Look up your Microsoft Dynamics 365 - Finance & Operations environment URL

Create a new Entra application

Give the new Entra app API permissions

Create a client secret

Link the new application to your Finance & Operations user

Configure the Microsoft Dynamics 365 - Finance & Operations connector

Step 1: Set up a new Microsoft Dynamics 365 - Finance & Operations connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector