License for the maker, credits for the agent
The confusing part of Copilot Studio licensing is that it has two layers. A license or role decides who may build agents. Copilot Credits pay for what those agents do when they run. A person with every license in the world still cannot run a paid agent if the tenant has no credits, and a tenant full of credits still needs someone with build access.
Microsoft’s documentation (November 2026) lists four ways to give a person access to build in Copilot Studio:
| Route | What you need first | Good for |
|---|---|---|
| Copilot Studio user license | A prepaid Copilot Credit pack subscription on the tenant | Teams that buy credits up front |
| Copilot Studio authors role | Pay-as-you-go via an Azure subscription and a billing policy, plus membership of the authors security group in Microsoft Entra, set in the Power Platform admin center | Teams that want to pay per use |
| Microsoft 365 Copilot license | The add-on license for that user | Building agents for the Microsoft Copilot harness |
| Trial | Self-service sign-up with a work account | Trying it out; you can’t publish |
The common mistake: “the user license is free, so Copilot Studio is free”
The Copilot Studio user license has no price tag, which leads many teams to think the tool costs nothing. Microsoft is explicit that you can only use it after the tenant has bought a prepaid Copilot Credit pack. Credits are bought as prepaid packs, through pay-as-you-go, or through a prepurchase plan, and unused credits don’t carry over. What an agent costs per message or action is on How does Copilot Studio pricing work?.
There is one real exception worth knowing. For users with a Microsoft 365 Copilot license, classic answers, generative answers and Microsoft Graph grounding are not charged when the agent runs in Copilot Chat, Teams or SharePoint under that user’s own identity. An agent that runs autonomously, or serves people without that license, does use credits. Microsoft also states that agents grounded only in public data or instructions can be used at no cost under usage-based billing.
What each license unlocks in Microsoft 365 Copilot
For agents that people use inside Microsoft 365 Copilot, the knowledge an agent may use depends on the licensing of the person using it:
| Knowledge source | Without a Microsoft 365 Copilot license | With a Microsoft 365 Copilot license |
|---|---|---|
| Instructions and public websites | Yes | Yes |
| SharePoint, Copilot connectors, Dataverse | Only with pay-as-you-go | Yes |
| Email, people, Teams messages | No | Yes |
The licensing models Microsoft lists here are the Microsoft 365 Copilot add-on, Microsoft 365 Copilot Business (the SKU for small and midsize businesses), Microsoft 365 E7, pay-as-you-go, and Microsoft 365 without the add-on.
The trial and the Teams-only plan
- Trial. Sign up as an individual with a work account; personal accounts are not accepted. You can create and test agents in the test chat but not publish them. The trial can be extended by 30 days, and agents keep working up to 90 days after it expires. Admins can disable self-service sign-up.
- Copilot Studio for Teams. Some Microsoft 365 subscriptions include a limited plan for agents inside Teams. It has no generative orchestration, publishes only to Teams, has no premium connectors, and stores data in Dataverse for Teams. Fine for a simple FAQ agent in one team, not for an agent that reasons over your systems.
What this means for a team
Decide the billing route before you hand out licenses. In practice:
- Pick prepaid packs or pay-as-you-go. Pay-as-you-go needs an Azure subscription and a billing policy.
- Create an Entra security group for the makers and add it as Copilot Studio authors.
- Check who already has Microsoft 365 Copilot: their internal use in Teams and Copilot is largely covered.
- Decide whether self-service trials stay on, so nobody builds a production agent on a trial that can’t be published.
A license decides who builds; it says nothing about what the agents know. Each maker connects their own knowledge, and what one agent learns stays in that agent. Which agents come with which license is on What are Copilot agents?.
Where Bombos fits
Copilot Studio licenses who may build and credits pay for each run, but the team’s knowledge still has to be wired in per agent. Bombos is a plugin that gives Copilot, your Studio agents and the other AI tools your team uses (Claude, ChatGPT, Codex, Cursor, your own agents) one shared memory of team knowledge, learned rules, mail and documents, traceable, in the cloud or on your own server. One person can try it first with their own agents.
Related questions
Is the Copilot Studio user license free?
The user license itself has no price, but Microsoft only lets you assign it after the tenant has a prepaid Copilot Credit pack subscription. Without credits on the tenant, the license gives a maker nothing to run agents with.
Can I build Copilot Studio agents with only a Microsoft 365 Copilot license?
Yes, for the Microsoft Copilot harness. Microsoft lists a Microsoft 365 Copilot license as one of the ways to get authoring access. For other harnesses and paid capabilities the tenant needs Copilot Credits.
What happens when the Copilot Studio trial ends?
You can extend the trial by 30 days. Agents built during the trial keep working for up to 90 days after it expires. During the trial you can create and test agents in the test chat, but not publish them.
How do I stop someone from building agents?
Remove them from the Copilot Studio authors security group and remove any per-user, trial or Microsoft 365 Copilot license they hold. Admins can also turn off self-service trial sign-up.
