Integration Service user guide

Microsoft Dynamics 365 revolutionizes CRM and ERP by applying intelligence to all forms of data. This enables organizations to evolve from reactive business decisions to proactive insights that empower your employees to accelerate business results.

Use your Microsoft credentials to authenticate and create your own Microsoft Dynamics 365 CRM connection. Once authenticated, you can use the connection to access the different functionalities offered by the Microsoft Dynamics 365 platform.

Find out more about how to create a connection with your Microsoft Dynamics 365 CRM instance from our Microsoft Dynamics 365 CRM authentication page.

The Microsoft Dynamics 365 CRM connector supports events via polling. More information about the events supported for the Microsoft Dynamics 365 CRM connector is available in the Microsoft Dynamics 365 CRM events page.

You can use the connection to enable the Microsoft Dynamics 365 CRM activities in UiPath® Studio and build automations that interact with your Microsoft Dynamics 365 CRM data. These activities allow you to execute create, read, update, and delete operations on your Microsoft Dynamics 365 CRM objects.

The UiPath connector is compatible with the Dataverse Web API v9. Learn more at the Microsoft documentation platform.

What should I do if the schema changed and the connector still shows the old structure?

The solution is to create a new connection (or fully re-create the existing one). This forces the connector to retrieve fresh metadata and the updated table structure appears.

Why do field/output data types sometimes change after recreating the connection?

This happens because the connector rebuilds its schema from the current Dataverse metadata. If Dataverse types, relationships, or activity schemas resolve differently after the change, Studio may infer a different output type.

Why do users still see a Microsoft login/consent screen when we use Bring Your Own OAuth 2.0 (client ID/secret)?

Bring Your Own OAuth 2.0 still follows an OAuth 2.0 authorization flow, so interactive sign-in/consent can be required. In contrast, a pure client credentials flow (application permissions) typically does not require user sign-in, but that depends on whether the connector supports that authentication type for Dynamics CRM in your scenario.

Does the connector run with the permissions of the person who runs the automation?

No, the connector uses the permissions of the account that created the OAuth connection in Integration Service. It does not inherit permissions from the automation runner.

Connection fails after sign-in. Why does the connector call whoami, and what do we need to allow?

The connector may call the whoami endpoint as a post-authentication validation to confirm that the tenant and access are valid. Ensure the user/app used for the connection has permission to access that API in Dynamics.

We’re seeing “service principal is disabled / tenant is disabled / subscription lapsed” errors. What does it mean?

This usually indicates the Azure AD app/service principal used for the connection is disabled, the tenant/subscription has lapsed, or the administrator has blocked token issuance for that resource. The fix is typically on the Microsoft side (re-enable the app/tenant/subscription or update the app registration and permissions).