Global or AI Administrator
The person who adds the connector needs one of those Microsoft 365 admin roles.
Loading...
Skip to setup
Connect Ad Legends
01 02 03 04 What Authorize does
Ad Legends · Microsoft Copilot
Connect Ad Legends
to Microsoft Copilot.
Add the Ad Legends brands server from the Microsoft 365 admin center. Create a Copilot client on this page, register it in Teams Developer Portal, then sign in to Ad Legends.
Before you begin
Four things to have ready.
A Copilot license
The people who will use Ad Legends in Copilot need a Microsoft 365 Copilot license.
An Ad Legends account
You will sign in to Ad Legends when you choose Authorize. Use the account Copilot should work from.
About an hour on a new tenant
If this Microsoft 365 tenant was just created, wait about an hour before the first connection. Microsoft refuses it until then.
Your Copilot client
Create a client, then download it.
The admin center menu lists None, OAuth 2.0, and Entra SSO. Create the client here. The two Microsoft pages below are where it goes next. The client ID and secret are shown once.
Checking your account.
01
Register the client in Teams Developer Portal
The connector article starts in the Teams Developer Portal. Open it, then follow the clicks.
https://dev.teams.microsoft.com
- 1Sign in to the Teams Developer Portal.
- 2Select Tools, then OAuth Client Registration.
- 3Select New OAuth connection. The OAuth article labels this button New OAuth client registration.
- 4Enter the fields below from top to bottom. Restrict usage by organization: Any Microsoft 365 organization. Restrict usage by Teams app: Any Teams app. Enable Proof Key for Code Exchange (PKCE): On. Client password authentication method: HTTP Basic authentication. Request body parameters also works.
- 5Select Save.
- 6Copy the OAuth client registration ID. That ID is the Reference ID in the admin center. It is not the Client ID.
Registration name
Ad LegendsBase URL
https://www.adlegends.aiRestrict usage by organization
Any Microsoft 365 organizationRestrict usage by Teams app
Any Teams appClient ID
Create the Copilot client on this page. Shown once.Client secret
Create the Copilot client on this page. Shown once.Authorization endpoint
https://www.adlegends.ai/api/oauth/authorizeToken endpoint
https://www.adlegends.ai/api/oauth/tokenRefresh endpoint
https://www.adlegends.ai/api/oauth/tokenScope
brands:read brands:write ads:read ads:generate billing:readEnable Proof Key for Code Exchange (PKCE)
OnClient password authentication method
HTTP Basic authentication. Request body parameters also works.Set up custom federated connectors and Configure OAuth 2.0 authentication
02
Add the connector in the Microsoft 365 admin center
Use the registration ID from step 01 as Reference ID. Authentication type is OAuth 2.0.
https://admin.cloud.microsoft/#/copilot/connectors/add
- 1Sign in to the Microsoft 365 admin center.
- 2In the left pane, select Copilot, then Connectors.
- 3Select the Gallery tab. Under Created by your org, select Add on Create a new connector.
- 4On Connect to MCP server, enter the form values below.
- 5Set Authentication type to OAuth 2.0. Paste the OAuth client registration ID into Reference ID.
- 6Check Notice. Choose Authorize, sign in to Ad Legends, then choose Create.
- 7Microsoft says the connection can take about 30 minutes before Copilot can use it. Ask in a new chat: Show my Ad Legends brands.
Display name
Ad LegendsDescription
Connect Microsoft 365 Copilot to your Ad Legends brands.MCP endpoint URL
https://www.adlegends.ai/api/mcp/brandsDeveloper name
Ad Legends Inc.Website URL
https://www.adlegends.aiPrivacy policy URL
https://www.adlegends.ai/privacyTerms of use URL
https://www.adlegends.ai/termsAuthentication type
OAuth 2.0Set up custom federated connectors and Authentication for MCP plugins
Admin center
Create the connector, then authorize it.
- 01On this page, sign in and choose Create Copilot client. Download the file. Leave the page and the secret is gone.
- 02Open Teams Developer Portal. Choose Tools, OAuth client registration, then New OAuth client registration. Enter the fields in the order on this page: Registration name, Base URL, Restrict usage by organization, Restrict usage by Teams app, Client ID, Client secret, Authorization endpoint, Token endpoint, Refresh endpoint, Scope, Enable Proof Key for Code Exchange (PKCE) on, Client password authentication method HTTP Basic authentication. Request body parameters also works.
- 03Save, then copy the OAuth client registration ID. That is the Reference ID. It is not the Client ID.
- 04Open the Microsoft 365 admin center at admin.cloud.microsoft. Go to Copilot, then Connectors, then Gallery. Under Created by your org, choose Create a new connector, then Add.
- 05Fill in every field with the values in the next section. Set Authentication type to OAuth 2.0 and paste the Reference ID.
- 06Choose Authorize. Sign in to Ad Legends, review the access, and approve it. Check the Notice box, then choose Create.
You sign in on Ad Legends, not in the admin center.
Authorize sends you to Ad Legends. Sign in with the account Copilot should use, check the brands and access on the approval screen, and approve. You do not paste an Ad Legends password into Microsoft.
Reference ID is the OAuth client registration ID from Teams Developer Portal. It is not your email and it is not the Client ID in the download.
Form values
Type these into Connect to MCP server.
Copy each value as it is written. The endpoint includes the full path.
Display name
Ad LegendsDescription
Connect Microsoft 365 Copilot to your Ad Legends brands.MCP endpoint URL
https://www.adlegends.ai/api/mcp/brandsDeveloper name
Ad Legends Inc.Website URL
https://www.adlegends.aiPrivacy policy URL
https://www.adlegends.ai/privacyTerms of use URL
https://www.adlegends.ai/termsAuthentication type
OAuth 2.0Authentication type is OAuth 2.0. Reference ID is the registration ID you copy after saving the client in Teams Developer Portal. Then choose Authorize, finish the Ad Legends sign-in, check Notice, and choose Create.
Try it in Copilot
Give it about 30 minutes, then ask one question.
Microsoft says a new connector can take about 30 minutes before Copilot can use it. You can stage the rollout to selected people or groups instead of the whole organization.
“Show my Ad Legends brands.”
Open a new Copilot chat and ask that. A working connection lists the brands the Ad Legends account you approved can access.
Troubleshooting
When the form will not finish.
“Wait at least 1 hour before creating your first connection.”
This is normal on a brand-new Microsoft 365 tenant. Wait about an hour, then submit the same form again. Nothing is wrong with the Ad Legends server.
The form asks for a Reference ID.
Paste the OAuth client registration ID from Teams Developer Portal. That ID is not your email and it is not the Client ID. An empty Reference ID makes Microsoft say the request is malformed.
The menu shows OAuth 2.0 with Dynamic Client Registration (DCR).
You can use that row and skip the client on this page. Copilot registers itself, then you choose Authorize. If that row is missing, create a client here and choose OAuth 2.0.
Authorize fails, or the sign-in says the redirect is not allowed.
Confirm the MCP endpoint is exactly https://www.adlegends.ai/api/mcp/brands, allow the sign-in window, and finish approval on the Ad Legends account you meant to use. If it still fails, contact Ad Legends and include the error text.
Copilot does not see Ad Legends yet.
Wait about 30 minutes after Create. Start a new Copilot chat. If you staged the rollout, confirm your account is in the selected group.
Microsoft’s notes
The pages this walkthrough follows.
Questions
Microsoft Copilot and Ad Legends.
Who can add this connector?
A Global Administrator or an AI Administrator in the Microsoft 365 tenant. The people who will use Ad Legends in Copilot also need a Microsoft 365 Copilot license.
Do I need a Client ID, a Client Secret, or a Reference ID?
Yes. Sign in on this page and create a Copilot client. In Teams Developer Portal, enter the form top to bottom: Registration name, Base URL, Restrict usage by organization, Restrict usage by Teams app, Client ID, Client secret, Authorization endpoint, Token endpoint, Refresh endpoint, Scope, Enable Proof Key for Code Exchange (PKCE) on, and Client password authentication method set to HTTP Basic authentication. Request body parameters also works. Save, then paste the OAuth client registration ID into Reference ID. That ID is not your email and it is not the Client ID. If the menu offers OAuth 2.0 with Dynamic Client Registration, you can use that row and skip the download.
Which Ad Legends account does Copilot use?
The account that finishes Authorize. Sign in with the Ad Legends account Copilot should work from, and approve the access on that screen. Staged rollout later controls which people in your tenant can use the connector.
Why does Microsoft say to wait an hour?
A brand-new Microsoft 365 tenant can refuse the first connection for about an hour. Wait, then submit the same form again. The Ad Legends server is not the cause.
How long until Copilot can use it?
About 30 minutes after you choose Create. You can limit the rollout to selected people or groups. Then open a new Copilot chat and ask “Show my Ad Legends brands.”
What if Authorize fails?
Confirm the MCP endpoint is exactly https://www.adlegends.ai/api/mcp/brands, allow the sign-in window, and finish approval on the Ad Legends account you meant to use. If Microsoft still reports a redirect or consent error, contact Ad Legends and include the message on the form.
Your brands, inside Copilot.
If a tenant setting blocks the connector, write to us with the error on the form. We will walk through it with you.