Three separate Microsoft products get bundled into the phrase "a Copilot licence," and teams routinely buy the wrong one, or discover a gap the day they try to publish. Here is what each piece actually requires, which base licences qualify, and the trap that shows up at the worst possible moment.
Anyone shopping for "a Copilot licence" is usually conflating three purchases that Microsoft sells and prices separately.
You need the first two. The third is optional, and most pilots skip it entirely.
Not every Microsoft 365 plan gives you Teams and SharePoint together, and that combination is what a base licence is really being judged on. Four common options, and where each one lands:
| Licence | Qualifies | Why |
|---|---|---|
| M365 Business Basic | Yes | The cheapest full fit. Teams, SharePoint, and a work account are all included. Web Office only, but building and testing an agent doesn't need the desktop apps. |
| Teams Essentials | No | Teams without SharePoint administration, so there's no knowledge-source story and no Microsoft 365 Copilot attach point. It looks like the cheap option, which is exactly why it catches people out. |
| M365 Apps for business | No | Desktop Office apps without Teams or SharePoint. There's nowhere for an agent to publish into. |
| E3 / E5 | Yes | Works fine, but you're paying for enterprise security and desktop suites a pilot doesn't need yet. Start smaller and upgrade once the rollout is real. |
The pattern worth remembering: SharePoint administration is the gate. Any plan that gives you Teams but not SharePoint will get you partway into Copilot Studio and then stop.
Copilot Studio's trial lets you build and test an agent without buying anything, and that's exactly why so many pilots start there. What the trial doesn't cover is publishing. Taking an agent out of the test pane and putting it in front of other people requires a Copilot Studio user licence attached to your account, a separate line item from the base licence question above.
The dialog that tells you this shows up the moment you click Publish. For a lot of builders, that's the first time they've seen it, and it tends to land on demo day, in front of the stakeholders who approved the pilot in the first place. Check whether your account can publish on day one of the build, not the day you're planning to show it off.
For a single agent built to prove the concept, M365 Business Basic plus the Copilot Studio trial covers the whole exercise at close to zero cost, right up until you're ready to publish. At that point you add a Copilot Studio user licence for the builder, and possibly for anyone else who needs publish rights.
If your organisation already runs E3 or E5 across the board, the base licence question is moot (you're covered) and Copilot Studio licensing is the only decision left. Either way, resolve licensing before you invest real build time, not after. An agent that works perfectly in the test pane and can't go live is a wasted afternoon at best and a credibility problem at worst.
Adding Microsoft 365 Copilot licences to your users doesn't change anything about Copilot Studio publishing rights, and it doesn't substitute for a qualifying base licence either. It's a separate purchase layered on top, aimed at giving people the assistant inside Word, Excel, and Outlook. Buy it because your team wants that assistant in their everyday apps, not because someone told you it's a prerequisite for building or running an agent. It isn't, and conflating the two is one of the more common ways teams overspend on a pilot before they've proven the agent is worth rolling out.
Before a builder spends real hours in Copilot Studio, two checks take about five minutes each and catch most of the surprises above. In the Microsoft 365 admin center, open the builder's account and confirm the assigned licence actually includes SharePoint administration, not just Teams. That's the detail that separates a qualifying base licence from a near-miss like Teams Essentials. Then, inside Copilot Studio itself, open any test agent and try Publish, even to a private test audience of one. If the publish flow completes, you know the Copilot Studio user licence is in place. If it doesn't, you've found the gap on day one instead of on the day it matters.
Once the licensing is sorted and the agent is ready to publish, the next question is whether it's actually trustworthy. See how to test a Copilot agent before it goes live for the evaluation categories that catch what a demo won't. And before it goes in front of an audience wider than your pilot group, read about the layered defence a grounded agent needs against indirect prompt injection.
The free first module of FluentWorkForce covers this hands-on, including the licensing walkthrough and the exact 403 errors you'll hit in a real tenant. Start Module 1 free → Rolling this out across a team instead? Talk to us →