Overview
Perform basic administrative tasks for Copilot and agents is the domain that most distinguishes AB-900, covering the day-to-day administration of Copilot and agents. It has three objective groups. Understanding Copilot and agent capabilities covers comparing built-in Copilot and agent capabilities, the monthly license versus pay-as-you-go model including SharePoint, which features can be enabled or disabled, and use cases for Researcher, Analyst and custom agents. Performing Copilot tasks covers assigning Copilot licenses, monitoring and managing pay-as-you-go billing, monitoring usage and adoption with Copilot Analytics and the Microsoft 365 admin center, and managing prompts. Performing agent tasks covers configuring user access to agents, creating an agent, understanding the approval process, and monitoring agents through the Microsoft 365 admin center and the Power Platform admin center.
At 25–30%, this domain tests the practical administration of an AI-enabled tenant. The exam rewards knowing the licensing models, how to monitor adoption, and the agent lifecycle from creation through approval to monitoring.
How it's tested
AB-900 questions in this domain describe a Copilot or agent administration need and ask how to license, monitor or manage it. Read the full scenario and all options before choosing, picking the feature or tool that most precisely matches what is described.
-
Licensing model
A Copilot usage pattern is described, and you choose the monthly license or pay-as-you-go model.
-
Monitor adoption
A usage-visibility need is described, and you choose Copilot Analytics or the admin center.
-
Agent lifecycle
An agent administration need is described, and you apply access, creation, approval or monitoring.
An organization wants to let a department use a Copilot capability occasionally and pay only for what it uses, rather than committing to a per-user monthly license for everyone. A monthly Copilot license charges a fixed amount per user regardless of usage. A pay-as-you-go billing model charges based on consumption, which suits occasional or variable use, so the administrator configures pay-as-you-go billing, the consumption-based option the exam expects.
Functional groups 3
Official functional groups from the Microsoft outline, in outline order.
3.1 Understand features and capabilities of Copilot and agentsCopilot and agent capabilities, licensing models, enabling features, and use cases.
- What it means
- This covers comparing the built-in capabilities of Copilot and agents, comparing the Copilot monthly license model to pay-as-you-go including SharePoint, identifying which Copilot features can be enabled or disabled, and use cases for Researcher, Analyst and custom agents.
- What to understand
- Copilot provides AI assistance across Microsoft 365, and agents extend it for specific tasks. Licensing is either a per-user monthly subscription or consumption-based pay-as-you-go. Administrators can enable or disable specific features. Researcher and Analyst are specialized capabilities, and custom agents address bespoke needs.
- How it shows up
- A capability or licensing need is described, and you must choose the model or identify the use case.
- Common confusion
- Confusing the monthly Copilot license with the pay-as-you-go model; monthly is a fixed per-user subscription, while pay-as-you-go is consumption-based.
3.2 Perform basic administrative tasks for CopilotAssign licenses, manage billing, monitor adoption, and manage prompts.
- What it means
- This covers assigning Copilot licenses, monitoring and managing Copilot pay-as-you-go billing policies, monitoring Copilot usage and adoption with Copilot Analytics and the Microsoft 365 admin center, and managing prompts including saving, sharing, scheduling and deleting.
- What to understand
- Copilot licenses are assigned to users, directly or via groups. Pay-as-you-go billing policies control consumption-based spend. Copilot Analytics and the admin center show adoption and usage. Prompt management lets administrators and users save, share, schedule and delete prompts to standardize and govern AI use.
- How it shows up
- A Copilot administration need is described, and you must choose license assignment, billing management, adoption monitoring or prompt management.
- Common confusion
- Confusing adoption monitoring tools; Copilot Analytics and the Microsoft 365 admin center both report usage at different levels.
3.3 Perform basic administrative tasks for agentsConfigure access, create an agent, understand approval, and monitor the lifecycle.
- What it means
- This covers configuring user access to agents, creating an agent, understanding the approval process for agents, and monitoring agents including usage, operational insights and the agent lifecycle, using the Microsoft 365 admin center and the Power Platform admin center.
- What to understand
- Agents are managed through a lifecycle: administrators configure who can access them, agents are created, an approval process governs their release, and they are monitored for usage and operational health. The Microsoft 365 and Power Platform admin centers provide agent administration and insights.
- How it shows up
- An agent administration need is described, and you must apply access configuration, creation, approval or monitoring.
- Common confusion
- Overlooking the agent approval process; agents go through approval before broad use, not straight from creation to everyone.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Copilot vs. agents
Broad AI assistance versus task-specific extensions.
- Remember
- Agents extend Copilot for specific needs.
- Tested as
- Capability questions.
- Trap
- Treating agents as identical to Copilot.
-
Monthly license vs. pay-as-you-go
Fixed per-user subscription versus consumption-based.
- Remember
- Pay-as-you-go suits variable use.
- Tested as
- Licensing questions.
- Trap
- Confusing the two models.
-
Enabling and disabling features
Controlling which Copilot features are available.
- Remember
- Admins govern feature availability.
- Tested as
- Administration questions.
- Trap
- Assuming all features are always on.
-
Researcher and Analyst
Specialized Copilot capabilities.
- Remember
- They address research and analysis use cases.
- Tested as
- Use-case questions.
- Trap
- Confusing the two roles.
-
Custom agents
Agents built for bespoke tasks.
- Remember
- They extend Copilot to specific workflows.
- Tested as
- Use-case questions.
- Trap
- Using a built-in where a custom agent fits.
-
Assigning Copilot licenses
Granting Copilot access to users.
- Remember
- Assign directly or via groups.
- Tested as
- Administration questions.
- Trap
- Expecting Copilot without a license.
-
Pay-as-you-go billing policies
Control consumption-based Copilot spend.
- Remember
- They manage variable costs.
- Tested as
- Billing questions.
- Trap
- Leaving consumption uncontrolled.
-
Copilot Analytics
Reports Copilot usage and adoption.
- Remember
- It measures how Copilot is used.
- Tested as
- Adoption questions.
- Trap
- Not monitoring adoption.
-
Prompt management
Save, share, schedule and delete prompts.
- Remember
- It standardizes and governs AI use.
- Tested as
- Administration questions.
- Trap
- Overlooking prompt governance.
-
Agent access configuration
Controlling who can use an agent.
- Remember
- It governs agent availability.
- Tested as
- Agent questions.
- Trap
- Giving everyone access by default.
-
Agent approval and lifecycle
Approval before release and ongoing monitoring.
- Remember
- Agents are governed through a lifecycle.
- Tested as
- Agent questions.
- Trap
- Skipping approval.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Monthly license vs. pay-as-you-go
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Monthly license | Fixed per-user subscription | Predictable cost for steady use | Using it for occasional use |
| Pay-as-you-go | Consumption-based billing | Suits variable or occasional use | Confusing with the monthly model |
Copilot vs. Researcher vs. Analyst vs. custom agents
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Copilot | Broad AI assistance | General productivity | Expecting specialized output |
| Researcher | Deep research capability | Research use cases | Confusing with Analyst |
| Analyst | Data analysis capability | Analysis use cases | Confusing with Researcher |
| Custom agents | Bespoke task agents | Specific workflows | Using a built-in instead |
Agent lifecycle stages
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Access configuration | Who can use the agent | Governs availability | Giving all users access |
| Creation | Building the agent | Produces the agent | Skipping governance |
| Approval | Governed release | Controls rollout | Releasing without approval |
| Monitoring | Usage and operational insights | Ongoing governance | Not monitoring after release |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Monthly for occasional use
- What candidates pick
- Recommend per-user monthly Copilot licenses for occasional, variable use.
- Why it looks right
- Monthly licensing is familiar.
- Why it's wrong
- Pay-as-you-go billing charges by consumption, which suits occasional or variable use better than fixed monthly licenses.
Clue to watch for The usage is occasional or variable and cost should follow it.
-
Copilot without a license
- What candidates pick
- Expect a user to use Copilot without an assigned license.
- Why it looks right
- Copilot is in the tenant.
- Why it's wrong
- Copilot access requires an assigned license, directly or via a group.
Clue to watch for A user cannot access Copilot features.
-
Skip agent approval
- What candidates pick
- Release a new agent to all users straight after creation.
- Why it looks right
- It is faster.
- Why it's wrong
- Agents go through an approval process before broad use as part of their governed lifecycle.
Clue to watch for A new agent is being rolled out organization-wide.
-
No adoption monitoring
- What candidates pick
- Deploy Copilot and not track whether it is used.
- Why it looks right
- Deployment seems complete.
- Why it's wrong
- Copilot Analytics and the admin center monitor usage and adoption, which guides rollout and value.
Clue to watch for The organization wants to understand Copilot usage.
-
Researcher is Analyst
- What candidates pick
- Use the Analyst capability for a deep research task.
- Why it looks right
- Both are specialized.
- Why it's wrong
- Researcher addresses research use cases; Analyst addresses data analysis.
Clue to watch for The task is research versus data analysis.
Answer framework
For any Domain 3 scenario, use these steps to find the answer AB-900 expects.
- Identify whether the need is understanding capabilities and licensing, a Copilot task, or an agent task.
- For licensing, choose the monthly per-user license for steady use or pay-as-you-go billing for occasional or variable use.
- For Copilot administration, assign licenses, manage pay-as-you-go billing, monitor adoption with Copilot Analytics and the admin center, and manage prompts.
- For agents, configure user access, create the agent, follow the approval process before release, and monitor usage and lifecycle in the Microsoft 365 and Power Platform admin centers.
- Match specialized capabilities to use cases, choosing Researcher, Analyst or a custom agent as the task requires. Where two options seem to fit, pick the one that most precisely matches the scenario.
Practice question
Want more like this? The AB-900 practice test has questions for every domain.
Checklist
0 of 10
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
This domain is what makes AB-900 an AI-administration exam, so focus on the practical tasks. Start with capabilities and licensing: understand how Copilot and agents differ, and firmly distinguish the per-user monthly license from consumption-based pay-as-you-go, which is a frequent decision point.
Next, learn the Copilot administration tasks: assigning licenses, managing pay-as-you-go billing, monitoring adoption with Copilot Analytics and the admin center, and managing prompts. Then learn the agent lifecycle, access configuration, creation, approval and monitoring, across the Microsoft 365 and Power Platform admin centers, and do not skip the approval step.
Because the exam is practical for a fundamentals level, exploring the Copilot and agent administration experiences in a trial tenant helps. This is the final domain, so finish with full practice tests spanning all three, and remember the whole exam centers on administering an AI-enabled tenant. AB-900 is more hands-on than older fundamentals exams, so use a free Microsoft 365 developer tenant to explore the admin experiences, and review missed practice questions by group to find weak spots.
FAQ
How much of AB-900 is Domain 3?
Perform basic administrative tasks for Copilot and agents is 25–30% of the exam, and it is the domain that most distinguishes AB-900 as an AI-administration exam.
What is the difference between the monthly Copilot license and pay-as-you-go?
The monthly license is a fixed per-user subscription suited to steady use. Pay-as-you-go charges based on actual consumption, which suits occasional or variable use.
Do users need a license to use Copilot?
Yes. Copilot access requires an assigned license, given to users directly or through a group, in addition to any pay-as-you-go consumption billing.
How do I monitor Copilot adoption?
With Copilot Analytics and the Microsoft 365 admin center, which report usage and adoption to guide rollout and demonstrate value.
What is the agent lifecycle?
Administrators configure who can access an agent, the agent is created, it goes through an approval process before broad use, and it is then monitored for usage and operational health.
What are Researcher and Analyst?
Specialized Copilot capabilities: Researcher addresses deep research use cases, and Analyst addresses data analysis use cases. Custom agents address bespoke workflows.
How does Domain 3 connect to the rest of the exam?
It administers the Copilot and agents that operate within the Microsoft 365 foundation of Domain 1 and the data governance of Domain 2, completing the picture of an AI-enabled tenant.
Other Cloud Computing certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- AWS Certified Solutions Architect - Associate Study guide
- AWS Certified Cloud Practitioner Study guide
- AWS Certified SysOps Administrator - Associate Study guide
- AWS Certified Solutions Architect - Professional Study guide
- Azure Developer Associate Study guide
- Google Cloud Associate Cloud Engineer Study guide
- CompTIA Cloud+ Study guide
- Microsoft Certified: Azure Fundamentals Study guide
- AWS Certified Developer - Associate Study guide
- HashiCorp Certified: Terraform Associate Study guide
- Azure Administrator Associate Study guide
- Azure Solutions Architect Expert Study guide
Test your Domain 3 knowledge
You have covered Copilot and agent capabilities, licensing, monitoring and the agent lifecycle. Test whether you can administer an AI-enabled tenant under exam conditions.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the AB-900 AI tutor Get any concept explained your way