Perform basic administrative tasks for Copilot and agents
Copilot Adoption and Prompt Management
ImportantUse operational usage reporting and Copilot Analytics for different questions, and govern prompts as owned content with a lifecycle.
Aligned to the current AB-900 guide, verified July 22, 2026.
Why this matters
AB-900 tests whether you can interpret Copilot adoption evidence correctly and manage saved prompts as owned, permission-aware content.
Must Know
- Microsoft 365 admin-center reports answer operational readiness, assignment, active-use, and feature-use questions.
- Copilot Analytics supports deeper adoption, agent, sentiment, assisted-work, and business-impact analysis, depending on license and role.
- Reports can differ because populations, filters, privacy thresholds, time windows, and refresh delays differ.
- Usage records activity; adoption adds sustained and distributed use; business impact asks whether desired outcomes changed.
- A saved prompt is reusable text; sharing a prompt does not share referenced files or grant source permission.
- Scheduled prompts depend on supported configuration, ownership, and current access.
- Review ownership and delete, transfer, or recreate obsolete or business-critical prompts when people or requirements change.
Compare and Distinguish
- Microsoft 365 admin-center report vs Copilot Analytics: operational usage/adoption administration vs richer organizational adoption, agent, impact, and business-value analysis.
- Usage vs impact: observed activity vs evidence that desired outcomes changed.
- Population vs privacy threshold: who is measured vs the minimum aggregation needed before a result is displayed.
- Saved prompt vs shared prompt vs scheduled prompt: personal reusable text vs audience-accessible prompt vs recurring execution.
- Prompt vs agent: reusable instruction vs maintained specialization with knowledge, owner, access, and optional actions.
Scenario examples
- Scenario: Admin-center active-user totals differ from the Copilot Dashboard. Think: Compare population, time window, privacy threshold, filter, and refresh delay before calling either wrong.
- Scenario: Leadership asks whether Copilot improved a business process. Think: Combine impact analytics and outcome measures; invocation count alone is insufficient.
- Scenario: A shared prompt references a finance file. Think: Recipients still need their own source permission; sharing the prompt grants none.
- Scenario: A scheduled prompt owner leaves. Think: Review ownership, access, schedule, and business need, then transfer/recreate or delete according to supported lifecycle.
Exam traps
- Usage does not equal productivity, impact, employee performance, or exam readiness.
- Two valid reports can differ because their definitions, populations, thresholds, and refresh windows differ.
- Sharing a prompt never grants source-data access.
- A schedule is not ownerless automation; ownership, permission, policy, and lifecycle continue to matter.
Key takeaways
- Admin reporting → operational use; Copilot Analytics → deeper adoption/agent/impact analysis.
- Reconcile reports by population, threshold, window, and refresh—not by forcing identical totals.
- Prompts have owners, audiences, source boundaries, schedules, and retirement needs.
How it works
- Usage telemetry is aggregated into operational reports and Copilot Analytics experiences. Roles, licenses, privacy settings, organizational data, filters, report windows, and processing delays determine what each viewer sees.
- Saving stores prompt text for reuse; sharing publishes or links it to an audience; scheduling adds recurring execution. At run time, the current owner/user permissions still determine accessible context.
- Prompt lifecycle follows create/save → validate → share or schedule for a justified audience → monitor/update → delete or retire when obsolete.
Objects and administrative surfaces
- Copilot readiness/adoption and usage reports — Microsoft 365 admin center Reports and Copilot areas.
- Microsoft Copilot Dashboard, Agent Dashboard, consumption and advanced reports — Viva Insights/Copilot Analytics experiences.
- Saved/shared prompts and prompt gallery — Microsoft 365 Copilot; scheduled-prompt availability — Microsoft 365 Apps cloud policy; organizational prompts — Microsoft 365 admin center where available.
When to use it
- Use admin-center reports for rollout operations and active-use questions; use Copilot Analytics for organization-level adoption, sentiment, agent, and impact questions.
- Save a tested prompt for personal reuse, share it when a maintained team pattern is useful, and schedule only justified recurring work.
- Delete or retire prompts that are obsolete, ownerless, duplicative, or contain inappropriate context.
Security and governance implications
- Use role-based dashboard access, privacy thresholds, exclusions, and minimum group sizes to protect employee privacy.
- Avoid secrets and unnecessary sensitive content in prompt text; review the data a schedule will access on each run.
- Define report purpose and measures before rollout so activity metrics are not misrepresented as performance surveillance or guaranteed return on investment.
Troubleshooting signals
- For report discrepancies, compare measured population, license assignment, activity definition, date window, time zone, filters, privacy threshold, and refresh delay.
- For a missing scheduled prompt, check license, optional connected experiences/cloud policy, owner, environment, source access, schedule, and service support.
- For an unavailable shared prompt, confirm share audience/link, owner state, prompt deletion, team membership where applicable, and source permission separately.
More detail
- The Microsoft 365 admin center provides Copilot readiness/adoption and usage reporting for administrators. It is suited to operational questions about assigned/eligible populations, active use, app or feature activity, and adoption over selectable reporting periods.
- Microsoft 365 Copilot Analytics includes the Microsoft Copilot Dashboard, Agent Dashboard, readiness/adoption reporting, consumption views, and advanced analysis depending on licensing and role. It supports organizational questions about adoption, sentiment, assisted work, agent activity, and business impact.
- Report populations differ. One report may use assigned licenses, another active users, an uploaded cohort, Entra organization attributes, or agent activity. Privacy thresholds can suppress small groups. Admin-center reports can offer rolling periods while dashboard data can use a prior-28-day view and a different delay.
- Usage means that people invoked Copilot or an agent. Adoption adds sustained and distributed use. Business impact asks whether outcomes such as time, quality, process, or key performance indicators improved. Analytics can support the question but cannot establish causation from activity count alone.
- A saved prompt is reusable text owned by a user. Sharing makes the prompt available to another person/team but does not share source files or grant data permission. Scheduling runs a prompt at configured times and depends on the owner, supported environment, current access, and administrator availability controls.
- Prompts can contain sensitive organizational context and should be treated as governed content. Owners should delete obsolete prompts, remove outdated shares/schedules, transfer or recreate important assets when ownership changes, and ensure organizational prompts have accountable maintenance.
Ready for the quiz?
- Why might two Copilot reports show different totals?
- How is usage different from adoption and business impact?
- What access does sharing a prompt grant?
- What should happen to scheduled prompts when their owner leaves?
Related objectives
- D3.2.c — Monitor Copilot usage and adoption, including Copilot Analytics and the Microsoft 365 admin center
- D3.2.d — Manage prompts, including saving, sharing, scheduling, and deleting