Command · Connector setup

Set up Microsoft Dynamics 365 with an Application User

Connect raia Command to Dynamics 365 server-to-server. You register an app in Microsoft Entra, give it access to your Dynamics 365 environment as an Application User, then paste four values into the connector form in raia Command.

Before you start

With the Application User method, nobody has to sign in each time raia Command reads Dynamics 365. Command connects as an app, and Dynamics 365 lets that app do only what its security role allows.

You'll use two Microsoft admin sites, both with the same Microsoft account — for example, the account you used to sign up for your Dynamics 365 trial. That account needs permission to register apps in Microsoft Entra and to manage your environment in the Power Platform admin center.

Along the way you collect four values and paste them into the form in raia Command:

The four values you collect and the raia Command field each one goes in
Field in raia Command	Where you find the value	Step
Application (client) ID	Microsoft Entra → your app → Overview	Step 1
Directory (tenant) ID	Microsoft Entra → your app → Overview	Step 1
Client secret	Microsoft Entra → your app → Certificates & secrets (the Value column)	Step 1
Environment URL	Power Platform admin center → your environment's details page	Step 2

Step 1: Register an app in Microsoft Entra

This gives you the Application (client) ID, the Directory (tenant) ID and the client secret.

Go to entra.microsoft.com and sign in.
In the left menu, open Entra ID (on some tenants it's Identity → Applications), then App registrations → + New registration.
Name the app something you'll recognize, such as Command connector.
Choose Accounts in this organizational directory only (single tenant). Leave the Redirect URI blank, then click Register.
On the app's Overview page, copy the Application (client) ID. It goes in the Application (client) ID field.
On the same page, copy the Directory (tenant) ID. It goes in the Directory (tenant) ID field.
Go to Certificates & secrets → Client secrets → + New client secret, then click Add.
Copy the Value column right away. It goes in the Client secret field.

Copy the Value, not the Secret ID

Microsoft shows the secret's Value only once, right after you create it. Don't copy the Secret ID next to it. If you lose the Value, create a new client secret. Treat the Value like a password, and note when the secret expires so you can create a new one and update the connection in time.

Step 2: Give the app access to Dynamics 365

You do this in the Power Platform admin center.

Go to admin.powerplatform.microsoft.com.
Click Manage → Environments and open the environment your Dynamics 365 trial created.
On the environment's details page, copy the Environment URL (something like orgxxxxxx.crm.dynamics.com). It goes in the Environment URL field.
Click Settings at the top, then Users + permissions → Application users → + New app user.
Click + Add an app, find the app you registered in Step 1, and select your business unit.
Under Security roles, pick a role, then click Create.

raia Command, and the agents that use this connection, can only do what this security role allows.

Choosing a security role

For a trial, Customer Service Representative fits for cases and knowledge articles. System Administrator is the simplest choice, but it gives the app full access to the environment. For real customer data, use a role that allows only the records your agents need.

Step 3: Connect in raia Command

Go back to the Microsoft Dynamics 365 connector in raia Command and choose the Application User (server-to-server) method.

Paste the Application (client) ID into the Application (client) ID field.
Paste the Directory (tenant) ID into the Directory (tenant) ID field.
Paste the secret Value into the Client secret field, and the environment address into the Environment URL field.
Click Connect Microsoft Dynamics 365.

Next, start with a small, approved import and check what arrives before you give agents wider access.

If the connection doesn't work

Check these first:

The client secret is the Value, not the Secret ID, and it hasn't expired.
The Application (client) ID and the Directory (tenant) ID come from the same app registration.
The Environment URL belongs to the environment where you created the application user.
The application user exists in that environment and has a security role.

Write tools stay off until an admin turns them on

The Dynamics 365 tools that create or update cases, contacts and accounts, or add notes, stay off until an admin turns them on — even if the security role allows changes.

Microsoft Dynamics 365 connector

What the connector imports and what its agent tools can do.

Command Connectors

All available Command connectors, authentication options, and Sync History.

Security guide

Least-privilege access and credential handling for connected systems.