4.2.2. Usage Monitoring and Adoption

💡 First Principle: Copilot adoption monitoring tells you whether licensed users are actually using Copilot, how often, and in which apps. Without this data, you're paying for licenses that may be sitting unused — and you can't drive adoption if you can't measure it.

Copilot Analytics (in the Microsoft 365 admin center → Copilot → Analytics):

• Shows active user counts per app (Copilot in Teams, Copilot in Word, etc.)
• Trend lines showing week-over-week or month-over-month usage
• Per-app engagement metrics (number of Copilot interactions per user)
• Adoption Score integration — Copilot usage contributes to the Microsoft 365 Adoption Score

What to look for in Copilot Analytics:

• Low active user % despite high license count → adoption gap; investigate with change management
• High usage in one app, low in others → targeted training opportunity
• Declining usage trend → user experience or value perception issue

Copilot Dashboard in Viva Insights (available with qualifying licenses):

• More detailed analytics: estimated time saved per user, satisfaction survey data
• Qualitative signals: do users report Copilot as helpful?

💡 Key Point: Usage data in Copilot Analytics is anonymized and aggregated by default to protect user privacy. Individual user-level data may require additional privacy configuration and admin permissions to access.

⚠️ Exam Trap: Copilot Analytics shows usage of licensed Copilot features — it doesn't track every AI interaction. If a user accesses a Copilot agent through a Teams channel, that activity may be tracked separately in the Power Platform admin center, not in Copilot Analytics.

Reflection Question: 30 days after deploying Copilot to 200 users, Copilot Analytics shows only 40 active users. The other 160 have the license but haven't opened Copilot. What are two actions an admin can take, and what does the data suggest about the root cause?