Overview

This guide explains how to create an Agent in Copilot Studio and connect this Agent to One Model using the Model Context Protocol (MCP)

Once connected, Copilot can securely query governed workforce metrics from One Model and incorporate those results directly into conversational workflows such as analysis, document drafting, reporting, and presentations.

By connecting Copilot to One Model via MCP, you can:

• Reduce context switching by querying workforce data directly from Copilot
• Stay within your existing workflow while drafting content, writing code, or building presentations
• Combine AI reasoning with trusted One Model metrics to answer complex workforce questions

Please Note: One Model’s MCP integration is currently in an early-access phase. Because AI platforms update their interfaces frequently, you may find that some buttons, menu names, or configuration steps have shifted slightly since this guide was published.

• System Variations: Steps may vary depending on your specific tenant setup, regional settings, or administrative permissions.
• Help Us Improve: If a step looks different in your system or you encounter an unexpected result, please let us know! Use the Feedback Form to help us refine these instructions for the final release.

Terminology & Notes

• In Copilot, MCP integrations are referred to as 'Agents.' These agents act as connectors to external systems such as One Model. 
• Throughout this guide, Agent refers to the custom Copilot bot you are building, while Tool refers to the specific MCP connection to One Model. These components work together to provide workforce insights.
• This guide uses Copilot as the reference AI platform. Other MCP-compatible tools may have similar steps but different terminology.

Audience & Prerequisites

This guide is intended for:

• One Model Administrators responsible for setup, configuration and publishing
• Business Users and Analysts with approved access who will connect to and use the app

Part 1: One Model Administrators 

Setup, Configuration, and Publishing

To authorize the connection between Copilot and your One Model production instance, an Administrator must configure both the One Model "Client" and the Copilot Studio "Tool."

Required Permissions

Ensure your user account is assigned an Application Access Role (AAR) with the following permissions enabled:

• CanAccessOneModelMCP - Allows use of the MCP to communicate with Copilot or other external AI tools
• CanConfigureCompany - Grants access to high-level company settings

These permissions are configured via:  Admin > Application Access Role > [Select Role] > Permissions.

Integration Client Configuration

Once permissions are granted, Administrators manage authorized AI integrations through the Integrations page.  This ensures that only approved external tools can access data from your One Model instance.

Create a Client Integration in One Model 

• Log into your One Model production instance
• Navigate to Admin > Integration
• Click Create New and select Microsoft 365 Copilot

Approved Client List

For security and compliance, One Model uses a Client Rule Approve List to control which external applications are allowed to connect. 

• You must specify approved client metadata (such as redirect/return URLs)
• This ensures that data is only shared with platforms vetted by your Security and Compliance teams

Pre-configured Templates:  One Model provides pre-configured connector templates for major AI providers. When selecting ChatGPT, Microsoft 365 Copilot, or Claude, required return URLs are auto-populated.

Custom Integrations: For proprietary or unsupported AI tools, select Custom and manually define required metadata fields and allowed values.

Creating the Tool in Copilot Studio

1. Log into Copilot Studio
2. Navigate to Agents 
3. Open an existing agent, or create a new agent.
4. Navigate to the Tools tab
5. Click Add a tool
6. Select Model Context Protocol

7. Configure the MCP:

• Server Name: e.g., One Model
• Server Description: e.g., One Model People Analytics Platform
• Server URL: the endpoint for your One Model MCP server
  • Example: https://api.[companyid].onemodel.us/mcp
  • Be sure to use the correct URL for your environment (production)
• Authentication: OAuth 2.0
• Type: Dynamic discovery
• Click Create

Tip: When to use Manual instead? 

If ‘Dynamic discovery’ fails to connect or your corporate firewall requires explicit endpoint mapping, switch the Type to Manual. This will prompt you to enter specific Authorize/Token URLs and will generate a Redirect URL that you must paste back into the One Model Integration page.

8. Click Create new connection 

Accept Permissions

A confirmation screen will display the connector’s capabilities.

• These permissions are defined by One Model
• They are read-only during setup

Click Accept to finalize the connection.

9. Click Add and configure 

The One Model connection has been added to your agent.

Test your Agent

Click Open connection manager

Click Connect

Click Submit

Publishing the Agent

The agent must be published before it can be used by end users.

Publish the Agent

1. Return to Agent
2. Locate the newly created One Model agent
3. Click Publish
4. Click Force newest version and then Publish

Your agent is now published.  From Copilot you can share your agent. 

1. Navigate to Agents 
2. Navigate to the Channels tab
3. Click Teams and Microsoft 365 Copilot

Your org admin should be able to share the app and promote it for all users automatically, but to do this manually, open Copilot, locate your new agent and select “share” and then provide the copied link to other users.

Test the Connection

1. Select the One Model app in Copilot
2. Enter a query that requires One Model data, such as:
   • What is my external hire rate trend?
   • What is my current headcount?

The query is routed through One Model’s MCP layer and returns a governed, data-driven response.

Tip: If you receive an error or no data, verify permissions, MCP URLs, and connector visibility.

Part 2: Business Users and Analysts

Connecting to and Using the One Model App 

Required Permissions

To connect Copilot to One Model, your user account must have an Application Access Role (AAR) with:

• CanAccessOneModelMCP enabled

This is managed by your One Model Administrator via: Admin > Application Access Role > [Select Role] > Permissions

Log in to One Model

Log in (or use SSO) to your company’s One Model production instance.

Enable the Agent in Copilot

1. In Copilot, select Agents from the left panel 
2. Search for the One Model agent
3. Select the agent and start a chat 
4. You will then be prompted to Open the connection manager

5. The connection manager will open in a new browser tab, click Connect

6. Click Submit

7. You will now see the Connected confirmation message. You can now close this browser tab.

8. In your Copilot chat, click Retry 

Test the App

Enter a query that requires One Model data, for example:

• What is the company’s external hire rate trend?
• What is the company's current headcount?

Copilot will route the request through One Model’s MCP layer and return results based on governed workforce data.

Tip: If you encounter errors or no data, confirm that the app is visible, connected, and that you have the required permissions.

Feedback Form

We encourage beta testers to complete the Feedback Form to share what’s working well, report issues, and suggest enhancements.

If you experienced app visibility or discoverability issues, please note:

• Whether the app was newly published or republished