Perform basic administrative tasks for Copilot and agents

An organisation runs a workload where employees only occasionally use a custom agent, and it wants to be charged for the consumption those interactions generate rather than committing to a fixed per-user subscription. Which Microsoft 365 Copilot commercial model matches this requirement?

• AThe Microsoft 365 Copilot per-user monthly licence, which grants each assigned user unlimited use for a fixed recurring fee
• BA Microsoft Entra ID P2 subscription, which includes Copilot agent usage as part of its identity governance features
• CPay-as-you-go billing, which meters agent consumption and charges the organisation for the messages actually usedcheck_circle Correct
• DA Microsoft 365 E5 add-on that converts unused Copilot licences into consumption credits automatically

Why A is wrong: This is a real model and is tempting because it is the headline Copilot offer, but it charges a flat fee per assigned user regardless of usage, which is the opposite of paying only for occasional consumption.

Why B is wrong: Entra ID P2 covers identity protection and governance such as Privileged Identity Management; it does not include or meter Copilot agent consumption, so it cannot fulfil the billing requirement.

Why C is correct: Pay-as-you-go bills on metered consumption of agent messages, so an organisation with occasional use pays for what it consumes rather than a fixed per-user fee.

Why D is wrong: This sounds plausible because E5 bundles many add-ons, but no such automatic licence-to-credit conversion add-on exists, making it an invented mechanism.

A research team wants a Microsoft 365 Copilot capability that can perform multi-step research across work data and the web to produce a structured, reasoned report on a complex topic. Which capability is designed for this reasoning-heavy research work?

• AAnalyst, a reasoning agent that runs data analysis over raw datasets to surface trends and calculations
• BThe semantic index, which ranks tenant content so prompt responses draw on the most relevant documents
• CCopilot Studio, the low-code environment used to build and publish custom agents for the organisation
• DResearcher, a reasoning agent that carries out multi-step research across work and web data to build a structured reportcheck_circle Correct

Why A is wrong: Analyst is a genuine reasoning agent, which makes it tempting, but it focuses on interrogating raw data such as spreadsheets to produce analytical outputs, not multi-step topic research and reporting.

Why B is wrong: The semantic index improves retrieval relevance behind the scenes; it is infrastructure that supports responses, not an agent that conducts multi-step research on request.

Why C is wrong: Copilot Studio is the authoring tool for creating custom agents, so it is a builder rather than the ready-made research capability the team is asking for.

Why D is correct: Researcher is the reasoning agent purpose-built to run deep, multi-step investigations across work content and the web and return a structured report, which matches the requirement exactly.

An administrator needs to assign Microsoft 365 Copilot licences to 200 staff and confirm each has a qualifying base licence. Which admin centre is the correct place to assign the Copilot licences to those users?

• AThe Microsoft 365 admin center, under Billing and user licence assignmentcheck_circle Correct
• BThe Microsoft Purview portal, under data lifecycle management
• CThe Microsoft Entra admin center, under enterprise applications
• DThe Teams admin center, under Copilot policies

Why A is correct: Copilot is a per-user add-on licence, and licence assignment for Microsoft 365 products is handled in the Microsoft 365 admin center, so this is correct.

Why B is wrong: The Purview portal governs compliance controls such as retention and DLP; it is tempting because Copilot governance often involves Purview, but it does not assign product licences.

Why C is wrong: Entra manages identity, groups, and app registrations, and can drive group-based licensing, but the Copilot add-on itself is assigned through the Microsoft 365 admin center, not the enterprise applications blade.

Why D is wrong: The Teams admin center configures Teams experiences and meeting policies; it is plausible because Copilot appears in Teams, but it does not assign the Copilot licence to users.

An organisation is rolling out agents built with Microsoft Copilot Studio and needs to govern them tenant-wide: view which agents exist, control which environments they run in, and manage data policies that apply to them. Which admin experience is purpose-built for this environment-level governance of agents?

• AThe Microsoft Entra admin center, which is the tenant-wide governance point for Copilot Studio agents and their environments
• BThe Microsoft Purview portal, which centralises environment management and data policies for Copilot Studio agents
• CThe Microsoft Power Platform admin center, which manages environments, data policies, and the agents running within themcheck_circle Correct
• DThe Microsoft 365 admin center, which is where environments and data policies for agents are configured

Why A is wrong: Entra handles identity, users, groups, and access, and it does register app identities, but it does not manage Power Platform environments or the agents inside them, so it is not the governance surface described.

Why B is wrong: The Purview portal governs data classification, compliance, and risk across the tenant, which is adjacent and tempting, but it does not create or manage Power Platform environments where agents run.

Why C is correct: Copilot Studio agents live inside Power Platform environments, so the Power Platform admin center is where an administrator governs environments, applies data loss prevention policies, and oversees the agents deployed across the tenant.

Why D is wrong: The Microsoft 365 admin center manages users, licences, and core service settings, so it is a natural first guess, but Power Platform environments and their agent data policies are configured in the Power Platform admin center instead.