4.1 Monitoring Adoption & Usage

Microsoft 365 isn't just a set of licenses you hand out — it's a platform you want people to actually use. The MS-102 exam expects you to know the two built-in telemetry surfaces a Microsoft 365 Administrator Expert uses to measure that usage: the Usage reports in the Microsoft 365 admin center and the Microsoft 365 Adoption Score (formerly Productivity Score). Together they answer "who is doing what, in which workload, and is our technology stack healthy enough to support them?"

The Microsoft 365 admin center Usage reports

Open the Microsoft 365 admin center and go to Reports → Usage. The Usage dashboard gives you tenant-level activity for the core workloads:

Each report lets you filter by the last 7, 30, 90, or 180 days, and each report has an Export option that downloads the underlying user-level rows as a CSV so you can build your own views in Excel or Power BI. The reports identify workloads that have been licensed but are underutilized — for example, 5,000 Teams licenses but only 800 active users in the last 30 days is a clear training opportunity.

Role requirements for usage reports

Not every admin should see every report. Microsoft 365 enforces least privilege:

• Global Administrator — full access to all reports.
• Global Reader — can read all reports but cannot change configuration.
• Reports Reader — the dedicated role for delegated report consumers; can view the Usage dashboard and Adoption Score but cannot modify tenant settings.
• Exchange / SharePoint / Teams communications / Teams service admin — each sees the reports scoped to their workload.

For MS-102, remember that Reports Reader is the right role when you want to grant a stakeholder (a department head, an adoption team member) report visibility without granting broader admin rights.

Microsoft 365 Adoption Score

The Microsoft 365 Adoption Score (in the admin center under Reports → Adoption Score) is the successor to what Microsoft previously called Productivity Score. It provides insight into how the tenant is using Microsoft 365 and the health of the underlying technology experiences. It is split into two categories:

People experiences

People experiences measure how people work in five sub-categories:

1. Content collaboration — coauthoring in SharePoint and OneDrive.
2. Mobility — working across platforms and devices.
3. Meetings — Teams meeting habits, video on, follow-up.
4. Teamwork — Teams channels, shared workspace engagement.
5. Communication — email, chat, community posts.

The five categories roll up into a single tenant-level Adoption Score presented alongside a benchmark against organizations of a similar size. Treat the individual category contributions as relative signals — Microsoft tunes the scoring model over time, so do not memorise a per-category point value.

Technology experiences

Technology experiences measure the infrastructure that supports the work:

• Endpoint analytics — device boot times, crash rates, managed device health (shared with Intune).
• Network connectivity — the Microsoft 365 network connectivity score.
• Microsoft 365 Apps health — how current the Office client is, add-in reliability.

How the score is computed and privacy

The Adoption Score is computed from aggregated, tenant-wide telemetry Microsoft already collects as the service provider. Microsoft publishes the following privacy commitments, and the exam has historically tested them:

• No per-user tracking — the score is built from aggregated signals, not individual user activity.
• No individual identification — you cannot drill from a score back to a named user.
• Minimum reporting group size — categories are not displayed when the population is too small to anonymize.
• Role-based visibility — admins can hide Adoption Score from users who should not see it.
• Opt out — the tenant can opt out of contributing telemetry to the external benchmark, and can opt out of viewing Adoption Score entirely.

For the exam, the critical distinction is: Usage reports give you user-level rows (exportable CSV) for operational investigation; Adoption Score gives you a tenant-wide, privacy-protected score for executive reporting and adoption planning. They are complementary, not redundant.

Driving adoption from the data

The reports exist to drive action. A typical adoption workflow:

1. Identify an underused workload from the Usage dashboard (low active-user ratio against licensed count).
2. Cross-reference the Adoption Score to see whether the gap is a people problem (low collaboration score) or a technology problem (poor network connectivity, stale Office clients).
3. Target training using the Microsoft 365 Adoption content — Microsoft publishes success kits, onboarding templates, and the Microsoft 365 Champions program for exactly this scenario.
4. Use Microsoft Viva Insights (the former Workplace Analytics lineage) to surface organizational-level work patterns and measure whether the intervention moved the needle.

An admin who only reads the reports and never closes the loop with training is doing half the job. The MS-102 blueprint pairs "monitor adoption" with the implied next step of acting on what you monitored.

---

Exam tip: If a question asks which role is the minimum required to view usage reports without granting tenant administration, the answer is Reports Reader. If it asks which tool shows a 0-100 tenant-wide score built from aggregated telemetry with per-user privacy protections, that is Adoption Score, not the Usage reports.