Configure Connection
Microsoft Dynamics 365 guide
Register an application in Microsoft Entra ID, configure certificate authentication in NIM, and test access to Dynamics 365 accounts.
You need access to create an application registration in Microsoft Entra ID and an application user with the appropriate security role in the target Dynamics 365 environment.
This connector uses an Entra application registration and certificate authentication. Keep the private-key .pfx certificate secure.
NIM requires Application ID, Directory ID, Resource (Tenant) URL, and a Certificate for authorization.
Create an application registrationDirect link to Create an application registration
Follow Microsoft's application registration instructions to create an application in the tenant associated with your Dynamics 365 environment.
- Open the Microsoft Entra admin center and go to Entra ID > App registrations.
- Select New registration, enter a descriptive name such as
NIM Dynamics 365, choose Accounts in this organizational directory only for a single-tenant integration, and select Register. - On the application Overview page, record the Application (client) ID and Directory (tenant) ID. You will enter both values in NIM.
Create and upload a certificateDirect link to Create and upload a certificate
- Create a certificate using your organization’s approved certificate process. Export both formats:
- An X.509 public certificate in
.cerformat. - A password-protected certificate with its private key in
.pfxformat.
- An X.509 public certificate in
- In the Entra application registration, open Certificates & secrets > Certificates and select Upload certificate. Upload the
.cerfile. - In NIM, go to Settings > Certificates, select Add a certificate, and upload the
.pfxfile.
The .pfx file contains the private key used by NIM. Store it only in approved locations, restrict access to it, and plan to replace it before it expires.
Grant Dynamics 365 API accessDirect link to Grant Dynamics 365 API access
Authorize this certificate-based integration through a Dynamics 365 application user and its security roles. Microsoft's server-to-server authentication guidance explains that delegated permissions are not required for this scenario.
Add the application user to Dynamics 365Direct link to Add the application user to Dynamics 365
- Open the Power Platform admin center and go to Manage > Environments. Select the environment NIM will access.
- Go to Settings > Users + permissions > Application users.
- Select New app user > Add an app, find the Entra application by its name or Application ID, and select Add.
- Choose the business unit, enter the requested email address, and assign a security role with Read access to the accounts and contacts NIM needs. Set the role's access scope to cover the intended records.
- Save the role assignment and select Create.
For the full procedure, see Microsoft's application user management instructions.
Configure and validate the NIM connectionDirect link to Configure and validate the NIM connection
- In NIM Studio, open Systems > Overview and add a Microsoft Dynamics 365 system, or select the existing system.
- Open its Connection screen.
- Enter the following settings and save the connection.
| NIM setting | Value |
|---|---|
| Application ID | The Application (client) ID from the Entra application registration. |
| Directory ID | The Directory (tenant) ID from the same registration. |
| Resource (Tenant) URL | The base URL of the Dynamics 365 environment NIM will access, such as https://yourorganization.crm.dynamics.com. |
| Certificate | The certificate with its private key uploaded under Settings > Certificates in NIM. Its public certificate must be uploaded to the Entra application. |
Test account accessDirect link to Test account access
-
Select Test Connection. NIM calls this endpoint on the configured Resource (Tenant) URL:
GET /api/data/v8.2/accounts?$top=1This request retrieves at most one account. An environment without accessible account records may return an empty result.
-
Confirm that the test succeeds. If it fails, check the Application ID, Directory ID, environment URL, certificate validity, and application user's security roles.
-
Collect the system and inspect the accounts and contacts data. Confirm that the role's access scope includes the records your process needs.
-
Validate the collected data and matching rules before using Dynamics 365 as a source for ticketing, customer service, or product access automation.
The connection test checks account access. Validate contact collection and any downstream destination operations separately.