Forum Discussion
Cannot Publish My Agent
- Apr 29, 2026
Hey MSOPS1 - you would have read the respoinse from Rajesh_Gurusamy , however, trying to help here- if that didn't work.
This issue typically relates to environment roles and configuration, not licensing alone.
To publish an agent in Copilot Studio, a user must have:
- A valid Copilot Studio / Power Platform license &
- The appropriate Power Platform environment role
A Teams license may allow access to Teams, but it does not grant publishing permissions in Copilot Studio.
Differences between users with identical licenses usually occur due to:
- Different environment security roles
- Dataverse not being enabled consistently
- The agent not being published in a Teams-enabled environment
- Missing permissions, which can also hide options such as knowledge sources, tools, or actions
What I suggest-
- Have your administrator verify your environment role assignment
- Confirm the environment has Dataverse enabled and Teams integration configured (if publishing to Teams)
- Ensure you are assigned a role such as Environment Maker in addition to the license
In Copilot Studio, licensing alone is insufficient, roles and environment configuration are required for agent publishing.
Hello MSOPS1 ,
It sounds like you are encountering a few common hurdles related to environment roles and agent types. Based on your description, here are the three steps to resolve this:
Upgrade from "Declarative" to "Custom" Agents The reason you are missing the Knowledge and Tools tabs is likely because you are building a Declarative Agent directly within the Microsoft 365 Chat interface. To access full functionality, you should use the Microsoft Copilt Studio.
Enable the "Copilot Studio Authors" Role The "user license" error when publishing is often a permissions issue rather than a missing license. Recent updates require that your Admin assigns you to a specific Security Group linked to the Copilot Studio Authors role within the Tenant Settings of the Power Platform Admin Center. You can find the step-by-step for this in of the https://microsoft.github.io/agent-academy/recruit/00-course-setup/ Agent Academy.
Making the Agent Visible in Teams Publishing the agent in the Studio only pushes the logic live; it doesn’t automatically deploy it to the company-wide Teams store. To make it appear for everyone:
Go to Availability options in the Teams channel settings.
Select "Show to everyone in my org" and click Submit for admin approval.
Your Teams Admin must then approve/publish the app in the . Detailed instructions are available here: .https://microsoft.github.io/agent-academy/recruit/11-publish-your-agent/
Recommendation: I highly suggest following the https://microsoft.github.io/agent-academy/ path. It covers these exact administrative requirements and helps ensure your environment is configured correctly for "Special Ops" level development.
If you have any further doubts or need specific steps for your admin, please let me know.
Best regards,
Rajesh G.