AB-900 Skills measured as of 22 Jul 2026
Microsoft August 22, 2026 8 min read

AB-900 Domain 3 Deep Dive: Copilot Licensing, Pay-As-You-Go and Agent Lifecycle

Domain 3 is the smallest slice of AB-900 and the one with the least written about it. Every objective, mapped to what you actually click in the Microsoft 365 and Power Platform admin centres.

AB-900 domain 3 Copilot licensing and agent administration tasks

Domain 3 of AB-900 is worth 25 to 30 percent of your score. It is the smallest of the three domains, and it is also the one with almost no independent study material written about it, because the features it covers are new enough that most prep content still predates them.

This brief walks the domain objective by objective, exactly as Microsoft lists it in the skills-measured document published 22 July 2026.

What domain 3 actually asks

The domain splits into three sub-objectives, and it helps to see them as a progression: understand the capabilities, then administer Copilot, then administer agents.

Understand features and capabilities of Copilot and agentsSub-objective 1
Perform basic administrative tasks for CopilotSub-objective 2
Perform basic administrative tasks for agentsSub-objective 3
Framing that helps

Every objective in this domain answers one of two questions: who is allowed to use this? (licensing, access, approval) or what is it doing now? (usage, billing, operational insights, lifecycle). Sort each objective into one of those two buckets as you revise and the domain gets noticeably smaller.

Copilot capabilities versus agents

The first objective asks you to compare the built-in capabilities of Copilot and agents. The distinction the exam is reaching for:

Microsoft 365 CopilotAgents
What it isAn assistant built into the Microsoft 365 appsA scoped, purpose-built assistant over selected knowledge or actions
Scope of dataGrounded in your work data via Microsoft GraphGrounded in whatever sources the agent is configured against
Who creates itProvided by Microsoft, enabled by adminsBuilt by makers, then approved and governed by admins
Commercial modelPer-user monthly licenceMonthly licence or pay-as-you-go consumption
Admin surfaceMicrosoft 365 admin centerMicrosoft 365 admin center and Power Platform admin center

The practical consequence, and a likely question angle: turning Copilot on for a user is a licensing decision, whereas letting a user build and publish an agent is a governance decision with an approval workflow behind it.

Monthly licence versus pay-as-you-go

Microsoft calls this out specifically: compare Copilot monthly license model to pay-as-you-go, including SharePoint. That trailing “including SharePoint” is not decoration — it is telling you SharePoint agents are a named pay-as-you-go scenario.

Monthly licencePay-as-you-go
Billing basisPer user, per month, predictableConsumption, billed against an Azure subscription
Best fitA defined population using Copilot dailyOccasional or uneven usage, pilots, or agent workloads
Admin actionAssign licences in the Microsoft 365 admin centerCreate and monitor a billing policy
Risk to managePaying for unused seatsUnbounded spend without monitoring
The exam angle on billing

Do not just memorise that pay-as-you-go exists. The objective is “monitor and manage Copilot pay-as-you-go billing policies” — the testable idea is that consumption billing creates an ongoing admin responsibility that per-seat licensing does not.

What you can turn on and off

The objective reads identify which Copilot features can be enabled or disabled. This is a recognition objective: you are being asked to distinguish the surfaces that are genuinely under admin control from the ones that follow automatically from a licence.

Anchor it to a simple rule — admin control in Microsoft 365 Copilot is mostly exercised through licence assignment, policy, and the underlying permissions of the content itself. If a question implies you can granularly switch off Copilot's access to a specific document through a Copilot toggle, be suspicious; that is usually a permissions or sensitivity-label answer instead.

Researcher, Analyst and custom agents

Three objectives, all phrased as “identify use cases for” — which tells you the exam wants matching, not configuration.

Researcher
A built-in agent for multi-step research — pulling together work data and, where permitted, web sources into a reasoned answer. Use case pattern: “compile a briefing on X drawing on our internal documents and the market”.
Analyst
A built-in agent oriented to working over data to produce analysis rather than prose. Use case pattern: “take this dataset and tell me what is happening in it”.
Custom agents
Built by makers for a specific, narrow job against chosen knowledge sources or actions. Use case pattern: “answer questions about our expense policy and nothing else”. These are the ones that carry an approval and lifecycle burden.

If a scenario describes a broad, open-ended investigation, think Researcher. If it describes reasoning over a dataset, think Analyst. If it describes a repeatable, bounded task tied to particular content, think custom agent.

Copilot administration tasks

Four testable tasks:

  • Assign Copilot licences. Standard licence assignment in the Microsoft 365 admin center, to users or groups. Remember from domain 1 that group-based assignment changes who gets features.
  • Monitor and manage pay-as-you-go billing policies. The consumption counterpart to licensing, as above.
  • Monitor usage and adoption. Two named surfaces: Copilot Analytics and the Microsoft 365 admin center. The framing is adoption — are the licences you bought being used?
  • Manage prompts — saving, sharing, scheduling and deleting. Prompts are a managed object with a lifecycle, not just typed text. Scheduling in particular is easy to miss on a first read.
