Skip to main content
Microsoft 365 Copilot connects to GetWhys through a read-only federated connector. It can retrieve research, personas, messaging frameworks, and brand voice—and score content—without indexing or changing your GetWhys data.

​
Before you start

This setup requires two roles. They can be held by the same person:
  • A GetWhys admin to generate OAuth credentials
  • A Microsoft 365 Global Administrator or AI Administrator with access to the Teams Developer Portal

​
Connect GetWhys

1

Generate GetWhys OAuth credentials

Generate an OAuth MCP Connector in GetWhys with a label such as copilot. Copy the OAuth Client ID and OAuth Client Secret. GetWhys shows the secret only once.On the connector, click Edit URIs and add Microsoft’s redirect URI:
2

Register GetWhys OAuth

In the Teams Developer Portal, open Tools → OAuth Client Registration and select + New OAuth connection.Enter these values:Select Save, then copy the OAuth client registration ID.
3

Create the federated connector

In the Microsoft 365 admin center, go to Copilot → Connectors and open the Gallery tab. Under Created by your org, find Create a new connector and select Add.Under Connect to MCP server, select Add and enter:Select Save. The connector appears under Your connections.
4

Roll out the connector

From Copilot → Connectors → Your connections, open GetWhys.Use Staged rollout to assign it to selected users or Microsoft Entra groups. When you’re ready to make it available across your tenant, select Deploy to all users.Changes can take up to 15 minutes to appear.
5

Enable GetWhys in Copilot

After the connector is deployed, each user opens Microsoft 365 Copilot Chat → … → Settings → Sources, finds GetWhys, and selects Connect.Microsoft uses the organization OAuth connection, so the user does not sign in to GetWhys separately.
GetWhys is also available as a source in supported Microsoft 365 Copilot experiences, including Copilot in Excel, the Researcher agent, and Cowork.

​
Verify the connection

With GetWhys connected as a source, ask: “Who am I in GetWhys?” If Copilot returns your GetWhys organization, you’re connected.

​
Troubleshooting

GetWhys does not appear under Sources — confirm that an admin enabled the connector for your account or Entra group. Allow up to 15 minutes after a rollout change. Authentication fails — confirm every OAuth endpoint and credential, make sure PKCE is enabled, and verify that Microsoft’s redirect URI appears under Edit URIs in GetWhys. A GetWhys tool is unavailable — disconnect and reconnect the source to refresh its tools. If the problem continues, try another MCP client or contact [email protected].