Forum Discussion
Cannot Publish My Agent
Hello
I am currently facing an issue publishing an agent for testing purposes in Microsoft Copilot Studio. Despite having the license assigned, the publishing process is not functioning as expected. The pop-up reads,
"There are open issues with your agent
You currently do not have a user license that allows you to publish in Copilot Studio. Please contact your administrator to upgrade your license or enable the necessary permissions"
I have noticed some inconsistencies in how these permissions are applied, a teammate with the same license initially could not access the environment at all. After being granted a Teams license, they were able to access and publish successfully however, the agent is not appearing in Teams. Moreover, there is no option to add a knowledge base, tools or further functionalities to the agent at this time.
Could someone clarify the specific requirements for agent publishing? Do I need to contact my administrator to assign a role or do I need to be assigned a completely different license? Additionally, why would two users with identical licenses experience different environment access and visibility results?
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.
4 Replies
Thanks for the responses. Apparently, buying the user license solved the problem in this case.
AggarwalatulMicrosoft
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.
Hey MSOPS1 , it looks like you're hitting three of the most common 'day-one' hurdles with Copilot. Here’s the simple fix for each:
The Missing Tabs: You're likely in the basic 'Declarative' builder. To get those Knowledge and Tools tabs, head over to the full Microsoft Copilot Studio instead.
The License Error: This is usually a permission quirk. Ask your Admin to add you to the 'Copilot Studio Authors' security group in the Power Platform Admin Center - that usually clears the 'user license' pop-up immediately.
The Teams Issue: Publishing in the Studio just saves your work; your Admin still needs to 'approve' it in the Teams Admin Center before it shows up in the store for everyone.
Thanks,
Rajesh GHello 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.
