> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/integrations/dynamics/dynamics-installation.md).

# Dynamics - Installation Process

Set up the Microsoft Dynamics 365 Sales integration. A few manual steps are required before you complete the configuration in the eMarketeer UI.

{% stepper %}
{% step %}

### Create an app user in the Power Platform environment

As a **System Administrator**, follow these steps:

1. Navigate to a consent URL and add the app: `https://login.microsoftonline.com/<your tenant id>/adminconsent?client_id=a2a5e177-5102-4792-b0eb-52f4539f3cf7`
2. Open the **Power Platform Admin Center** at `https://admin.powerplatform.microsoft.com`.
3. Go to **Manage > Environments** and select the environment you are configuring.
4. Open **Settings → Users + permissions → Application users**.
5. Click **+ New app user**.
6. In the app selection screen, choose **eMarketeer Marketing Cloud**. If it is not visible, search using the App ID `a2a5e177-5102-4792-b0eb-52f4539f3cf7`.
7. Assign the security role **System Administrator** to the app user.
8. Click **Save**.
   {% endstep %}

{% step %}

### Enable auditing for consent sync

To ensure consent data syncs correctly, enable auditing for the Contact table.

1. Go to Power Apps at `https://make.powerapps.com`.
2. Navigate to **Tables → Contact**.
3. Click **Properties**, then **Advanced options**.
4. Check **Audit changes to its data**.
5. Click **Save**.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-dc80c418a402ca60f853b2e4ca40b73f1984bc9c%2Faudit.png?alt=media" alt="Advanced options for the Contact table with audit changes enabled"></div>
{% endstep %}

{% step %}

### Enable the integration in eMarketeer

This action requires the Administrator role.

In eMarketeer, click the gear icon at the top right, choose **Account Settings**, open **Integrations**, and click **Manage** on the **Microsoft Dynamics 365** card.

Click **Connect to Dynamics 365**.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-0a077a602ec5e3eea5fdd7c7625c342058b587ab%2Fdynamics-installation-connect-button.png?alt=media" alt="Microsoft Dynamics 365 integration page in eMarketeer with the Connect to Dynamics 365 button"></div>

Microsoft asks you to pick an account. Choose a Microsoft account that has access to the Dynamics environment you want to integrate, or click **Use another account** to sign in with a different one.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-4e2b6fa774fb7a4852c085c22d2237fbd619c458%2Fdynamics-installation-pick-account.png?alt=media" alt="Microsoft Pick an account screen with two accounts and Use another account"></div>

Choose the organization (environment) you want to integrate with and click **Continue**.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-6eebe2dd398587e00a779257ec2b33a3328f36d6%2Fdynamics-installation-choose-organization.png?alt=media" alt="List of Dynamics organizations to connect to, with one selected, and the Continue button"></div>
{% endstep %}
{% endstepper %}


---

# 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://support.emarketeer.com/integrations/dynamics/dynamics-installation.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.