Connect Microsoft 365 Copilot
The admin click path for adding GeoReputation to Microsoft 365 Copilot as a custom federated connector, the roles it needs, and what we have not yet been able to confirm about invocation.
This is a tenant administrator's job from start to finish. If you are the person who wants the data rather than the person with the admin roles, send them this link, and read the box below before you do, because it is the part that decides whether this is worth their afternoon.
What we know, and what we do not. Microsoft supports custom federated MCP connectors in Microsoft 365 Copilot, and the click path below is theirs. What we have not yet watched happen is a tool call from Copilot Chat arriving at our server. Several public reports describe connectors that add, connect and list their tools correctly while Copilot never calls them, because whether a tool is invoked is decided by Copilot's own orchestration rather than by the connector. A Microsoft moderator's reply on one of those threads says tool discovery succeeding does not guarantee the server will be called. So: your admin can add us, and Copilot decides when to use us. We are not going to tell you it works before we have seen it work. If Copilot is where your team lives, talk to us before the admin starts and we will test it against your tenant with you.
What the admin needs before starting
Roles. All three, per Microsoft's own prerequisites:
- Global Administrator or AI Administrator in the Microsoft 365 admin center
- An appropriate Microsoft Entra admin role, if you are using single sign-on
- Access to the Teams Developer Portal
Licences. Every person who will use the connector needs a Microsoft 365 Copilot licence. The connector being enabled is not enough on its own.
Credentials from us. Microsoft's OAuth route registers the client in your
own Teams Developer Portal, and it asks for a client secret. A secret
published in public documentation is not a secret, so we issue a confidential
client per tenant instead of publishing one. Email
support@georeputation.com with your tenant name and we will mint it, including
registering the redirect URI Microsoft requires,
https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect.
The API Access add-on on your GeoReputation account. Without it the connector adds and signs in, and then every question comes back saying the add-on is missing.
Details Microsoft asks for. The prerequisites now include a developer and legal block. Ours:
| Field | Value |
|---|---|
| Developer name | Fairview Labs, Inc. |
| Website URL | https://georeputation.com/docs/api/mcp |
| Privacy policy URL | https://georeputation.com/privacy |
| Terms of use URL | https://georeputation.com/terms |
Network. If your tenant restricts outbound traffic, Microsoft publishes static egress addresses for Copilot. Our server is on the public internet with no IP allowlist, so there is nothing to add on our side.
Step 1: register the OAuth connection
In the Teams Developer Portal:
-
Select Tools > OAuth Client Registration
-
Select + New OAuth connection
-
Fill in the connection:
Field Value Name GeoReputationClient ID the one we issued you Client secret the one we issued you Authorization endpoint https://api.georeputation.com/oauth/authorize/Token endpoint https://api.georeputation.com/oauth/token/Refresh endpoint https://api.georeputation.com/oauth/token/Scopes brands:read runs:read reports:read orgs:read offline_access -
Enable Proof Key for Code Exchange (PKCE). We support it and it is worth having
-
Save
The refresh endpoint is the same URL as the token endpoint, which is not a mistake in this page. Our authorization server refreshes on the token endpoint, as OAuth allows, and Microsoft's form asks for the field separately.
orgs:read is optional and requires a reviewed application grant. If your
client was not granted it, authorization removes that scope and the connector
still works for the account's home organization; list_orgs reports that
home-only state explicitly.
The portal then shows an OAuth client registration ID. Copy it. The next step needs it and there is no way to continue without it.
Step 2: create the connector
In the Microsoft 365 admin center:
-
In the left pane, select Copilot > Connectors
-
Select the Gallery tab
-
Under Created by your org, find the Create a new connector tile and select Add
-
On the Custom connector page, under Connect to MCP server, select Add
-
Fill in:
Field Value Display name GeoReputationDescription see below Base URL https://mcp.georeputation.com/mcp -
Enter the OAuth registration ID from step 1
-
Select Save
Include the /mcp path in the Base URL. Microsoft's example shows a bare host,
but our server answers at that path and the OAuth metadata we publish names that
exact URL. Reports from people connecting other MCP servers say a mismatch here,
a trailing slash included, is a common cause of a connector that signs in and
then cannot be used.
The description is not decoration. Microsoft's own guidance is that Copilot's orchestrator reads it to decide whether to call the server at all, and given the open question at the top of this page it is the one field worth spending five minutes on. Something like:
Brand visibility in AI assistants. Answers how often ChatGPT, Gemini,
Perplexity and Copilot mention a brand, which questions it wins and loses,
and why its visibility score moved. Read-only.
You can change it later from Your Connections with Edit description, so it is not a one-shot decision.
Step 3: roll it out
- Select your connector
- Select Staged rollout
- Choose Users or Groups and add your test people
- When you are satisfied, select Deploy to all users
Each person then has to sign in to GeoReputation once, under Settings > Sources in Copilot. Until they do, the connector exists for them and returns nothing, which is easy to mistake for it being broken.
If a user cannot see or use it
Microsoft's own FAQ lists six conditions that must all be true, and they are spread across three different admin pages, which is why "it is enabled" is rarely the whole answer. Check in this order:
- The publisher type is allowed in Agents > Settings > Agent and plugin access, or the connector is turned on individually
- The connector is enabled and not blocked in Agents > Tools
- The user is included in Agents > Settings > User access
- The user is included in the staged rollout, directly or through a group
- The user has a Microsoft 365 Copilot licence
- The propagation time has passed and the user has refreshed Copilot
Changes take up to ten minutes to reach Microsoft 365 experiences, and users may need to start a new conversation rather than just reload.
All of these must allow the user. If any one is restrictive, the user cannot use the connector, and the admin pages will each show you a different part of the picture: Your connections shows the connector's own state, Agents > Tools shows block status, and Sources shows only what the signed-in user can actually reach.
If it is added and Copilot still ignores it
This is the open question from the top of the page, so it is worth separating from a misconfiguration.
- Name the brand in the request and phrase it close to what the tools do: "using GeoReputation, how visible is Acme in AI answers this month". Microsoft advises matching prompts to tool descriptions, and it is the only lever a user has
- Check the connector's description. A vague one is the documented cause of an orchestrator skipping a server
- Then tell us. We instrument the server and can see whether a tool call ever arrived from your tenant, which is the difference between Copilot not calling us and us not answering. That evidence is worth more to us than it is to you, and we would rather have it than guess
What this connector can do
The same eleven read-only tools as every other client: your brand list with scores, a brand's visibility and its change over a window, prompt categories and the prompts inside them, which categories moved, your recommendations and reports, your monitoring runs and the individual answers inside them, what changed for one question, and the client list for an agency account. No writes. It cannot start a scan, change a brand or spend anything on your account, because the API it reads refuses writes from any token.
The full list, phrased as the questions they answer, is on the connector page.
Windows are 7, 30 or 90 days.
Scores run 0 to 1000, not 0 to 100, and they are not percentages. A move is best described in points. The bands the product itself uses, so a number means the same thing here as on your dashboard:
| Score | Band |
|---|---|
| 0 | Not Visible |
| 1–199 | Low |
| 200–399 | Limited |
| 400–599 | Moderate |
| 600–799 | Good |
| 800–1000 | Strong |