> For the complete documentation index, see [llms.txt](https://docs.dinmo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dinmo.io/integrations/destination-platforms/microsoft-dynamics-365.md).

# Microsoft Dynamics 365

## Supported Destination Services

DinMo supports the following destination service:

* [Synchronise data objects](/integrations/destination-platforms/microsoft-dynamics-365/synchronise-data-objects.md) - sync any dataset

## Authentication to Microsoft Dynamics 365

Regardless of the selected destination service, DinMo will always connect to MD365 using OAuth2 authentication. Please make sure the user who connects MD365 on DinMo has the right permissions on the target ad accounts.

You must enter the following credentials to login to MD365 from DinMo:

* Web API endpoint
* Tenant ID
* Client ID
* Client Secret

### Setting up App Registration

To find this information, you must go through the following steps:

1. Go to the 'Azure Active Directory' portal, then 'App Registrations'
2. Create a single tenant app registration
   1. From 'Overview', copy across the **Client ID** and **Tenant ID** generated here
3. Within the App, go to 'Certificates & secrets', then click **New Client Secret**
   1. Copy this Client Secret into DinMo
4. Now you must grant the correct permissions to be able to use the app. Go to 'API Permissions', and click 'Add Permissions', where you can select 'Dynamics CRM' and enable *user\_impersonation* permission

### Web API Endpoint

To complete your MD365 connection setup, you will need to provide your service URL (Web API Endpoint). To do this:

1. Sign in to [Microsoft Power Apps](https://powerapps.microsoft.com/).
2. Go to settings (top right corner) to open the settings sidebar. Then select 'Developer resources'.
3. Copy the Web API Endpoint from the sidebar


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dinmo.io/integrations/destination-platforms/microsoft-dynamics-365.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.