> 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.md).

# Microsoft Dynamics 365

The eMarketeer integration for Microsoft Dynamics 365 Sales bridges your marketing and sales teams so CRM and marketing automation share one reliable source of truth.

With Dynamics connected to eMarketeer, you can sync contact preferences, enforce GDPR compliance, import CRM segments on the fly, and automate customer Journeys without creating data silos.

## In this section

* [Setup & Configuration](/integrations/dynamics/dynamics-installation.md): step-by-step instructions for connecting your Dynamics 365 instance to eMarketeer and provisioning the initial data tables.
* [Consent & Subscription Sync](/integrations/dynamics/dynamics-legal-basis-sync.md): how the automated, multi-tiered sync engine handles Legal Basis and granular email subscriptions to keep both systems aligned and compliant.
* [Importing Contacts & Lists](/integrations/dynamics/dynamics-import.md): how to pull Dynamics Contact and Lead Marketing Lists into eMarketeer, either as a standard import or on the fly before a send-out.
* [Journey Steps & Automations](/integrations/dynamics/dynamics-journey-steps.md): how to use eMarketeer's visual automations to trigger actions, sync engagement, and update data in Dynamics based on how contacts interact with your marketing.

## What to do next

If you are setting this up for the first time, start with the [Setup & Configuration](/integrations/dynamics/dynamics-installation.md) guide to connect the two systems.


---

# 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.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.