Share
Report
2Hi all,
I'm stuck in what feels like a circular issue when trying to publish a Copilot Studio agent and would appreciate any guidance.
The setup:
- I'm a maker building a custom agent in Microsoft Copilot Studio.
- The agent uses one or more tools/plugins (connector actions / API plugins).
- I want to publish it so it can be used in Microsoft Teams / Microsoft 365 Copilot.
The problem:
When I go to the Publish page in Copilot Studio, I see this warning under "Draft agent status":
"You have one or more active plugins within your agent, which is a feature that requires admin approval for publishing. Disable your plugins or contact your admin to publish this agent."
The agent status shows "Not published."
I contacted my admin and asked them to approve the agent, but they say they cannot see the agent anywhere on their side (it's not appearing in the Microsoft 365 admin center → Copilot → Agents → Requests queue, or anywhere else they've looked).
So I can't publish because it needs admin approval, and the admin can't approve because the agent doesn't appear in their queue. It feels like a deadlock.
What I've already tried / verified:
- The agent is functional and works in the test panel.
- I have a Copilot Studio user license.
- I attempted the standard publish flow from the Publish page.
What I'm not sure about:
- Whether there's a specific "Submit for admin approval" action I'm supposed to trigger that I'm missing (and if so, where exactly it lives in the current UI).
- Whether this is actually a tenant-setting issue (e.g., "Publish agents with AI features" not enabled in Power Platform admin center).
- Whether this could be a license issue at the tenant level (e.g., tenant lacks Microsoft 365 Copilot licensing, so the admin-side Requests queue isn't fully provisioned).
- Which specific tool/plugin in my agent is triggering the "requires admin approval" flag, since the warning doesn't say.
My questions:
- What is the correct, current step-by-step flow to actually get this agent into my admin's approval queue?
- Is there a way to identify which plugin/tool is triggering the admin-approval requirement?
- What should I ask my admin to check on their side (specific settings, license SKUs, admin center sections) to unblock this?
- Has anyone else hit this exact "maker is blocked, admin sees nothing" scenario, and how was it resolved?
Any pointers to documentation or your own experience would be hugely appreciated. Thanks!
Screenshot 2026-0...
All responses (
Answers (
