Use this guide to add Adapt's read-only MCP server as a custom federated connector in Microsoft 365 Copilot. A Microsoft 365 administrator creates and deploys the connector; each user then connects it with their own Adapt account.
Before you begin
- Confirm that the people who will use the connector have the required Microsoft 365 Copilot licences and that your tenant permits custom federated connectors.
- Use an account that can manage Copilot connectors in the Microsoft 365 admin centre. The administrator also needs an Adapt Lumia account to authorise the connector.
- Contact Adapt Support for your MCP server URL and the Reference ID for Adapt's Microsoft OAuth registration. Enter this Reference ID in the Microsoft connector wizard.
Set up the connector as a Microsoft 365 administrator
- In the Microsoft 365 admin centre, open Copilot → Connectors → Gallery → Created by your org. Under Create a new connector, select Add, then select Connect to MCP server.
- Enter a display name and the MCP server URL supplied by Adapt as the Base URL. Complete the required developer, website, privacy policy, and terms of use fields. Choose OAuth 2.0 and enter the Reference ID supplied by Adapt below.
| Field | Value |
|---|---|
| Display name | adapt-lumia |
| MCP endpoint URL | https://api.theadaptway.com/mcp |
| Developer name | Adapt |
| Website URL | https://lumia.theadaptway.com |
| Privacy policy URL | https://lumia.theadaptway.com/about/privacy-terms-conditions?section=1 |
| Terms of use URL |
https://lumia.theadaptway.com/about/privacy-terms-conditions?section=0
|
| Authentication type | OAuth 2.0 |
| Reference ID | MGRjNTViMDUtNGZmNi00OGEwLTgwYjQtM2RmMTkyYTMyZGVlIyMwMWQzZmQ0YS01MTc3LTRmYjktOWE5OS1lZDMwMTg1MTUwMGQ= |
Note that the Reference ID is shareable configuration, not an ADAPT bearer token or the client secret. Any Microsoft 365 organization permits use of the Microsoft authentication configuration; it does not automatically deploy the connector, grant access to all ADAPT organisations, or establish a Microsoft-tenant-to-ADAPT-organisation mapping. ADAPT still enforces the signed-in user's existing permissions.
- Select Authorize. Sign in to Adapt Lumia if prompted, review the Microsoft 365 Copilot access request, and select Allow access. The connector cannot be created until this authorisation succeeds.
- When the creation button becomes available, select Create and then Done on the success screen. Your Microsoft interface may label the creation action Save.
- In Your connections, enable the connector or stage its rollout to the intended users or groups according to your tenant policy. Microsoft advises that connector changes can take up to 15 minutes to take effect.
Connect as a Copilot user
- Open Microsoft 365 Copilot and select Settings from your profile menu.
- Open Sources, find the connector name chosen by your administrator, and select Connect. If it is not listed, ask your administrator to check the rollout and allow time for the change to take effect.
- Select Continue to Adapt Lumia. Sign in with your own Adapt account and approve the access request.
- Confirm that Adapt appears under your connected sources. You can disconnect it from Copilot's Sources settings.
Access and verification
Adapt's MCP tools are read-only. Each connection uses the signed-in person's existing Adapt permissions, including their organisation access. The Reference ID does not grant access to Adapt data by itself.
A Connected status confirms the account connection but does not prove that Copilot can use an Adapt tool. Test a question that should retrieve Adapt information and check the result. If the source is unavailable or the test fails, ask your Microsoft 365 administrator to check the connector's rollout and licensing, then contact Adapt Support.
For more detail, see Microsoft's custom federated connector setup guide and connector licensing prerequisites.
Core adapt principles