Skip to content

Licensing & prerequisites

The single most common blocker on the ramp is "the walkthrough describes a feature I can't see." Almost always that's a licensing or admin-enablement gap, not a mistake on your part. This page maps what each stage actually needs.

Unofficial — verify before you buy

Licensing and feature availability change often and vary by tenant, region, and plan. Treat this as a planning aid, not a contract. Confirm specifics with your Microsoft account team or the official Microsoft 365 Copilot licensing docs.

At a glance

Stage Core requirement Special access Who enables it How it's billed
1 · Chat Microsoft 365 Copilot license (for work-grounded answers) — IT assigns the license Per-user M365 Copilot license
2 · First-Party Agents Microsoft 365 Copilot license Some agents roll out in waves IT + the agent's admin controls Included in the M365 Copilot license
3 · Cowork Microsoft 365 Copilot license Frontier enrollment for the full feature set Account team / Global Admin License covers licensed users; unlicensed usage metered as Copilot Credits
4 · Agent Builder Microsoft 365 Copilot license Agent Builder enabled for makers IT (maker permissions) Included in the license; metered features (e.g. tenant-graph grounding) accrue Copilot Credits
6 · Copilot Studio Copilot Studio license + Power Platform environment Connectors, auth, publishing rights IT / Power Platform admin Copilot Credits — pay-as-you-go, message packs, or pre-purchase
7 · Foundry Azure subscription + Microsoft Foundry project Developer skills, Azure RBAC, CI/CD Engineering / Azure admin Azure consumption — model inference tokens + Azure resources

Stage by stage

Stage 1 · Chat

  • License: A Microsoft 365 Copilot per-user license (on top of a qualifying Microsoft 365 plan) is what unlocks answers grounded in your email, files, chats, and meetings.
  • Without a license: Copilot Chat still works for general, web-grounded questions — a fine place to build the prompting habit — but it can't reason over your work content.
  • Admin must: Assign the license and confirm Copilot is turned on for the user.

Stage 2 · First-Party Agents

  • License: Covered by the same Microsoft 365 Copilot license — the prebuilt agents are included, not sold separately.
  • Watch for: Individual agents (Researcher, Analyst, Facilitator, and others) graduate from preview to GA on their own timelines and can be governed per-tenant, so the exact roster you see may differ.
  • Admin must: Confirm the specific agents are enabled and rolled out to the right users.

Stage 3 · Cowork

  • License: Microsoft 365 Copilot. Basic end-to-end task delegation and document synthesis work with standard licensing.
  • Special access: The fuller Cowork capabilities — autonomous multi-step runs, recurring background tasks, and advanced Copilot Pages features — often require Frontier enrollment, Microsoft's early-access program. Walkthroughs that need it are marked on the Cowork stage page.
  • Admin must: Nominate the tenant for Frontier (via your CSM / AE / FastTrack contact) or opt in through the Frontier portal if eligible.

Stage 4 · Agent Builder

  • License: Microsoft 365 Copilot — Agent Builder lives inside the M365 Copilot experience.
  • Special access: Your tenant must allow makers to create and share agents; some orgs restrict this.
  • Admin must: Grant agent-creation/sharing permissions and set any approval or publishing controls.

Stage 6 · Copilot Studio

  • License: A Copilot Studio license (standalone capacity or a qualifying bundle) plus a Power Platform environment to build in.
  • Special access: Building real agents pulls in more moving parts — connectors to other systems, Entra ID authentication, publishing rights to Teams/web, and DLP policies that govern what an agent may touch.
  • Admin must: Provision the environment, grant maker roles, approve connectors, and set governance guardrails. See Govern and monitor agents at scale.

Quick self-diagnosis

I can't see a feature a walkthrough describes — what do I check?
  1. License — do you have a Microsoft 365 Copilot license assigned (Stages 1–4) or a Copilot Studio license (Stage 6)? Your IT admin can confirm.
  2. Rollout wave — for first-party agents and newer capabilities, the feature may still be rolling out to your tenant.
  3. Frontier — for the advanced Cowork features, your tenant may need Frontier enrollment.
  4. Admin policy — maker permissions, connector approvals, and DLP can all hide or block a capability even when it's licensed.

📚 Learn more.

Was this page helpful?

Found an issue or want to suggest an improvement? Open a GitHub issue  ·  Star on GitHub