Skip to main content
GetWhys connects to Microsoft 365 Copilot through a custom federated connector. Microsoft 365 Copilot uses MCP to retrieve GetWhys data in real time without indexing it into Microsoft 365. Microsoft 365 federated connectors are read-only. Copilot can retrieve research, personas, messaging frameworks, and brand voice from GetWhys. Tools that perform an action may not be available through this connector.

​
Before you start

You’ll need:
  • A Microsoft 365 Global Administrator or AI Administrator
  • Access to the Teams Developer Portal
  • GetWhys OAuth client details for your Microsoft 365 tenant
Microsoft 365 requires each user to authenticate with their own GetWhys account. An Organization MCP API Token is not used for this setup. Contact GetWhys via Teams, Slack, Google Chat, or [email protected] to register the Microsoft redirect URI and get the OAuth client details required below.

​
Register GetWhys OAuth

In the Teams Developer Portal:
  1. Open Tools → OAuth Client Registration.
  2. Select + New OAuth connection.
  3. Enter the GetWhys OAuth client ID, client secret, authorization endpoint, token endpoint, refresh endpoint, and scopes supplied by GetWhys.
  4. Select Save.
  5. Copy the OAuth client registration ID. You’ll use it when you create the connector.
Microsoft uses this redirect URI for the OAuth flow:

​
Create the federated connector

Your Microsoft 365 admin completes this setup once:
  1. Open the Microsoft 365 admin center.
  2. Go to Copilot → Connectors.
  3. Open the Gallery tab.
  4. Under Created by your org, find Create a new connector and select Add.
  5. Under Connect to MCP server, select Add.
  6. Enter:
    • Display name: GetWhys
    • Base URL: https://api.getwhys.io/mcp
    • OAuth registration ID: the ID from the Teams Developer Portal
  7. Select Save.
The connector appears under Your connections. Changes can take up to 15 minutes to appear.

​
Roll out the connector

From Copilot → Connectors → Your connections, open GetWhys and choose one of these rollout options:
  • Use Staged rollout to assign the connector to selected users or Microsoft Entra groups.
  • Select Deploy to all users when you’re ready to make it available across your tenant.

​
Connect your GetWhys account

After an admin deploys the connector, each user connects their own GetWhys account:
  1. Open Microsoft 365 Copilot Chat.
  2. Select the … menu, then Settings.
  3. Select Sources.
  4. Find GetWhys and select Connect.
  5. Sign in to GetWhys and approve access.
GetWhys is also available as a source in supported Microsoft 365 Copilot experiences, including Copilot in Excel and the Researcher agent.

​
Verify

With GetWhys connected as a source, ask the verify prompt: “Who am I in GetWhys?”

​
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 that the OAuth registration uses the GetWhys values supplied for your tenant and includes Microsoft’s redirect URI exactly. A GetWhys tool is unavailable — Microsoft 365 federated connectors support read-only tools. Use another MCP client if your workflow needs tools that perform actions.