> ## Documentation Index
> Fetch the complete documentation index at: https://conductorone-sathya-add-agent-guardrails-doc.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Connect Copilot Studio to C1
> Build a Copilot Studio agent that calls governed tools through C1, then publish it to Microsoft 365 Copilot for your whole organization.
Build an agent in Copilot Studio that calls the tools your IT team approved for you, using your own identity, with every call authorized and logged by C1. Then publish the agent so your colleagues use it from Microsoft 365 Copilot and Teams.
## What you'll do
The full path from empty agent to an agent your whole organization can use has three stages, and the middle one involves your Teams admin.
1. **Build it.** Create the agent, add C1 as a tool, authorize the connection, and write the agent's instructions.
2. **Publish it.** Publish the agent, connect the Microsoft 365 Copilot channel, and request admin approval to reach everyone.
3. **Approve and use it.** Your Teams admin approves the app, you confirm it went through, and people add the agent in Microsoft 365 Copilot.
You don't need a C1 admin role for any of this. You do need a Teams admin for stage three if you want the agent available to the whole organization.
## Before you begin
* AI access management must be enabled for your tenant. See [Enable AI access management](/product/admin/enable-ai-access-management).
* A Copilot Studio environment you can create agents in, from your Power Platform admin.
* Access in C1 to the tools you want the agent to call. Request it from the C1 catalog and an approver grants it. See [Find and request AI tool access](/product/how-to/ai-tools#find-and-request-ai-tool-access).
* A Teams admin who can approve the app, if you're publishing to everyone in your organization.
## Get your C1 MCP server URL
Every connection to C1 uses the same URL, scoped to your tenant. Copy it before you open Copilot Studio.
In C1, click your profile menu and click **AI & API**.
On the **AI connections** tab, copy the **MCP server URL**.
```text theme={"theme":{"light":"css-variables","dark":"css-variables"}}
https://-mcp.conductor.one/v1
```
You now have the URL to paste into Copilot Studio's MCP onboarding wizard.
## Create a blank agent
Start from a blank agent so nothing is configured that you didn't choose. If you already have an agent you want to give governed tools to, skip to [Add C1 as a tool](#add-c1-as-a-tool).
Sign in to [Copilot Studio](https://copilotstudio.microsoft.com/).
Switch to the environment you want to build in.
Copilot Studio creates the agent in whichever environment is selected, and you can't move the agent to a different one later. If you see an error that you don't have permissions to any environments, ask your Power Platform admin for access to one.
Go to the **Agents** page and select **Create blank agent**.
To set the primary language, solution, or schema name at the same time, select the down arrow next to **Create blank agent**, select **Advanced create**, and select **Confirm and create**. You can't change the primary language after the agent is created.
Enter a name and description for the agent, then select **Save**.
The name has a 42-character limit and can't contain angle brackets. The description has a 1,024-character limit.
Copilot Studio provisions the agent and opens its **Overview** page.
## Add C1 as a tool
C1 appears to Copilot Studio as an MCP server. Add it through the MCP onboarding wizard.
Go to the **Tools** page for your agent.
Select **Add a tool**, then select **New tool**.
Select **Model Context Protocol**. The MCP onboarding wizard appears.
Enter a **Server name** and **Server description**, and paste your C1 MCP server URL into **Server URL**.
Write a clear description, because the agent's orchestrator uses it to decide when to call C1. For example: "Governed access to approved company tools, authorized per user by C1."
For the authentication type, select **OAuth 2.0**, then select **Dynamic discovery** as the type.
Select **Create**, then select **Next**.
On **Add tool**, select **Create a new connection**, then select **Add to agent**.
C1 is now added as a tool, and the agent needs an authorized connection before it can call it.
## Authorize the connection
The first time the agent calls a C1 tool, C1 asks you to sign in and confirm the connection.
Test the agent and ask it to list its available tools.
When the sign-in prompt appears, sign in to C1.
Review the connection details and click **Allow**.
The agent now lists the tools your access profiles grant you. If the list is empty, your access hasn't been granted yet.
Some downstream services require your own credentials rather than a shared account. Authorize those from your profile menu under **AI & API > MCP connections > Connect**. See [When a tool needs your own credentials](/product/how-to/ai-tools#when-a-tool-needs-your-own-credentials-per-user-oauth).
## Write the agent's instructions
Instructions tell the agent how to behave and when to use the tools it has.
On the agent's **Overview** page, find the **Instruction** section and select **Edit**.
Describe what the agent does, and when it should use its tools.
Select **Save**.
Test the agent and adjust the instructions until it behaves the way you want.
The agent now follows these instructions when deciding when to call C1.
## Publish the agent
Publishing makes the current version of the agent available to be used. On its own it doesn't put the agent in front of anyone; connecting the channel and sharing the agent do that.
Select **Publish** and confirm.
You must publish at least once before anyone, including you, can use the agent in Microsoft 365 Copilot or Teams.
## Turn on the Microsoft 365 Copilot channel
Publishing doesn't connect the agent to Microsoft 365 Copilot. Connect the channel yourself, and check the Microsoft 365 setting while you're there. This is the step that decides whether the agent appears in Microsoft 365 Copilot or only in Teams.
Open your agent in Copilot Studio and select **Channels** on the top menu bar.
Select the **Teams and Microsoft 365 Copilot** tile. The configuration panel appears.
Under **Turn on Microsoft 365**, confirm **Make agent available in Microsoft 365 Copilot** is selected.
It's selected by default. If you clear it, the agent is available in Teams only.
Select **Add channel**.
Select **See agent in Teams**, then select **Add** to install the agent for yourself.
The agent is now installed for you in both Teams and Microsoft 365 Copilot. Nobody else can use it yet.
## Request admin approval to publish to everyone
To make the agent available to your whole organization, submit it for your Teams admin to approve. Approved agents appear in the **Built for your org** section of the Teams app store and the **Built by your org** section of the Microsoft 365 Agent Store.
In the **Teams and Microsoft 365 Copilot** configuration panel, select **Availability options**.
If the agent shows **Added to Teams** under **Show to my teammates and shared users**, remove it.
An agent left in both places appears twice in the app store.
Select **Show to everyone in my org**.
Review the submission requirements, then select **Submit for admin approval**.
Select **Yes** to confirm.
The agent goes to your Teams admin for review, and the submission status appears in the panel.
After submitting, don't set the agent's access to anything narrower than everyone in your organization. If you do, people can install the agent from the app store and then find they can't chat with it.
While you wait, keep in mind that only one person can hold a submission at a time. Until your admin approves or rejects it, nobody else can resubmit the agent.
## Approve the agent in the Teams admin center
This section is for your Teams admin. Send it to them along with the agent's name.
The submitted agent arrives in the Teams admin center as a custom app awaiting approval. Until an admin publishes it, its status is **Blocked** and no one in the organization can use it.
Sign in to the Teams admin center and go to **Teams apps** > **Manage apps**.
The **Pending approval** widget at the top of the page shows apps waiting for review.
Find the agent in the table.
A newly submitted app shows a **Publishing status** of **Submitted** and a **Status** of **Blocked**. Sort the **Publishing status** column in descending order to find it quickly.
Select the agent's name to open its details page, and review the **About** tab.
The tab shows the description, status, who submitted it, and the app ID.
In the **Publishing status** box, select **Publish**.
The **Publishing status** changes to **Published** and the **Status** changes to **Allowed**. Everyone in the organization can now find the agent in the **Built for your org** section of the Teams app store.
By default every user in the organization can access the app. To narrow that, assign an app permission policy. To put the agent directly in people's Teams app bar instead of making them search for it, assign an app setup policy.
## Confirm the agent is configured
Once your admin has approved the agent, check that everything landed before you tell people to use it.
In Copilot Studio, open **Channels** > **Teams and Microsoft 365 Copilot** > **Availability options** and select **Refresh**.
The status changes to **Approved**.
Confirm **Make agent available in Microsoft 365 Copilot** is still selected in the channel panel.
Open the agent and ask it to list its tools, to confirm the C1 connection still works after publishing.
If the status still shows as pending after your admin has published the app, the Teams app store may be caching. Refresh your browser, or sign out of the Teams desktop app and back in.
## Use the agent in Microsoft 365 Copilot
Each person who wants the agent adds it themselves.
Open Microsoft 365 Copilot.
Find the agent in the agent list, or add it from the **Built by your org** section of the Microsoft 365 Agent Store.
Enter **@**, select the agent from the list, and ask a question.
When C1 asks you to sign in, sign in and select **Allow**.
Everyone authorizes C1 with their own identity, so each person sees only the tools their own access grants them. Sharing the agent doesn't share your access.
### Update the agent later
You can keep improving the agent after it's approved. Changes to the instructions or other content only need a republish: select **Publish** again and everyone gets the update. You only need to resubmit for admin approval if you change the agent's details, such as its name, description, or icon.
## Troubleshoot Copilot Studio connection errors
| Symptom | Cause | Fix |
| :------------------------------------------------------- | :---------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **AI & API** isn't in your C1 profile menu | AI access management isn't enabled for your tenant. | Ask your C1 admin to contact the C1 support team. |
| **Model Context Protocol** isn't offered as a tool type | The agent uses classic orchestration. | Turn on generative orchestration on the agent's **Settings** page, under **Generative AI** > **Orchestration**. If the option isn't there, your Power Platform admin turned it off for the environment. |
| The wizard can't reach or register with the C1 URL | A typo in the URL, or a Power Platform data policy blocking connectors. | Check the URL. If it's correct, ask your Power Platform admin whether a data policy applies. |
| The agent connects but lists no tools | Your access hasn't been granted. | Request it from the C1 catalog. See [How to request AI tools](/product/how-to/ai-tools). |
| A tool call is denied part way through a working session | Your access was revoked, or a just-in-time grant expired. | Submit a new request to renew. |
| Tools from one service fail while others work | That service needs your own credentials. | Authorize it under **AI & API > MCP connections**. |
| You don't have permissions to any environments | You have no Copilot Studio environment. | Ask your Power Platform admin for access to one, or to create one. |
| The agent doesn't appear in Microsoft 365 Copilot | The channel setting is off, or the agent was never published. | Select **Make agent available in Microsoft 365 Copilot**, then publish. |
| The agent is approved but isn't in the app store | The Teams app store is caching. | Refresh your browser, or sign out of the Teams desktop app and back in. |
| Colleagues can install the agent but can't chat with it | The agent's access is narrower than the app store audience. | Set access to everyone in your organization. |
## Frequently asked questions about connecting Copilot Studio
No. Anyone with a C1 account can build an agent and authorize it. Enabling AI access management and granting tool access are C1 admin tasks done separately. Publishing to your whole organization needs a Teams admin.
Only the tools your access profiles grant you. C1 checks every tool call against your granted access, so two people using the same agent can see different tools.
Yes, with a smaller audience. Use **Copy link** to share an installation link, or **Show to my teammates and shared users** to list the agent in the **Built with Power Platform** section of the Teams app store. Both reach only people you've shared the agent with. Reaching everyone in the organization requires admin approval.
The next tool call returns a denied error, and in-flight calls finish. Nothing on your machine is deleted; only new tool calls are affected. See [What happens if your access is revoked or expires](/product/how-to/ai-tools#what-happens-if-your-access-is-revoked-or-expires).
Yes. When you add C1 to another agent in the same environment, the **Add tool** dialog offers your existing connection instead of making you create a new one.
Yes. Every tool call is logged with full identity context. See [Audit AI tool usage](/product/admin/audit-ai-tool-usage).