> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://knowledge.buildagil.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Connection to Microsoft Copilot

||| This role is a preview version. Therefore, it may not behave as expected, or the role may still change. For the time being, this role is available exclusively to project administrators.

* [Setting Up the Connection](#3-setting-up-the-connection)
* [Testing the Connection](#3-testing-the-connection)
* [Terms of Use](#3-terms-of-use)

| The connection between Microsoft Copilot and buildagil is established via the buildagil openCDE MCP Server. For information, see the following article: [Buildagil openCDE MCP Server](/en/article/buildagil-opencde-mcp-10ffv05/).

||| Please note the [Terms of Use](#3-terms-of-use) when using external AI environments. In particular, handle content from buildagil responsibly and ensure adequate data protection. Buildagil has no control over the processing of content outside of buildagil (including external AI environments).

### Setting Up the Connection
The buildagil openCDE MCP Server can be used in Microsoft Copilot both as a connector and as an agent. The following section describes how to set it up as a connector.

| A client ID and a client secret are required for the connection; these can be requested from Support. In the near future, you will be able to manage the connection yourself. Additionally, administrator permissions in the Microsoft 365 Admin Center and access to the Teams Developer Portal are required.

OAuth 2.0 authentication is first configured in the Teams Developer Portal. To do this, register an OAuth client using the client ID and client secret. After saving, a registration ID is displayed, which is required to set up the connector. For detailed instructions on registering the OAuth client, see the following Microsoft article: [Set up custom federated connectors](https://learn.microsoft.com/de-ch/microsoft-365/copilot/connectors/set-up-custom-federated-connectors#oauth-20).

The connector is set up in the Microsoft 365 Admin Center under "Copilot" and "Connectors." To do this, in the "Gallery" under "Created by your organization," select the "Add" option next to the "Create a new connector" entry.

![](https://storage.crisp.chat/users/helpdesk/website/-/d/2/9/f/d29f517da520580/connector-hinzufugen_j5i0o.png)

Next, under "Custom Connector," select the "Connect to MCP Server" option.

![](https://storage.crisp.chat/users/helpdesk/website/-/d/2/9/f/d29f517da520580/mit-mcp-server-verbinden_jtyp6a.png)

Next, assign a "Display Name," enter a "Description" for the data source, and enter the following address in the "MCP Endpoint URL" field: `https://openapi.buildagil.com/mcp`.

![](https://storage.crisp.chat/users/helpdesk/website/-/d/2/9/f/d29f517da520580/generelle-informationen-zum-cu_hwx62h.png =1000x903)

In addition, enter the "Developer Name," "Website URL," "Privacy Policy URL," and "Terms of Service URL." For "Authentication Type," select "OAuth 2.0" and enter the registration ID you copied earlier in the "Reference ID" field. After authorizing and confirming the notification, the connector is saved.

![](https://storage.crisp.chat/users/helpdesk/website/-/d/2/9/f/d29f517da520580/details-zur-datenquelle-und-au_1n7ye11.png =1000x745)

> Set up a connector, Add a Copilot connector, Microsoft 365 Admin Center, Copilot connectors, Custom connector, Connect to MCP server, MCP endpoint URL, openapi.buildagil.com/mcp, Authentication, OAuth 2.0, Reference ID, Registration ID, Teams Developer Portal, Client ID, Client Secret, Request credentials, Contact support, Administrator rights
### Testing the Connection
Once setup is complete, the connector will appear in the Microsoft 365 Admin Center under "Your Connections." To make it available to users, it must be deployed there to the desired users or groups. Users can then sign in with their buildagil account in Copilot under "Settings" and "Sources."

![](https://storage.crisp.chat/users/helpdesk/website/-/d/2/9/f/d29f517da520580/mit-mcp-quelle-verbinden-in-ei_1t5vp6j.png =700x566)

To use the connector in Copilot, "Work IQ" must be enabled. There, you can enable or disable all connected sources, including buildagil. If "Work IQ" or the buildagil source is not enabled, no content from buildagil can be found. To review this, you can ask a question about buildagil in the chat, such as “What projects do I have on buildagil?”

![](https://storage.crisp.chat/users/helpdesk/website/-/d/2/9/f/d29f517da520580/verbindung-testen-mit-aktivier_1yny5jc.png)

| Microsoft Copilot can be opened and used directly from buildagil via the AI assistant. For more information, see the following article: [AI Assistant](/en/article/ki-assistant-174zczu/)

> Test connection, Check connection, Connector connected, Connector status, Your connections, Deployment, Sources, Work IQ, Enable Work IQ, Turn source on and off, Connection not working, Copilot can't find any data, Test question in chat, Artificial intelligence
### Terms of Use
The Terms of Use for [Buildagil openCDE MCP Servers](/en/article/buildagil-opencde-mcp-10ffv05/) apply.