Most-missed detail

Prompt management includes scheduling. If a question describes a recurring Copilot task that should run without a person triggering it, scheduled prompts is the answer being fished for — not a custom agent.

Agent access, creation, approval and monitoring

The final sub-objective, and the one that most clearly separates AB-900 from a Copilot user course.

Access
Identify how to configure user access to agents. Who may use a published agent, and who may build one. Two different controls; questions like to conflate them.
Create
Create an agent. At fundamentals level this is about knowing the path exists and roughly what it involves — choosing knowledge sources and scoping behaviour — not authoring a production agent.
Approve
Understand the approval process for agents. Agents built by makers do not simply appear for everyone. There is a review and approval step, and this is the governance hinge of the whole domain.
Monitor
Monitor agents — usage, operational insights and lifecycle — across the Microsoft 365 admin center and the Microsoft Power Platform admin center. Both are named explicitly. If an answer option offers only one of them for full lifecycle visibility, read the question again.

The word lifecycle is doing real work here. An agent is created, approved, used, and eventually should be retired — and someone has to notice when one has stopped being used or has drifted from its purpose. That ongoing custody is the responsibility AB-900 is certifying.

Question patterns to expect

Fundamentals questions in this domain fall into a few recognisable shapes. Learning the shapes is faster than memorising every permutation.

PatternWhat it sounds likeHow to attack it
Which admin centre?“An admin needs to review agent usage across the organisation. Where do they go?”Copilot usage and licences → Microsoft 365 admin center. Agent lifecycle also involves the Power Platform admin center
Licence or consumption?“A team will use an agent occasionally during a three-month pilot”Irregular or short-lived usage → pay-as-you-go. Steady daily use → per-user licences
Which agent?“A user needs a briefing drawn from internal documents and public sources”Broad investigation → Researcher. Reasoning over data → Analyst. Bounded repeatable task → custom agent
Missing governance step“A maker built an agent but colleagues cannot see it”Think approval and user access configuration before assuming a technical fault
Actually a domain 2 question“Copilot surfaced a document a user should not have seen”Permissions, sensitivity labels or SharePoint oversharing — not a Copilot setting

That last row deserves dwelling on. A meaningful share of questions that look like Copilot administration resolve to permissions and labelling, because that is genuinely how the product works — Copilot inherits the access the user already has. If an answer option offers a Copilot-level switch to hide one specific document, treat it as the distractor.

A five-question self-check

If you can answer these without looking anything up, domain 3 is not where you will lose the exam.

  1. Name the two admin centres involved in monitoring agent lifecycle.
  2. Give one scenario where pay-as-you-go beats a monthly licence, and say why.
  3. What are the four verbs in the prompt-management objective? One of them surprises most people.
  4. Distinguish Researcher from Analyst in one sentence each.
  5. What has to happen between a maker building an agent and colleagues using it?
Answers, briefly

1. Microsoft 365 admin center and Power Platform admin center. 2. Short pilots or uneven usage — you pay for consumption rather than idle seats. 3. Saving, sharing, scheduling and deleting. 4. Researcher runs multi-step research across sources; Analyst reasons over data to produce analysis. 5. Approval, plus configuration of user access.

How this domain connects to the rest of the exam

Domain 3 does not stand alone. An agent's blast radius is determined by the permissions and sensitivity labels from domain 2, and by the groups and roles from domain 1. Expect at least some questions that look like domain 3 but resolve to a Purview or Entra answer — which is exactly why the full exam guide recommends studying Purview first.

Frequently Asked Questions

What percentage of AB-900 is Copilot and agent administration?

Domain 3, 'Perform basic administrative tasks for Copilot and agents', is 25 to 30 percent of the exam. It is the smallest of the three domains.

What is the difference between a Copilot licence and pay-as-you-go?

A monthly Copilot licence is a per-user subscription assigned in the admin centre. Pay-as-you-go bills consumption against an Azure subscription instead, and the exam expects you to know it also applies to SharePoint agents.

What are Researcher and Analyst in Microsoft 365 Copilot?

They are specialised built-in agents. Researcher handles multi-step research across your work data and the web; Analyst works over data to produce analysis. AB-900 asks you to identify use cases for each rather than configure them.

Which admin centres do I need for agent monitoring?

The Microsoft 365 admin center and the Microsoft Power Platform admin center. AB-900 explicitly names both for monitoring agent usage, operational insights and lifecycle.

Drill Domain 3 Question by Question

Timed practice questions with worked explanations, so you find the weak objective before the exam does.

Browse All Exams
ExamCert

ExamCert Team

Certified IT professionals tracking the cloud, AI, and security certification landscape. Every exam brief is rebuilt against the official skills-measured document on the date shown above.

Practice Before You Book

500–1,000+ practice questions per exam with detailed explanations, across Azure, AWS, GCP, security, and AI certifications.