You've built your first Copilot Studio agent. You've tested it in the chat panel. Everything looks good. You go to hit publish and the button is disabled. No clear error message. No obvious reason why.
If you're using a Copilot Studio trial licence, this is by design — and the fix isn't obvious.
Quick Check
If you're on a trial and can't publish, you likely don't have the Authors role configured.
The Problem
The Copilot Studio trial licence gives you access to create agents and test them using the built-in test chat panel. However, publishing is blocked by default on a trial. You cannot deploy your agent to any channel — Teams, a website, SharePoint — without additional setup.
Some older tutorials assume publishing is available in trial environments, which is why you might not even be aware the restriction exists if you're following a course or guide written before this change.
The Fix — Copilot Studio Authors Role
To enable publishing on a trial, you need to add yourself to the Copilot Studio Authors role in the Power Platform Admin Center. This works because the Authors role enables the pay-as-you-go access path via Copilot Credits, where publishing is allowed.
⚠️ Important: Enabling the Authors role activates the pay-as-you-go access path via Copilot Credits. In a trial environment without an Azure subscription linked, this typically won't generate charges during testing. However, in a corporate tenant where Azure billing is already configured, this can incur costs if your agent is used beyond testing. Be aware of your tenant setup before proceeding.
Step 1 — Create a security group (requires admin access)
This group will be used to grant publishing rights at the tenant level.
- Navigate to admin.cloud.microsoft
- Expand Teams & groups and select Active teams & groups
- Select the Security groups tab and select Add a security group
- Name it something like
AgentCreators— this is the group you'll associate with the Authors role - Complete the creation wizard, then open the group
- Go to the Members tab, select View all and manage members
- Add yourself as a member
Step 2 — Assign the group in Power Platform Admin Center (requires Power Platform admin access)
This is where you associate the security group with the tenant-level publishing permission.
- Navigate to admin.powerplatform.com
- Select Manage → Tenant settings
- Find Copilot Studio authors and select the pencil icon
- Select your security group from the list and click Done
- Click Save
Return to Copilot Studio and refresh the browser. Publishing should now be available.
Important — This Is a Trial Workaround
This setup is specifically needed because the trial licence doesn't include publishing rights. In most cases, paid licences include publishing capability without this workaround, assuming the environment and permissions are correctly configured.
The Authors role approach is also used in paid environments as an alternative access path to per-user licensing, which is why it can activate billable usage in tenants where billing is already set up.
Why This Matters Beyond the Trial
The trial limitation is frustrating, but it mirrors how publishing is controlled in real environments. Understanding this restriction is actually a useful introduction to a broader governance principle — publishing is a controlled action, not something every user in a tenant can do by default.
In a production environment, you'd want to think carefully about:
- Who has publishing rights
- Which environments agents are published to
- What approval process exists before an agent goes live
- Whether billing is configured and monitored before agents reach end users
The steps above solve the immediate problem. In production, those same questions become your governance framework.