Connecting Legatics to Microsoft 365 Copilot lets your team ask questions about live matters from Copilot Chat. Your firm's Legatics System admin and Microsoft 365 admin set it up once. Each user then signs in with their own Legatics account.
Setup has five steps. Steps 1 to 3 are done once for the whole firm. Steps 4 and 5 are done by each user.
Who | What |
Legatics System admin | Create a connected app in Legatics and copy the Client ID and secret |
Microsoft 365 admin | Register an OAuth client for Legatics in the Teams Developer Portal |
Microsoft 365 admin | Add Legatics as a connector and roll it out to users |
Each user | Connect their Legatics account in Copilot Chat |
Each user | Wait 15 minutes, then ask Copilot about their matters |
Before you start
You'll need:
System admin access to the Legatics Administration System
A Microsoft 365 admin who can use the Teams Developer Portal and the Microsoft 365 admin centre
A Microsoft 365 Copilot licence for each user, assigned to the account they normally sign in with
Your firm's Legatics MCP URL:
Region | MCP URL |
Europe |
|
United States |
|
Australia |
|
Note: If your firm uses a dedicated or private Instance, your MCP URL will be different. Contact your Legatics Account Manager to confirm it.
Step 1: Create a connected app in Legatics
In the Legatics Administration System, go to Setup → Integrations and open the Connected apps tab.
Select Create connected app.
Under Application type, leave Confidential client selected.
Enter a Name, for example Microsoft 365 Copilot, and an optional Description.
Under Redirect URLs, add
https://teams.microsoft.com/api/platform/v1.0/oAuthRedirectUnder Select at least one connection type, tick Legatics MCP.
Under Allowed scopes, select Read only. This is the only scope offered for MCP connections.
Select Save.
Copy the Client ID and Client secret. Your Microsoft admin needs both in Step 2.
Note: The client secret is only shown in full once. If you lose it, select Regenerate secret and update the OAuth client registration in Step 2.
Step 2: Register an OAuth client in the Teams Developer Portal
Your Microsoft 365 admin completes this step.
In the Teams Developer Portal, go to Tools → OAuth client registration and select Register client.
Fill in the registration using the values below.
Save the registration and copy its Registration ID (shown as a Reference ID on the connector). You need it in Step 3.
Field | Value |
Registration name | For example Legatics MCP |
Base URL | Your MCP URL, exactly as shown above. No extra path, and no trailing slash |
Restrict usage by app | Any Teams app |
Client ID | From Step 1 |
Client secret | From Step 1 |
Authorization endpoint | For your region, from the sign-in table below |
Token endpoint | For your region, from the sign-in table below |
Refresh endpoint | Same as the token endpoint |
Scope |
|
PKCE | Enabled |
The sign-in addresses depend on your firm's region. They don't follow the same pattern as the MCP URLs.
Region | Authorization endpoint | Token and refresh endpoint |
Europe |
|
|
United States |
|
|
Australia |
|
|
Important: The scope must include legatics_mcp. Without it, users can sign in but Copilot can't load any Legatics tools.
Step 3: Add Legatics as a connector in the Microsoft 365 admin centre
Your Microsoft 365 admin completes this step.
Create a Copilot agent connector for Legatics that points to your MCP URL and uses the Registration ID from Step 2.
In the Microsoft 365 admin centre, go to Copilot → Connectors and check that Legatics appears.
Roll the connector out to the users who should have access.
Important: The MCP endpoint URL in the connector must match the Base URL in the OAuth client registration character for character, including whether there's a trailing slash.
Step 4: Connect your Legatics account
Each user completes this step once.
Open Microsoft 365 Copilot Chat.
Go to … → Settings → Sources.
Find Legatics and select Connect.
You're taken to Legatics. Log in and review the permissions on the consent screen. Legatics MCP should appear as a permission.
Select Authorize. You're returned to Copilot.
Note: Copilot only sees the matters you can see in Legatics.
Step 5: Use Legatics in Copilot
Wait about 15 minutes after connecting. Copilot needs this time to load the Legatics tools.
Open Researcher in Copilot Chat.
Name Legatics in your prompt, for example "Using Legatics MCP, list my active matters."
Note: Copilot can read matters, lists, documents and audit information. It can't create or update anything in Legatics yet, because Microsoft doesn't currently allow write actions on custom MCP connectors.
Having trouble?
Copilot says the Legatics tools are unavailable or that sign-in is required
The scope in the OAuth client registration is probably missing legatics_mcp.
In the Teams Developer Portal, check that the Scope includes
legatics_mcp, for examplelegatics_mcp read_only.In Copilot Chat, go to Settings → Sources, disconnect Legatics and connect it again. This gets a fresh token with the new scope.
Wait about 15 minutes and try again.
If Microsoft adds a space after a comma in the scope field, for example legatics_mcp, read_only, that's fine.
The Authorize button is greyed out on the Legatics login page
The scope is missing from the OAuth configuration. Add legatics_mcp to the Scope field in the OAuth client registration, then sign in again.
Sign-in completes but Copilot never loads any tools
The Base URL in the OAuth client registration probably doesn't match the connector.
In the Teams Developer Portal, go to Tools → OAuth client registration and open the registration the connector's Reference ID points to.
Check the Base URL is exactly your MCP URL, with no extra path, and matches the connector's MCP endpoint URL exactly.
Check Restrict usage by app is set to Any Teams app.
Sign in again from the connector.
You see a redirect error after logging in
Check that the redirect URL on the connected app in Legatics is exactly https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect.
Legatics only offers the Read only scope
That's expected. Read only is the only scope for MCP connected apps. The legatics_mcp scope is entered on the Microsoft side, in the OAuth client registration.
Copilot can read but can't make changes
That's expected. Microsoft doesn't currently allow write actions on custom MCP connectors.
Someone in your team can't connect
Check they have a Microsoft 365 Copilot licence on their main sign-in, the connector has been rolled out to them, and they have an active Legatics account on the right Instance.
FAQ
How do I turn the connection off?
To stop it for everyone, disable or delete the connected app in Legatics. To stop it for yourself, disconnect Legatics in Settings → Sources in Copilot Chat.
Is this included in our Legatics licence?
Yes. The MCP server is included for all customers at no extra cost.
Still need help?
For Microsoft licensing, tenant or network problems, contact your internal IT team first. For anything else, email support@legatics.com with your Instance, the step you got stuck on, any error message, and the time you tried. The time helps us find your attempt in our logs.
