Microsoft Dynamics 365 Sales (Dataverse)

Microsoft Dynamics 365 Sales (Dataverse)

This connector works with Dynamics 365 Sales and any other Dataverse environment (Customer Service, Power Apps, custom tables) through the Dataverse Web API v9.2 (https://<org>.crm<n>.dynamics.com/api/data/v9.2): accounts, contacts, leads, opportunities, activities and notes, plus OData and FetchXML queries and table metadata for everything else. Every call runs as the user who authorized the connector, with that user's security roles: the AI sees and changes exactly what that user may.

Setup (one-time, about 10 minutes)

1. Find the environment's address: in Dynamics open Settings (gear) → Advanced settings, or the Power Platform admin center → Environments → your environment → Environment URL. It looks like contoso.crm4.dynamics.com. Put the host name, without https:// and without a path, into DYNAMICS_ORG_HOST.
2. Open https://entra.microsoft.com → Applications → App registrations → New registration (or reuse the app of the Outlook, OneDrive or SharePoint connector). Supported account types: Accounts in this organizational directory only is the usual choice.
3. Redirect URI: platform Web, https://cloud.anythingmcp.com/api/mcp-oauth/callback on AnythingMCP Cloud, or <your AnythingMCP URL>/api/mcp-oauth/callback when you host AnythingMCP yourself. It must match character for character (AADSTS50011 otherwise).
4. API permissions → Add a permission → Dynamics CRM → Delegated permissions → user_impersonation. Grant admin consent if your organisation does not let users consent themselves.
5. Certificates & secrets → New client secret; copy the secret Value (shown once).
6. Fill in MICROSOFT_CLIENT_ID, MICROSOFT_CLIENT_SECRET, MICROSOFT_TENANT_ID (the Directory (tenant) ID, your domain, or organizations for a multi-tenant app) and DYNAMICS_ORG_HOST, then install.
7. On the connector page click Authorize with Provider and sign in with a user of that environment. The refresh token is stored encrypted and access tokens are renewed automatically.

Region in the host name: the number after crm is the datacenter region: crm North America, crm2 South America, crm3 Canada, crm4 EMEA, crm5 Asia Pacific, crm6 Australia, crm7 Japan, crm8 India, crm11 United Kingdom, crm12 France, crm14 South Africa, crm15 UAE, crm16 Germany, crm17 Switzerland, crm19 Norway, crm20 Korea, crm21 Sweden. Copy it from the environment URL rather than guessing. Government clouds use crm9.dynamics.com, crm.microsoftdynamics.us or crm.appsplatform.us.

Scope: https://<DYNAMICS_ORG_HOST>/user_impersonation offline_access, built from the host. offline_access makes Microsoft issue a refresh token. Do not add Microsoft Graph scopes to this connector: one token serves one API. Changing DYNAMICS_ORG_HOST later needs a new authorization, because the token belongs to one environment.

Who can use it: the signed-in user needs a Dynamics 365 or Power Apps licence in that environment and a security role (Salesperson, Sales Manager or System Customizer). Writes are limited by the same role.

Names: tools take column logical names (name, emailaddress1, estimatedvalue), and the generic tools take the entity set name, the plural used in the URL (accounts, opportunities, salesorders, cr123_projects). d365_list_tables maps tables to entity sets, d365_describe_table lists the columns, d365_list_lookups the lookup navigation properties, d365_get_choice_options the numbers behind choice columns.

Reading

• Answers carry labels next to raw values: statecode is 0 and [email protected] is Open; a lookup such as _parentcustomerid_value holds the id and its FormattedValue the name.
• filter: name eq 'Contoso', contains(name,'Contoso'), startswith(fullname,'Mey'), estimatedvalue gt 10000, createdon ge 2026-10-01T00:00:00Z (date and time columns with a full UTC timestamp; date-only columns such as estimatedclosedate bare, estimatedclosedate le 2026-12-31), _ownerid_value eq <user id> (lookups as _<column>_value, GUIDs bare), statecode eq 0 for active rows. Choice columns compare numbers.
• select keeps answers small. The list tools have a short default; d365_query and the get tools return every column without one.
• Paging: page_size rows per page (default 50). When more rows exist the answer has @odata.nextLink; call d365_next_page with the same entity set and the part of the link after ?, unchanged. For a short answer, set a small page_size: Dataverse ignores $top whenever a page size is requested, so the tools page instead. Pass the same page_size to d365_next_page as to the first call. Dataverse has no $skip.
• d365_fetchxml_query runs FetchXML for joins and aggregates; page it with <fetch page="2" count="50">. d365_query takes apply for simple OData aggregates.

Writing

• Create tools return the new row. Lookups are set with "<navigation property>@odata.bind": "/<entity set>(<id>)", e.g. "[email protected]": "/accounts(<id>)"; the dedicated tools do this for the common ones (account_id, regarding_*_id).
• Update tools change only the columns given and send If-Match, so they never create a row by accident. Pass the row's @odata.etag from the last read to refuse the change when someone else edited it meanwhile (412), or leave the default *.
• d365_qualify_lead closes a lead and creates account, contact and opportunity from it; d365_win_opportunity and d365_lose_opportunity close an opportunity. These change the sales pipeline and are reversed only by hand in Dynamics: ask the user before each one.
• Confirm every create and update with the user.

Switched off at install: d365_delete_account, d365_delete_contact, d365_delete_lead, d365_delete_opportunity, d365_delete_record. A deletion can cascade to related rows depending on the relationship; turn these on per tool only if the AI should delete data.

Limits: Dataverse allows 6,000 requests per user in 5 minutes and a combined execution time of 20 minutes per 5 minutes; beyond that it answers 429 with Retry-After. A page holds at most 5,000 rows.

Common errors

• 401: the authorization was revoked, the client secret expired, or the token was issued for another environment (after changing DYNAMICS_ORG_HOST). Click Authorize with Provider again.
• 403 with 0x80040220 (SecLib::AccessCheckEx) or "principal user is missing privilege": the user's security role lacks that privilege for the table.
• 401 or 403 right after signing in, on every call: the user is not a member of this environment, or has no licence there.
• 404 0x80040217 "Does Not Exist": the id is wrong or the row was deleted. 404 "Resource not found for the segment": the entity set name is wrong (plural, as d365_list_tables shows it).
• 400 "Could not find a property named": a column logical name is misspelled, or a lookup was written without @odata.bind.
• 412: the row changed since the etag was read; read it again and retry.

Microsoft's own MCP server: Dataverse also offers an MCP server at /api/mcp, which an administrator must turn on and to which every client app must be added as an allowed client in the Power Platform admin center. This connector uses the Web API instead, so it works in any environment with the user's normal sign-in.