Skip to content

Manage Your FlowStudio MCP Tenant Plan

A FlowStudio MCP tenant plan gives your whole organization one shared pool of MCP calls instead of a separate subscription per person. This page is for the owner or an admin of a paid Team or Business plan. It covers how the plan works, how to add and manage people, and how each person gets and rotates their own connection key.

The short version: Everyone you deploy the Cowork plugin to can use the plan inside Copilot Cowork right away. To let someone connect from their own tools (Claude Code, VS Code, Codex), switch them on in the Team access page. Each person then copies their own connection key from their dashboard. All calls draw from one shared monthly pool.

How the tenant plan works

  • One shared pool. Team includes 5,000 MCP calls a month, Business includes 15,000. Every person draws from the same pool, and it resets each month. You do not buy a seat per person.
  • Owner and admins. The person who bought the plan is the owner. The owner and any admins can manage people. Only the owner can add or remove admins.
  • Members. Everyone else is a member. Members use the plan; they do not manage it. Their own access and connection key live on their dashboard.
  • Outside people. You can add someone outside your organization, like a client. They share the same pool and connect from their own Microsoft tenant. Outside people can be members only, never admins.

Part 1, Admin: add and manage people

Open the Team access page and sign in with your Microsoft account. Only the owner and admins can see it.

Who already has access

Anyone you deployed the Cowork plugin to can already use the plan inside Copilot Cowork. There is nothing to add for that. The Team access page is for the next step: letting people connect from their own tools outside Cowork.

Turn on outside-tool access

In the members table, switch a person on to let them connect from their own tools, like Claude Code, Codex, or Visual Studio Code. Switching someone off does not remove them; they keep Cowork access, they just lose outside-tool access.

The Team access page does not show or manage anyone's key. Once a person is switched on, they get and rotate their own connection key from their own dashboard, covered in Part 3. As an admin you control who is allowed to connect; each person handles their own key.

Add a person by email

  1. Click Add person.
  2. Enter their email. It can be inside or outside your organization.
  3. Click Add to plan.

They show as Pending until they sign in to FlowStudio themselves, then turn Active. FlowStudio does not email them, so tell them to sign in at mcp.flowstudio.app with their Microsoft account.

People marked External are outside your organization, like a client's account. They share this plan's monthly calls and connect from their own tenant. External people can be members only, never admins.

Part 2, Admin: consent for your organization

The first time someone uses FlowStudio against a flow, Microsoft shows a one-time permission prompt. If you approve it as an admin, tick Consent on behalf of your organization so nobody else in your tenant gets prompted.

If people have already consented for themselves. Once a user approves for just themselves, that prompt will not show them the organization checkbox again. To grant for everyone after that, an admin opens the consent screen directly and ticks the organization box. Contact support and we will send the exact link for your tenant.

Part 3, Each person: get and rotate your connection key

This is for any member who connects from their own tools. Inside Copilot Cowork you do not need a key at all.

Get your key

  1. Sign in at mcp.flowstudio.app/dashboard with your Microsoft account.
  2. Connect both Power Platform permissions: Power Automate, then Power Apps. Both must show Connected.
  3. Your key appears in the Your API Key section. Click copy.

On a tenant plan, your key is automatically scoped to the shared pool, so your calls count against the team allowance, not a personal one. The dashboard also shows the MCP endpoint and a ready-to-paste config. For per-agent setup, see Getting Started with FlowStudio MCP.

Rotate your key

To replace a key, for example if it leaked, disconnect Power Platform on your dashboard and reconnect. The old key stops working and you copy the new one. Use x-api-key as the header name, lowercase with the hyphen. That is the most common setup mistake.

Troubleshooting

  • A person is stuck on Pending: they have not signed in to FlowStudio yet. Have them sign in at mcp.flowstudio.app with their Microsoft account.
  • Someone has no connection key: they are not switched on for outside tools yet, or they have not connected both Power Platform permissions. Turn them on in Team access, then have them connect Power Automate and Power Apps on their dashboard.
  • HTTP 401 or 403 from an outside tool: the key is missing, expired, or sent with the wrong header. The header must be x-api-key, not Authorization: Bearer.
  • The pool is used up: the shared allowance resets next month. If your team needs more, move up a tier in the Microsoft 365 admin center or contact us.

Related guides