Set up Microsoft Copilot Studio for Control MCP

Fix a Copilot Studio environment where Create agent keeps loading, then add Control as an MCP tool.

Use this page if you want to use Control in Microsoft Copilot Studio and the Copilot Studio side is not ready yet. The most common symptom: you can open Copilot Studio, but when you select Create agent, the page keeps loading and nothing appears.

This almost always comes from Microsoft setup, not from Control. Work through the checks below in order. Most teams are done after the first two.

Before you start

You need:

• a Microsoft 365 work account in your organization’s tenant;
• access to the Power Platform admin center, or a colleague who has it; and
• access to the Control workspace you want the agent to query.

Quick checks

1. You have a Copilot Studio license, a trial, or a billing plan. Opening the Copilot Studio site does not require one. Creating an agent does.
2. The environment has Dataverse. Copilot Studio stores agents in Dataverse.
3. Copilot Studio is open in the environment you prepared. The environment name is shown in the top-right corner of Copilot Studio.
4. You have the right role in that environment. You need System Administrator or Environment Maker.

Causes and resolutions

No Copilot Studio license, trial, or billing plan

How to confirm: Nobody has assigned you a Copilot Studio license, you have not started a trial, and no pay-as-you-go plan is linked to the environment.

Resolution: Choose one of these options.

Trial (fastest)

1. Open aka.ms/TryCopilotStudio and sign in with your work account.
2. Accept the trial.
3. Sign out of Copilot Studio and sign in again.

If you see a message that your administrator has turned off self-service sign-up, ask a Microsoft 365 administrator to start the trial in the Microsoft 365 admin center under Billing → Purchase services and assign it to you.

A trial lets you build an agent and test it in the Copilot Studio test pane. Publishing the agent to Teams or Microsoft 365 Copilot requires a paid license.

Pay-as-you-go

Pay-as-you-go bills Copilot Studio usage to an Azure subscription instead of a per-user license.

Before you start, check that:

• the environment is a Production or Sandbox environment. Developer environments cannot be linked, and in some tenants the default environment cannot be linked either;
• you are Owner or Contributor on an Azure subscription; and
• the Microsoft.PowerPlatform resource provider is registered on that subscription (Azure portal → your subscription → Resource providers).

Then:

1. In the Power Platform admin center, open Licensing → Pay-as-you-go plans and select New billing plan.
2. Choose the Azure subscription and resource group.
3. Choose the same region as your environment, for example Europe or Switzerland.
4. Select the environment and save.
5. Wait 5 to 10 minutes, then sign out of Copilot Studio and sign in again.

You may also need a Copilot Studio User License, which is free. A Microsoft 365 administrator can add it under Billing → Purchase services and assign it to the people who build agents.

Add a budget in Azure Cost Management → Budgets to receive spending alerts while testing. Budgets do not cap or stop pay-as-you-go charges.

Verify: Sign in to Copilot Studio again. Create agent opens the agent builder.

The environment has no Dataverse

How to confirm: In the Power Platform admin center, open Manage → Environments and select the environment. If the page shows an Add Dataverse card, the environment has no Dataverse.

Resolution:

1. Select Add Dataverse.
2. Set the language and currency. You cannot change the currency later.
3. Set Enable Dynamics 365 apps to No. Copilot Studio does not need them, and this choice cannot be undone.
4. Save and wait. Setup usually takes 5 to 15 minutes.

Verify: Refresh the environment page. The Add Dataverse card is replaced by an environment URL, and Recent operations shows the operation as succeeded.

Everyone in your organization can build in the default environment. If the agent should be visible only to a small group, create a separate Production or Sandbox environment for it instead of adding Dataverse to the default environment.

Copilot Studio is open in a different environment

How to confirm: Copilot Studio opens the default environment unless you choose another one. Check the environment name in the top-right corner.

Resolution: Select the environment name and switch to the environment that has Dataverse and a license or billing plan.

Verify: The environment you prepared is shown in the top-right corner, and Create agent opens the builder.

The environment is still being set up

How to confirm: The environment or its Dataverse was created in the last half hour. The first time Copilot Studio opens in an environment, it installs its own components in the background.

Resolution: Wait 10 to 30 minutes and try again. In the Power Platform admin center, open the environment and check Resources → Dynamics 365 apps. Items that still show Installing mean setup is not finished.

Verify: No items show Installing, and Create agent opens the builder.

Your role in the environment is missing

How to confirm: In the Power Platform admin center, open the environment and select Environment maker → See all or Environment admin → See all. Your account is not listed. A Microsoft 365 or tenant admin role does not add you automatically.

Resolution: Ask an environment administrator to give you the Environment Maker or System Administrator role.

Verify: Sign out and in again. Create agent opens the builder.

The browser blocks Copilot Studio

How to confirm: Copilot Studio works for a colleague on the same environment but not for you.

Resolution: Try Microsoft Edge or Google Chrome in a private window with ad blockers and privacy extensions turned off. Allow third-party cookies for Microsoft sites.

Verify: Create agent opens the builder in the private window.

Find the exact cause in the browser

If you are still unsure which cause applies, the browser shows it:

1. Open the browser developer tools (Cmd+Option+I on Mac, F12 on Windows) and select the Network tab.
2. Clear the Network log, then select Create agent in Copilot Studio.
3. Find the failed request triggered by selecting Create agent and open its response. Ignore unrelated asset or telemetry failures.

What the response shows	Most likely cause
403 with a message about a license	No license, trial, or billing plan
A message about provisioning, or status 409	The environment is still being set up
401 or 403 with a message about a security role	Your role in the environment is missing
A message about Dataverse or the organization not being found	The environment has no Dataverse

Add Control to your agent

When Create agent works:

MCP requires generative orchestration. In your agent’s Settings → Generative AI, under Orchestration, set Use generative AI orchestration for your agent’s responses? to Yes.

1. In Control, copy your workspace server URL from Data outputs → MCP Server.
2. In Copilot Studio, open your agent’s Tools page and select Add a tool → New tool → Model Context Protocol.
3. Enter a server name and description, paste the workspace server URL, and choose OAuth 2.0 → Dynamic discovery.
4. Select Create, then Next to open the connection dialog.
5. Create a new connection, sign in with your Control account when prompted, and approve access.
6. Select Add to agent.
7. Open the test pane and ask a narrow read-only question, for example: “List the entities in my Control workspace.”

If dynamic discovery fails with a registration or authorized-party error, ask a Control administrator to confirm that dynamic client registration is enabled for your environment. If your setup requires a pre-registered OAuth application, choose Manual and use the client credentials and endpoint details supplied by your administrator. Follow Microsoft’s manual OAuth setup instructions, including registering the callback URL with the OAuth application.

Menu labels in Copilot Studio change from time to time. If a step looks different, see Connect an AI client with MCP for the connection details Control expects.

Collect information for support

If Create agent still does not open, contact your Microsoft administrator or Microsoft support first, because the cause is on the Microsoft side. If Copilot Studio works but Control does not connect, email [e-mail] with:

• the environment type (Default, Production, or Sandbox) and region;
• whether you use a trial, a license, or pay-as-you-go;
• the step that failed; and
• the exact error text, with personal and financial data removed.

Never send access tokens, client secrets, passwords, or unredacted screenshots of financial data.

Related content

• Connect an AI client with MCP
• Troubleshoot Control MCP
• Connect external tools through MCP