Dynamics 365 (Dataverse)

Connecting the Dataverse MCP server lets your agents search, query and change the data in a Dataverse environment, including the environment behind your Dynamics 365 apps. Each Dataverse environment has its own server, so you type your environment's host when you connect.

Read How MCP Servers Work in Outermind first if you have not connected an MCP server before.

Before you start

• A Dataverse environment and its host name, as it appears in the environment's URL, for example yourorg.crm.dynamics.com. In some regions the crm part carries a number.
• A Power Platform admin for that environment, to allow Outermind in; see Prepare Dataverse.
• A Microsoft work account with access to the environment. The connection acts as the person who signs in, so agents can do what that person's Dataverse security roles allow.
• The Outermind application (client) ID, which Outermind support provides on request.
• A tenant admin in Outermind to run the wizard and grant the tools.
• Microsoft billing. Calls may use Copilot Credits; see Billing notes.

Prepare Dataverse

Outermind signs in with its own multi-tenant Microsoft Entra application, so you do not register an application. A Power Platform admin must allow it into each environment you want to connect:

1. Ask Outermind support for the Outermind application (client) ID.

2. In the Power Platform admin center, go to Manage > Environments, select the environment, then Settings. Expand Product, select Features, and find the Dataverse Model Context Protocol section. Under Step 1, turn on Allow MCP clients to interact with Dataverse MCP server (GA version) if it is not already on.

3. Under Step 2 in that section, click Go to Advanced Settings to open the Allowed MCP Clients table. Click New and fill in the four required fields:

   • Name: any label, for example Outermind.
   • Unique Name: a name starting with a valid publisher customization prefix, for example new_outermind. The unprefixed name outermind is refused when you save.
   • Application Id: the Outermind application (client) ID from step 1.
   • Is Enabled: Yes. It defaults to No.

   Click Save & Close.

Repeat steps 2 and 3 for every environment you connect. Depending on your organisation's Microsoft Entra consent settings, a Microsoft Entra admin may also need to approve the Outermind application the first time someone signs in.

Connect in Outermind

1. Open the Capabilities hub, click MCP Servers under Tool Management, and click Add MCP server.
2. Under Known server, pick the Dynamics 365 (Dataverse) entry (shown with the host *.dynamics.com). The wizard shows "A Power Platform admin must allow Outermind's client ID for this environment." and the expected sign-in is OAuth sign-in. Optionally edit Purpose, the one-line description agents see beside this server.
3. Instead of an endpoint, the wizard asks for an Organisation host. Type your environment's host only, such as yourorg.crm.dynamics.com, with no https:// and no path. Outermind builds the endpoint https://yourorg.crm.dynamics.com/api/mcp from it, and refuses a host that is not under dynamics.com. Click Next.
4. On Credential, the wizard says "Outermind signs in with its own application registered with this provider." Click Connect, sign in with your Microsoft work account, and approve. Microsoft shows the Permissions requested page for Outermind - Dataverse MCP on every connection, including a reconnect.
5. On Summary, Outermind discovers the environment's tools and makes them active. Under Grant tools to agents, pick an agent to choose an access level for each one; to leave a tool out, use the connection page afterwards.

To connect another environment, add a second connection with that environment's host and a display name that tells the two apart.

What your agents can do

The server offers 15 generally available tools, including:

Tool	What it does
search_data	Searches the data in the environment
search	Searches the environment
describe	Describes a table and its columns
read_query	Runs a read-only SQL query
create_record	Creates a row
update_record	Updates a row
delete_record	Deletes a row
create_table	Creates a table
update_table	Changes a table's definition
delete_table	Deletes a table
upsert_skill	Creates or updates a skill
delete_skill	Deletes a skill

plus tools to upload and download files.

Read actions start at tier low, and every other action starts at high; see Risk tiers.

warning

create_table, update_table and delete_table change your environment's structure, not just its data. Keep them at tier high, and exclude them on the connection page unless agents genuinely need them.

What is not available

• Many-to-many associations. The earlier built-in Dynamics 365 integration could explicitly associate two records in a many-to-many relationship; the MCP server cannot.
• Expanding related records in one call. The earlier integration could fetch a record with its related records expanded ($expand); with the MCP server, the agent reads the related records separately.
• Other Microsoft MCP servers. The Dynamics 365 Sales MCP server and the Business Central MCP server are separate products and are not covered by this connection.

Billing notes

Microsoft charges Copilot Credits for each call made to the Dataverse MCP server from outside Copilot Studio, which includes calls from Outermind agents, unless your licensing includes Dynamics 365 Premium or a Microsoft 365 Copilot user subscription license (USL). Check your Microsoft licensing before you give agents broad access.