Amplify's AI Assistant can be exposed to Microsoft 365 Copilot as a custom federated connector using the Model Context Protocol (MCP). Once connected, Copilot users can ask questions about their Amplify data — initiatives, benefits, costs, RAID items, tasks — directly from Copilot chat.

Setup has three parts:

1. In Amplify — collect the MCP connection details (Administrator).
2. In Microsoft — register the OAuth connection and create the connector (Microsoft 365 Global or AI Administrator).
3. In Copilot — each end user connects and authenticates once (Premium Copilot Licence).

Prerequisites

• Administrator privileges in Amplify.
• Global Administrator or AI Administrator role in Microsoft 365.
• Access to the Teams Developer Portal and the Microsoft 365 admin center.
• A Microsoft 365 Copilot licence for each end user who will use the connector.

Step 1: Collect the MCP connection details in Amplify

All of the values Microsoft asks for are found in one place in Amplify.

• Click your avatar in the top right corner.
• Click Administration in the menu.
• Go to Authentication in the side menu.
• Scroll to the AI Assistant (MCP) OAuth section.

From this section, gather the following:
 

MCP Server URL

Copy the MCP Server URL. You will paste this into Microsoft as the connector's Base URL. Keep it on your clipboard or in a scratch note — you will need it in Step 2.

Allow DCR

Turn on Allow DCR (Dynamic Client Registration). This lets Microsoft register itself with Amplify automatically, rather than you creating credentials by hand.

Client ID

If the Microsoft setup process asks for a Client ID, copy it from this section.

Client Secret

If the Microsoft setup process asks for a Client Secret, copy it from this section.

Redirect Whitelist URL

Add the following URL to the Redirect Whitelist, then click Save:

https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect

If authentication fails at the end of Step 3 with a redirect or callback error, add this URL as well:

https://global.consent.azure-apim.net/redirect

Step 2: Set up the connector in Microsoft

The Microsoft-side configuration is documented by Microsoft and may change. Follow their current instructions here: Set up custom federated connectors for Microsoft 365 Copilot

At a high level, the process has two stages. Use the Amplify values from Step 1 where indicated.

Stage 1 — Register the OAuth connection (Teams Developer Portal)

1. Sign in to the Teams Developer Portal.
2. Go to Tools > OAuth Client Registration.
3. Select + New OAuth connection.
4. Give the connection a name your users will recognise, for example Amplify.
5. Enter the Client ID and Client secret copied from Amplify in Step 1.
6. Confirm the redirect URI is https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect — this is the URL you whitelisted in Amplify.
7. Select Save, then copy the OAuth client registration ID that Microsoft generates. You need it in Stage 2.

Stage 2 — Create the connector (Microsoft 365 admin center)

1. Sign in to the Microsoft 365 admin center.
2. Go to Copilot > Connectors in the left pane.
3. Open the Gallery tab, and under Created by your org select Add on the Create a new connector tile.
4. Under Connect to MCP server, select Add.
5. Enter a Display name. This is the name your end users will search for in Copilot, so choose it carefully and tell your users what it is.
6. Enter the Amplify MCP Server URL from Step 1 as the Base URL.
7. Enter the OAuth client registration ID from Stage 1.
8. Select Save.

You can then use Staged rollout to release the connector to a small group of test users before deploying it to everyone.

Step 3: Connect Amplify in Copilot (end users)

Share these steps with your users once the connector has been deployed to them. Each user does this once.

1. In Copilot, click the settings cog in the bottom right of the sidebar, next to your username.
2. In the Chat Settings modal, select Sources in the sidebar.
3. Search for the connector by the name your administrator gave it in Step 2.
4. Click Connect.
5. Click Continue to [connector name].
6. Sign in on the Amplify login page that appears.
7. Click Allow to grant read access.

The connector now shows as connected, and Amplify can be used as a source in Copilot chat.

Troubleshooting

• The connector doesn't appear when the user searches in Sources. Confirm the user is in scope for the staged rollout, that the connector is Enabled, and that at least 15 minutes have passed since the last change. Check the user is searching for the exact display name set in Step 2.
• Sign-in works but the connection fails at the end. This is almost always the redirect URL. Return to the AI Assistant (MCP) OAuth section in Amplify and confirm `https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect` is in the redirect whitelist. If it is, add `https://global.consent.azure-apim.net/redirect` as well and have the user try again.
• Registration or token errors. Confirm Allow DCR is still enabled in Amplify, and that the Client ID and Client Secret entered in the Teams Developer Portal match the current values in Amplify.
• The user connects but sees no Amplify data. Check the user's permissions in Amplify. Copilot can only return what that user can already see.

If the problem persists, contact Amplify Support with the connector display name, the Amplify instance URL, and the exact error message shown to the user. Do not include the client secret.