Home / artificial-intelligence-machine-learning / Microsoft 365 Certified: Copilot and Agent Administration Fundamentals (AB-900) / Cheat Sheet
Microsoft 365 Certified: Copilot and Agent Administration Fundamentals (AB-900)

AB-900 Cheat Sheet

AB-900 Tests Whether You Can Govern Microsoft 365 Data and Administer Copilot and Agents Safely

AB-900 rewards understanding how Microsoft 365 identity, permissions and Purview controls shape what Copilot and agents can reach, and handling basic Copilot and agent administration.

Check Your Readiness →
Among the harder certs
Avg: Not published by Microsoft
Pass: 750 / 1000
Most candidates understand Microsoft 365 Certified: Copilot and Agent Administration Fundamentals (AB-900) concepts — and still fail. This exam tests how you apply knowledge under pressure.

AB-900 Decision Framework

Data protection and governance is the largest domain at 35-40%, followed by core Microsoft 365 services (30-35%) and Copilot and agent administration (25-30%). Most scenarios reduce to who can access what, and which control changes that.

  1. 01
    Identify the Object — Recognise the Microsoft 365 object or admin center involved: users, licenses, groups, mailboxes, SharePoint sites, Teams or agents.
  2. 02
    Secure Identity — Apply Zero Trust with Microsoft Entra ID, MFA, Conditional Access and Privileged Identity Management, and use sign-in logs to troubleshoot.
  3. 03
    Protect the Data — Classify and protect content with sensitivity labels, DLP and retention, and spot risk with Compliance Manager and activity reports.
  4. 04
    Control Copilot Exposure — Remember Copilot respects existing permissions, so find and fix oversharing with data access governance and SharePoint Advanced Management, and watch AI activity with DSPM for AI.
  5. 05
    Administer Copilot and Agents — Assign licenses or pay-as-you-go billing, control agent access and approvals, and monitor usage reports.

Wrong instinct vs correct approach

Overshared HR site before Copilot rollout
✕ Wrong instinct

Block Copilot for everyone until every site has been reviewed by hand.

✓ Correct approach

Run data access governance reports, tighten site permissions, apply restricted access control or restricted content discovery with SharePoint Advanced Management, and label sensitive content. This removes the exposure Copilot would surface.

User cannot sign in
✕ Wrong instinct

Reset the user's password and remove MFA.

✓ Correct approach

Check the Microsoft Entra sign-in logs to see whether a Conditional Access policy, MFA requirement or risky sign-in blocked the attempt, then fix the specific cause. Removing MFA weakens security without diagnosing anything.

Users publishing agents without review
✕ Wrong instinct

Remove Copilot licenses from users who build agents.

✓ Correct approach

Configure who can access and publish agents and require the agent approval process in the admin center, then monitor agents in the Microsoft 365 and Power Platform admin centers. Governance keeps the benefit while controlling risk.

Know these cold

  • ▸ Copilot sees only what the user can already see.
  • ▸ Sensitivity labels protect; retention labels keep or delete.
  • ▸ Zero Trust — erify explicitly, least privilege, assume breach.
  • ▸ Conditional Access needs Entra ID P1; PIM needs P2.
  • ▸ DLP stops sensitive data from being shared; labels classify it.
  • ▸ Fix oversharing before you deploy Copilot.
  • ▸ Sign-in problems start in the Entra sign-in logs.

Can you answer these without checking your notes?

In this scenario: "Overshared HR site before Copilot rollout" — what should you do first?
Run data access governance reports, tighten site permissions, apply restricted access control or restricted content discovery with SharePoint Advanced Management, and label sensitive content. This removes the exposure Copilot would surface.
In this scenario: "User cannot sign in" — what should you do first?
Check the Microsoft Entra sign-in logs to see whether a Conditional Access policy, MFA requirement or risky sign-in blocked the attempt, then fix the specific cause. Removing MFA weakens security without diagnosing anything.
In this scenario: "Users publishing agents without review" — what should you do first?
Configure who can access and publish agents and require the agent approval process in the admin center, then monitor agents in the Microsoft 365 and Power Platform admin centers. Governance keeps the benefit while controlling risk.

Common Exam Mistakes — What candidates get wrong

Believing Copilot bypasses permissions

Microsoft 365 Copilot only grounds responses in content the signed-in user already has permission to access through Microsoft Graph. The real risk is existing oversharing, which Copilot makes easier to find, so the fix is permissions and governance.

Confusing sensitivity labels and retention labels

Sensitivity labels classify and protect content, for example with encryption, watermarks or access restrictions. Retention labels and policies decide how long content is kept and whether it is deleted afterwards.

Misremembering the Zero Trust principles

Microsoft's Zero Trust model has three principles: verify explicitly, use least privilege access and assume breach. Network location alone is never treated as proof of trust.

Forgetting the license behind identity features

Conditional Access requires Microsoft Entra ID P1 and Privileged Identity Management requires Entra ID P2 (both included in some Microsoft 365 suites). Tenants without them rely on security defaults for baseline MFA.

Treating pay-as-you-go as a Copilot license

Microsoft 365 Copilot is a per-user license assigned in the Microsoft 365 admin center. Pay-as-you-go billing instead charges metered usage, such as agent use by people without that license, to an Azure subscription through a billing policy.

Resources to help you pass Copilot & Agent Administration AB-900 on your first attempt

Find out whether governance, core services or Copilot administration is costing you AB-900 points.