Copilot Studio Agent for Self Service Portal

On this page

Introduced in 2026.2

Set up an agent in Microsoft Copilot Studio so Self Service Portal users can get help from Alloy Navigator in Teams. Each user signs in with their portal account and the agent works within that account's permissions.

Before you begin

  • Enable the Self Service Portal MCP server and copy its full Server URL ending in /V2/Ssp/Mcp. The Alloy Navigator API must be reachable from the Microsoft cloud over HTTPS.
  • Make sure you can create agents and custom connectors in your Copilot Studio environment. Have a Self Service Portal account ready to test the connection.

Create and test the agent

  1. Create an agent in Microsoft Copilot Studio and give it a name your portal users will recognize.
  2. Go to Tools > Add a tool > New tool and choose Model Context Protocol. Enter a server name and description, then paste the Server URL.
  3. Choose OAuth 2.0 and Dynamic discovery. Create a connection, sign in with the test Self Service Portal account, and select Allow. Add the tool after the connection is ready.
  4. Open the tool and set its authentication to End user account so the agent uses each person's portal permissions.
  5. Save the agent. In Preview, ask the agent which Alloy Navigator account it is using and check that it identifies the test account.

For details on adding the tool, see Connect an existing MCP server to an agent.

Publish and share the agent in Teams

  1. Publish the agent. Under Channels, open Teams + Microsoft 365 and select Add channel.
  2. In Copilot Studio, select Share and grant the intended users access to the agent.
  3. In the Teams channel settings, go to Availability options > Copy link. Share the installation link and the steps for connecting in Teams with those users.

Publish the agent again after making changes. If someone can open the link but cannot use the agent, check that they have access. For channel and sharing options, see Connect and configure an agent for Teams.

Restore the agent's MCP connection

If the tool shows Couldn't load MCP tools, try connecting again first. An agent can lose its registration after the API moves to a new database or its signing key is reset. If reconnecting fails:

  1. In Copilot Studio, remove the MCP server from the agent's Tools.
  2. In the same agent, add the portal MCP server again. Enter a new Server name and set the tool's authentication to End user account.
  3. Test the connection in Preview, then publish the agent again.