Exercise - Interpret Relecloud's Copilot adoption data

  • 10 minutes

Relecloud's leadership wants evidence the Copilot rollout is actually landing, not a guess. You've just learned how usage reports and Adoption Score complement each other—now read both for Relecloud's tenant and turn what you find into a recommendation leadership can act on.

Important

Prerequisites for this exercise:

  • A Microsoft 365 tenant with Reports Reader, AI Report Reader, Global Reader, or Global Administrator access.
  • At least one test user licensed for Microsoft 365 Copilot in the last 30 days, so the AI Adoption category actually appears on the Adoption Score report.
  • The tenant's usage reports and Adoption Score enabled (both are on by default; a Global Administrator may need to re-enable if a privacy setting turned them off).

Reports and Adoption Score data can lag by up to 72 hours, so use whatever the most recent complete reporting period shows—don't wait for "today's" numbers.

Task 1: Review the usage report for a Microsoft 365 service

  1. Sign in to the Microsoft 365 admin center at admin.microsoft.com with your Reports Reader account.
  2. In the left navigation, select Reports > Usage.
  3. Open the Microsoft 365 Apps activity report. Review the last 30 days.
  4. Note two numbers: total active users (users who used at least one app) and per-app active users (Word, Excel, Teams, OneDrive, and so on).
  5. Reflect: this tells you whether Relecloud's workforce is actually opening the apps Copilot rides on. If Word active users are low, no Copilot in Word rollout will move the needle—the base engagement isn't there yet.

Task 2: Interpret the Adoption Score, focusing on AI Adoption

  1. In the same Reports navigation, select Adoption Score.
  2. Review the overall score and the category scores. Note the score, the primary experiences breakdown, and any category the tenant is significantly below the peer benchmark on.
  3. Open the AI Adoption category. Note the AI Adoption score and the breakdown of Copilot-licensed users, active Copilot users, and per-experience usage (Copilot in Word, Excel, Teams, and so on).
  4. Reflect: usage reports told you how much the workforce is using each app. Adoption Score's AI Adoption tells you how much of that Copilot-licensed workforce is actually engaging Copilot, and where. A high license count paired with low active-Copilot users is the classic "we bought it but nobody's using it" signal.
  1. Back on the Adoption Score overview, find the lowest category (whether AI Adoption or one of the primary-experience categories) and open its Recommended actions panel.
  2. Pick one recommended action that fits Relecloud's Copilot rollout goal. For example, if AI Adoption shows high licensing but low Copilot in Teams engagement, the recommended action might be to publish a short internal how-to on saving Teams meeting transcripts—the exact prerequisite for Copilot recaps you configured back in Unit 7 of the Exchange and Teams module.
  3. Write down the recommended action and one sentence framing it for leadership: what's low, what to do, and what you'll measure to confirm it worked (the same category score, 60 days from now).

You've now read the usage report, interpreted Adoption Score's AI Adoption category, and turned the data into a specific recommendation—the same one-page brief leadership actually needs to see.