You can use Pliant MCP in Microsoft 365 Copilot through a Copilot Studio agent. Each user signs in with their own Pliant account. Pliant roles and permissions apply as in the web app.
Copilot Studio cannot register itself with Pliant automatically, because Pliant does not offer dynamic client registration. You set up OAuth 2.0 manually in a custom connector. The setup needs a client ID and client secret from Pliant Support. Contact Pliant Support to request them.
Before you start
MCP access turned on for your Pliant organization.
A Pliant account for each user.
The client ID and client secret from Pliant Support.
Set up the connector
Open Copilot Studio and select your environment.
Create an agent, or open an existing one. Turn on generative orchestration in the agent settings.
Go to Tools > Add a tool > New tool > Model Context Protocol.
Enter a server name, for example Pliant, and a short description.
Enter this server URL: https://mcp.getpliant.com/mcp
Select OAuth 2.0, then Manual. Do not select dynamic discovery.
Enter the client ID and the client secret from Pliant Support.
Enter the values in the list below.
Create the tool. Copilot Studio then shows a redirect URL.
Send the redirect URL to Pliant Support. Pliant registers it for your connector. Wait for the confirmation before you sign in.
Select Create a new connection and sign in with your Pliant account. Then select Add to agent.
In the tool settings, set the credentials to the end user. Each user then signs in as themselves.
OAuth values
Authorization URL: https://login.getpliant.com/authorize
Token URL template: https://login.getpliant.com/oauth/token
Refresh URL: https://login.getpliant.com/oauth/token
Scope: openid offline_access McpAccess mcp:read:spend mcp:read:cards mcp:read:members
The scope must include McpAccess. Without it, every request fails.
Test and roll out
In the test pane of Copilot Studio, ask "Who am I in Pliant?". The agent returns your name and organization.
Open make.powerapps.com in the same environment. Go to Custom connectors, select Share on the Pliant connector, and add your users or a security group with Can use.
Publish the agent. Then go to Channels > Teams and Microsoft 365 Copilot and add the channel.
Users open the agent in Microsoft 365 Copilot from the Agents list. Each user signs in with Pliant at the first tool call.
Troubleshooting
Copilot often shows Pliant rejections as "HTTP 502". Microsoft's proxy changes the real status.
"RegisterDynamicClientAsync failed. Status Code: NotFound": You selected dynamic discovery. Select OAuth 2.0 and Manual instead.
HTTP 502 right after sign-in: The scope is missing McpAccess, or your organization has no MCP access. Fix the scope, delete the connection and create a new one.
"Callback URL mismatch" on the sign-in page: Pliant has not registered the redirect URL of this connector yet. Send the exact redirect URL to Pliant Support.
A colleague sees "connector info unavailable": The connector is not shared with them. Share it with Can use.
Studio skips the sign-in: Studio reuses connections. Select Create new connection and use a private browser window.
When you contact Pliant Support, send the time of the failed attempt with the time zone, the redirect URL of your connector, and the error text.
