Skip to main content

Connecting PI's MCP to Microsoft Copilot

This article applies to client-side IT administrators and technical sponsors responsible for enabling PI's MCP connector during the current Pre Beta phase.

Learn how to enable the Predictive Index MCP connector for your organization, and get PI-powered behavioral intelligence right in Microsoft Copilot.

Note: Before proceeding, ensure you've achieved the PI-specific prerequisites for enabling the MCP.

Who can add the connector to Copilot?

Microsoft Copilot is admin-managed only; there is no individual self-service path. An admin publishes an agent carrying the connector once for the organization, and each user still authenticates with their own PI account the first time they use the MCP.

Prerequisites specific to Copilot

  • Microsoft 365 Copilot licenses for your users

  • A data policy covering the connector, in the same group as the agent’s other connectors

    • Where to find: Power Platform admin center → Security → Data and privacy → Data policy

  • Advanced connector policies (default-deny) that allow the MCP

    • Where to find: Security → Data and privacy → Advanced connector policies (or the environment group’s Rules page)

    • What to do: Add the connector, save, then publish the rules

How to connect PI's MCP to Copilot

Note: Copilot's menu labels and navigation flows are subject to change over time. If a label in the steps below does not match what you see in Copilot, please refer to our host-agnostic steps for general guidance.

Step 1: Add the connector.

  1. Sign in at copilotstudio.microsoft.com, select your environment, and open or create the agent for Obi.

  2. Open Settings → Generative AI → Orchestration and set generative AI orchestration to "Yes." (Our MCP requires it.)

  3. Select Tools → New tool → Model Context Protocol.

  4. Enter a Server name (e.g., "Obi by PI"), a short description, and the Server URL: https://mcp.predictiveindex.com/mcp.

  5. Set authentication to "OAuth 2.0" with Type: Dynamic discovery. No client ID or secret is needed.

  6. Select "Create a new connection," sign in with your PI account, then add it to the agent.

  7. On the tool’s Overview page, under Details → Additional details → Credentials to use, select "End user credentials" (not "Maker-provided credentials"). This is what makes each user authenticate as themselves.

Note: "OAuth 2.0" here is Copilot Studio’s own dropdown label for the authentication pattern. PI’s authentication method is OAuth 2.1 with PKCE, described under "Signing in and data scoping".

Step 2: Publish org-wide.

  1. Select "Publish."

  2. Go to Channels → Teams and Microsoft 365 Copilot, leave "Make agent available in Microsoft 365 Copilot" selected, and add the channel.

  3. Under availability options, choose to show it to everyone in your organization and submit for admin approval. (The status will show as "Pending.")

  4. A tenant admin approves the app in the Microsoft Teams admin center "Manage apps" page, or in the Microsoft 365 admin center under "Agents." (The status will become "Approved.")

Step 3: Have users sign in.

  1. In Microsoft Teams or Microsoft 365 Copilot, users will find the agent under "Built for your org."

  2. Have users add the agent.

  3. Once users ask a PI-related question, a sign-in prompt will ask them to connect their own PI account.

  4. Users should enter their login credentials and confirm.

Tip: Once the MCP is enabled, learn how to leverage the MCP here.

FAQs

The UI steps for Copilot are inaccurate/outdated. What now?

Copilot's menu labels and navigation flows are subject to change over time. If a label in the steps above does not match what you see in Copilot, please refer to our host-agnostic steps for general guidance.

If you need additional help configuring our MCP, please reach out to our product manager, Stefano Hernandez, at [email protected].

Additional support

Did this answer your question?