3.1 Copilot Licensing and Billing

Quick Answer: Microsoft 365 Copilot is a per-user add-on on top of a qualifying base license. Assign it in the Microsoft 365 admin center under Active users > Licenses and apps. For variable usage, pay-as-you-go meters consumption in Copilot Credits through a linked Azure subscription instead of fixed monthly seats.

Why Licensing Matters on AB-900

Domain 3 — Basic Administrative Tasks for Copilot and Agents — is worth 25–30% of the AB-900 score. Licensing and billing questions test whether you know where admins act, what each model costs, and which prerequisites must exist before users see Copilot. Microsoft writes distractors that swap billing models, confuse purchase with assignment, or point you to the wrong admin center.

Built-in Copilot vs Custom Agents (Licensing Lens)

Microsoft 365 Copilot is the built-in productivity assistant embedded in Word, Excel, PowerPoint, Outlook, Teams, and other M365 apps. It grounds on the tenant semantic index and the signed-in user's Microsoft Graph permissions. Custom agents are organization-built assistants authored in Microsoft Copilot Studio with scoped topics, knowledge sources, and actions. They carry separate governance, approval, and sometimes distinct licensing considerations. AB-900 expects you to distinguish the two before choosing a billing model.

Prerequisite Base Licenses

Before any Copilot add-on works, each user needs a qualifying base license:

Assigning only the Copilot SKU without a base license leaves the user unable to access integrated app experiences. During rollout, admins verify both licenses appear on each pilot user's account.

Monthly Per-User License Model

The monthly per-user license is a fixed subscription: one Copilot seat per licensed user, billed predictably regardless of how heavily that person uses Copilot in a given month. This model fits organizations with steady, organization-wide adoption where finance wants predictable OpEx and HR wants every knowledge worker enabled.

Assignment path: Microsoft 365 admin center → Active users → select user → Licenses and apps → enable Microsoft 365 Copilot. Group-based licensing through Entra security groups scales assignment for departments.

Purchase path: Billing → Purchase services acquires new Copilot seats; assignment is a separate step under Active users.

Pay-as-You-Go Billing Model

Pay-as-you-go suits pilots, seasonal teams, or fluctuating usage where committing to hundreds of monthly seats is premature. Instead of a fixed per-user fee, consumption is metered in Copilot Credits and billed based on actual usage.

Prerequisite: Connect the Microsoft 365 tenant to an Azure subscription in the Microsoft 365 admin center so Microsoft can meter and invoice consumption. Without that link, pay-as-you-go cannot be enabled.

Billing policy management: Admins create and adjust pay-as-you-go billing policies in the Microsoft 365 admin center, controlling cost exposure caps and which workloads consume credits.

On the Exam: If a stem describes fluctuating month-to-month usage or a small pilot avoiding seat commitments, the answer is almost always pay-as-you-go. If it describes predictable enterprise-wide deployment, choose the monthly per-user license.

Copilot Administrator Role

Day-to-day Copilot configuration should not require Global Administrator. Microsoft provides the Copilot Administrator Entra role, scoped to manage Copilot settings, usage policies, and org-wide toggles such as web grounding — without tenant-wide superuser rights. This follows least-privilege access, a Zero Trust principle tested across AB-900.

Microsoft-Built Agents and Licensing

Researcher and Analyst are Microsoft-built reasoning agents included with a Microsoft 365 Copilot license. Pay-as-you-go does not apply to these agents — a common exam trap that reverses the billing relationship.

Worked Scenario: Choosing a Billing Model

A 500-person company launches Copilot to 50 sales reps for a 90-day pilot with uncertain continuation. Finance refuses 50 fixed monthly seats. The administrator should:

1. Link an Azure subscription for metering.
2. Enable pay-as-you-go billing policies in the M365 admin center.
3. Assign base licenses plus enable Copilot access for the pilot group.
4. Monitor consumption through billing reports before converting to per-user licenses if adoption stabilizes.

Common Exam Traps

E5 vs E3 and Copilot Governance Readiness

While Copilot licensing is separate from the base SKU, Microsoft 365 E5 includes advanced Purview capabilities — Insider Risk Management, Communication Compliance, and extended audit — that many organizations rely on when governing Copilot at scale. E3 provides foundational DLP and sensitivity labels but lacks several AI governance tools tested elsewhere on AB-900. When an exam stem ties licensing to comprehensive Copilot governance, E5's bundled compliance stack is often the implied prerequisite even though the Copilot add-on itself attaches to either tier.