Microsoft AB-900: Copilot and Agent Exam Blueprint

AB-900 is a beginner-level Microsoft certification exam for administrators who need to understand how Microsoft 365, security, governance, Copilot, and agents fit together. The current AB-900 exam is not a general AI fundamentals test and it is not simply a renamed Microsoft 365 fundamentals exam. Its purpose is narrower and more operational: support, secure, protect, and administer an AI-enabled Microsoft 365 environment.

The English AB-900 exam follows the Microsoft study guide effective October 14, 2026. Its three major areas are Microsoft 365 features and objects (30–35%), data protection and governance for Microsoft 365 and Copilot (35–40%), and basic Copilot and agent administration (25–30%). This is the current English blueprint, not a future version; localized exam update schedules may differ.

That timing matters because AB-900 sits in a fast-moving part of the Microsoft stack. The durable way to read the blueprint is to focus on relationships: users and groups determine access; Microsoft Entra controls identity; SharePoint and Teams hold collaborative data; Microsoft Purview applies classification and governance; Copilot uses permitted organizational context; and agents add another layer of access, lifecycle, monitoring, and control. The exam is testing whether those pieces form a coherent administrative model in your head.

Microsoft 365 objects are the base layer of the exam

The first domain begins with ordinary Microsoft 365 administration. Candidates should recognize how users, groups, licenses, domains, mailboxes, distribution groups, SharePoint sites and libraries, teams, channels, and policies relate to one another. This is why practical familiarity with the Microsoft 365 admin center matters: AB-900 expects you to know which administrative surface is appropriate for a given object rather than treating Microsoft 365 as one undifferentiated portal.

The exam is foundational, so it does not expect the implementation depth of a specialist administrator exam. It does expect enough object awareness to avoid obvious category errors. A mailbox is not governed through the same interface as a SharePoint site. A license assigned to a group affects access differently from a document permission. A Teams policy is not the same control as a sensitivity label. These distinctions become more important once Copilot is involved because AI does not remove the underlying Microsoft 365 permission model.

Candidates coming from the older MS-900 Microsoft 365 Fundamentals path may recognize some platform concepts, but AB-900 applies them to AI-enabled administration. The overlap is useful background, not proof that the exams are interchangeable.

Identity and security determine what Copilot can safely reach

Identity is where the exam moves from inventory to control. Microsoft Entra ID, authentication methods, authorization, Conditional Access, single sign-on, risky sign-ins, audit logs, Privileged Identity Management, app registrations, and enterprise applications all shape how people and workloads access Microsoft 365. The important study question is not merely what each feature is called, but what risk it addresses.

For example, Conditional Access evaluates conditions and applies access controls; MFA strengthens authentication; PIM reduces standing privileged access; audit logs provide evidence of activity; and app registrations or enterprise applications represent identities and integrations that can receive permissions. When a scenario involves Copilot, the same identity principles remain in force because Copilot operates within the user’s permitted context rather than bypassing authorization.

The broader Zero Trust principles are therefore practical exam logic. Verify explicitly, use least privilege, and assume breach are not slogans to memorize separately from Microsoft 365 administration. They explain why identity, device state, risk, permissions, and monitoring are combined when access is evaluated.

Data protection and governance are the center of gravity

The October 14, 2026 English outline assigns the largest weighting to data protection and governance. Microsoft 365 Copilot depends on identifying sensitive information, understanding who can reach it, governing retention, and detecting risky behaviors.

Microsoft Purview provides the vocabulary for this part of the blueprint: Information Protection, Data Loss Prevention, Insider Risk Management, Communication Compliance, Data Security Posture Management for AI, Data Lifecycle Management, eDiscovery, sensitivity labels, classification, retention, alerts, and activity investigation. A candidate does not need a specialist-level information-security certification merely to prepare for AB-900. SC-400 is retired; the current specialist responsibilities are represented by SC-401, while AB-900 requires a sound understanding of what each Microsoft 365 governance control does.

A practical example is data loss prevention. DLP is relevant when the requirement is to detect or restrict sensitive data movement according to policy. That is different from a sensitivity label, which classifies and can protect content; different again from retention, which governs lifecycle; and different from insider-risk tooling, which looks for patterns of risky user activity. Scenario questions become simpler when the administrative objective is identified before the product feature.

