3.2 Usage Monitoring and Analytics

Quick Answer: Monitor Copilot adoption with Copilot Analytics and the Copilot Usage Report in the Microsoft 365 admin center. Leaders also use the Microsoft Copilot Dashboard in Viva Insights for sentiment data. Do not confuse these with Adoption Score (all M365 workloads) or Service Health (availability, not usage).

Why Usage Monitoring Is an Admin Responsibility

Deploying Copilot without measuring adoption is a governance failure. AB-900 tests whether administrators know which reports answer which questions — active users vs service uptime vs employee sentiment vs license cost. Microsoft deliberately names tools similarly; picking the wrong dashboard is a scored mistake.

Copilot Usage Report (Microsoft 365 Admin Center)

The Copilot Usage Report lives in the Microsoft 365 admin center under Reports. It provides aggregated, tenant-level data:

• Active users — how many licensed users actually used Copilot in the reporting period
• Feature-level usage — chat, email drafting, meeting summaries, document generation
• Adoption trends — week-over-week or month-over-month movement

This report answers: "Are people using what we paid for?" It does not capture individual prompt text (that requires Purview Audit) and does not show DLP violations (that is Purview Communication Compliance or AI Hub).

Copilot Analytics

Copilot Analytics extends usage visibility with deeper adoption analytics designed for administrators evaluating return on investment (ROI) and planning change management. Combined with admin center reports, it is the primary answer when an exam stem asks how to monitor Copilot usage and adoption across the organization.

Administrators use Copilot Analytics to:

1. Identify departments with low activation rates
2. Compare feature usage (Teams meeting summaries vs Word drafting)
3. Justify license expansion or reallocation to leadership
4. Trigger targeted training for under-adopting groups

Microsoft Copilot Dashboard (Viva Insights)

The Microsoft Copilot Dashboard in Viva Insights targets organizational leaders rather than day-to-day admins. It surfaces:

• Adoption metrics at a leadership-friendly granularity
• Feature usage trends across the licensed population
• Aggregated employee sentiment about how helpful Copilot is in daily work

This is an adoption and sentiment tool. It is not a DLP alert source, not a forensic prompt log (Purview Audit), and not a license cost breakdown (Billing section).

Reports You Should NOT Confuse

On the Exam: "Which report shows aggregated Copilot feature usage such as active users and which apps are being used?" → Copilot Usage Report. "Which tool gives leaders employee sentiment about Copilot helpfulness?" → Microsoft Copilot Dashboard in Viva Insights.

Monitoring Agent Usage

Custom Copilot Studio agents add a second monitoring surface. Agent usage and operational insights are tracked through both the Microsoft 365 admin center (agent management, approvals, org-wide agent catalog) and the Power Platform admin center (environment-level governance, maker activity, Dataverse storage). AB-900 frequently pairs these two consoles in multi-select or "best two tools" questions.

Preparing Users for Adoption

Administrative preparation is not only licensing. The complete rollout loop:

1. Assign Copilot licenses to the intended audience (directly or via group)
2. Configure org settings — web grounding, feature toggles, plugin policies
3. Communicate approved use cases and link to prompt libraries
4. Monitor adoption through Copilot Analytics and usage reports
5. Remediate gaps — training, permission cleanup, or license reallocation

Skipping step 4 is how organizations discover six months later that 80% of seats are unused.

Worked Scenario: Low Adoption Investigation

Copilot Usage Report shows 200 licensed users but only 40 active in the last 28 days. An administrator should:

• Check whether inactive users still need licenses (reclaim seats)
• Review feature-level breakdown — are users stuck on chat but not using Teams summaries?
• Cross-reference Copilot Dashboard sentiment — is helpfulness low in specific departments?
• Verify permissions and oversharing cleanup did not block expected value
• Launch targeted enablement rather than blaming the tool

Org Settings That Affect Perceived Usage

Admins influence adoption through Settings > Org settings > Microsoft 365 Copilot:

• Web grounding toggle — when disabled, Copilot cannot enrich responses with Bing/public web data (common in regulated industries)
• Feature availability toggles — enable or disable specific Copilot experiences org-wide
• Integrated apps — control third-party plugins and connectors that extend Copilot

These settings do not appear in usage reports directly, but misconfiguration often shows up as low adoption or support tickets.

Common Exam Traps

Message Center and Service Health for Copilot Admins

Copilot administrators should monitor the Message Center for planned Copilot feature changes, policy updates, and deprecation notices that affect governance settings. Service Health confirms whether low usage stems from an outage rather than poor adoption — a distinction that matters when leadership asks why meeting summaries stopped appearing. Neither tool replaces Copilot Analytics for measuring active users, but both belong in a complete admin monitoring routine alongside usage reports.