AB-900 - Perform basic administrative tasks for Copilot and agents (30% of the exam) - Section 3.1
Understand the features and capabilities of Copilot and agents, and the licensing models behind them.
Built-in capabilities of Copilot versus agents; the Copilot monthly licence model compared to pay-as-you-go, including SharePoint; which Copilot features can be enabled or disabled; and use cases for Researcher, Analyst and custom agents.
Microsoft 365 Copilot licencepay-as-you-go billingResearcherAnalystcustom agentsCopilot feature controls
Practice question for this objective
lock_openFree samplePerform basic administrative tasks for Copilot and agentsmedium
An administrator wants to turn off a specific optional Microsoft 365 Copilot capability, such as web content grounding in Copilot Chat, for the whole tenant while leaving the rest of Copilot enabled. From which admin experience are these Copilot feature controls managed?
AThe Microsoft Purview portal, which exposes Copilot settings and feature controls for the tenant
BMicrosoft Entra ID, which exposes Copilot settings and feature controls for the tenant
CThe Microsoft Power Platform admin centre, which exposes Copilot settings and feature controls for the tenant
DThe Microsoft 365 admin centre, which exposes Copilot settings and feature controls for the tenantcheck_circle Correct
Identify the Microsoft 365 admin centre as the place administrators manage tenant-wide Microsoft 365 Copilot feature controls. Tenant-level Copilot feature controls, such as enabling or disabling web content grounding, are surfaced in the Copilot settings of the Microsoft 365 admin centre, making it the correct admin experience.
Why A is wrong: Purview governs compliance and data protection; it is tempting because it touches Copilot data, but it does not host the Copilot feature on and off controls.
Why B is wrong: Entra ID manages identity and access such as conditional access, not the optional Copilot capability toggles for the tenant.
Why C is wrong: The Power Platform admin centre governs environments and connectors for Power Platform; it is not where Microsoft 365 Copilot feature controls live.
Why D is correct: Copilot feature controls, including toggles such as web content grounding, are managed from the Copilot settings surfaced in the Microsoft 365 admin centre.
Exam traps in Perform basic administrative tasks for Copilot and agents
Answers that look right on this material and are not. Each one is a distractor from a different question in the AB-900 bank for this domain.
The Microsoft Entra admin center, because Copilot feature availability is defined as an identity role assignment
errorWhy it is wrong: Entra manages identity, groups, and access, which makes it tempting, but Copilot feature enablement is not configured as an identity role there.
The monthly per-user licence bills each user only for the prompts they submit, whereas pay-as-you-go charges a single flat annual fee for the whole tenant regardless of usage.
errorWhy it is wrong: Tempting because it inverts the two models, but it is wrong: the per-user licence is a fixed seat fee, not per-prompt metering, and pay-as-you-go is consumption-based, not a flat annual tenant fee.
They are configured per user inside each person's Copilot app settings, so a policy applied there governs the whole organisation.
errorWhy it is wrong: Tempting because users see some personal toggles, but per-user app settings do not set organisation-wide policy, so this misplaces the control.