Copilot security is inherited from the Microsoft 365 environment

A recurring misconception is that enabling Copilot creates a separate data-security boundary. In reality, Copilot relies on the permissions and controls already present in Microsoft 365. Microsoft Graph supplies organizational context, and the user’s access determines what information can be grounded into responses. If SharePoint permissions are overly broad, Copilot can expose the consequences of that oversharing more quickly even though it is still respecting those permissions.

That is why the blueprint calls out SharePoint oversharing and the tools used to investigate it. Reviewing SharePoint and Microsoft 365 sharing is useful because AI readiness depends on ordinary access hygiene. Data access governance reports, restricted access controls, and related SharePoint management capabilities help administrators find situations where a large audience can reach content that was never intended to be broadly discoverable.

The exam therefore treats Copilot governance as an extension of existing Microsoft 365 governance. Responsible AI principles matter, but they sit beside concrete controls: permissions, labels, DLP, compliance recommendations, audit evidence, and data-access review.

Copilot administration includes licensing, usage, prompts, and feature controls

The administrative domain covers more than switching Copilot on. Candidates need to understand license assignment, pay-as-you-go concepts, which features can be enabled or disabled, and how usage and adoption are monitored. Microsoft also includes named experiences such as Researcher and Analyst because administrators may need to understand what users are actually being granted access to.

Usage monitoring is not merely a reporting task. It connects adoption with governance. An organization needs to know whether licensed users are actually using Copilot, whether usage patterns justify the investment, and whether new capabilities are creating operational or data-protection concerns. Copilot Analytics and the Microsoft 365 admin center therefore sit at the intersection of adoption and control.

Prompt management is another concrete administrative topic in the published October update, including saving, sharing, scheduling, and deleting prompts. The point is not to turn an administrator into a prompt engineer. It is to understand that prompts can become managed organizational artifacts rather than remaining temporary personal text.

Agents add lifecycle and access questions

Agents extend the environment beyond the built-in Copilot experience. AB-900 expects basic understanding of how user access to agents is configured, how an agent is created, how approval works, and how agents are monitored through Microsoft 365 and Power Platform administrative surfaces. The scope is administrative rather than developer-heavy.

That distinction helps separate AB-900 from the deeper AB-620 AI Agent Builder exam. AB-620 goes into building, integrating, extending, evaluating, and deploying sophisticated Copilot Studio agents. AB-900 asks a different question: once Copilot and agents exist in the tenant, how does an administrator provide access, monitor use, apply governance, and maintain control?

For exam preparation, avoid studying advanced agent architecture simply because it is interesting. Stay at the level of user access, approval, lifecycle, monitoring, basic creation, and the relationship between Microsoft 365 and Power Platform administration.

How to use the current October 14, 2026 outline

Microsoft’s English AB-900 study guide reflects the October 14, 2026 update. Candidates should use the published weights and detailed objectives as their baseline, while checking the official exam listing for later changes or language-specific rollout. Historical notes that call the change forthcoming are outdated.

The good news is that Microsoft describes the changes as mostly minor, not a complete redesign. The same core story remains: Microsoft 365 objects and security, Purview-centered data protection and governance, and Copilot/agent administration. The update sharpens details such as specific admin tasks and named capabilities rather than replacing the certification’s purpose.

This is also why outdated third-party study plans can be risky. A list created before the September 2026 study-guide update may omit newer named features or misstate the relative emphasis. Always reconcile study notes with the live Microsoft page close to the exam date.

AB-900 rewards connected administration, not isolated memorization

A useful mental model is to imagine a user asking Copilot to summarize information from a Microsoft 365 environment. The user identity is controlled through Entra; licenses determine feature access; SharePoint, Teams, Exchange, and other services contain the data; permissions and Graph determine reachable context; Purview and security controls govern sensitive information; the Microsoft certification ecosystem provides deeper role-based paths when a candidate needs more implementation expertise; and administrators monitor usage and agent lifecycle.

If you can trace that path from identity to data to AI experience to governance, most of the blueprint becomes easier to organize. AB-900 is a fundamentals exam, but it is not shallow. It asks whether you can see an AI-enabled Microsoft 365 tenant as a connected administrative system.