After rolling out Copilot, it is natural to ask whether employees are using it. Microsoft 365 Copilot adoption metrics can help answer that question, but they need context. Activity counts tell you what is being used, not whether the work is better or employees are getting value.
A useful review connects report patterns with the tasks employees do, checks for access or awareness issues, and offers support where it can help. Treat the data as a guide to adoption, not a scorecard for individual performance.
Where to find the Microsoft Copilot usage report
In the Microsoft 365 admin center, go to Reports, open Usage, and select the Microsoft 365 Copilot usage report. Microsoft’s Copilot usage report documentation explains the available metrics and report views.
The report provides viewing periods of 7-, 28-, 90-, and 180-days, as described in Microsoft’s report guidance. Choose a period that fits the question you are investigating. A shorter view can help you check recent rollout activity; a longer view can show whether usage is becoming part of regular work.
Start with the overall picture, then look for differences by app and over time. Avoid drawing conclusions from a single snapshot, especially when employees have only recently received access or training.
Which adoption metrics matter?
Enabled users and active users
Compare the number of people enabled for Copilot with the number recorded as active during the selected period. The enabled count describes the group that can use the service. The active count indicates that users in that group had qualifying Copilot activity in the period.
An active-user count is a useful sign of reach, but it does not mean that someone uses Copilot frequently, uses it well, or has improved their work. It is an activity measure, so pair it with conversations about real tasks and barriers.
Usage by app
Look at the report’s app-level activity to see where Copilot is being used, such as in Word, Excel, Outlook, or Teams. Patterns can help you identify where employees are finding a fit and where they may need a clearer example or additional guidance.
For instance, if a team uses Copilot in Outlook but rarely in Word, ask whether document-related work is a regular part of the team’s workflow and whether employees know how to get started. Low use does not automatically mean a training problem. It may reflect the work people do, access issues, or a workflow that is not a good fit.
Prompts and activity over time
Prompt counts and activity trends can help indicate how often Copilot is being used. Compare those patterns with the active-user count: a group may have a broad reach but relatively occasional use, while another may have fewer active users who return to Copilot more regularly.
Do not treat prompt volume as a measure of quality. A high count cannot tell you whether a response was accurate, whether an employee had to redo the work, or whether a business process improved.
Turn report patterns into useful support
Use the metrics to form questions, then check those questions with employees and managers. The goal is to find a practical next step, not to assume the report explains why a pattern exists.
- Low activity across a group: Check whether employees know Copilot is available, can access it, and understand which work tasks it can support.
- Low use in a particular app: Offer examples tied to that app and the group’s actual workflows. A short, relevant demonstration may be more useful than general guidance.
- Uneven use between teams: Ask what tasks, processes, or support differ. Share effective, approved use cases where they are relevant to other teams.
- Activity drops after rollout: Check whether employees encountered friction, lost access, or did not find a useful fit for their work. Follow up before assuming interest has faded.
Build a follow-up into the rollout. Review the pattern, select a focused support action, and check the report again after employees have had a chance to use that support. Your AI adoption roadmap can help connect this review to broader rollout goals.
Respect privacy and understand the limits
Microsoft says user identities are hidden by default in usage reports. Keep the review proportionate: use group and app patterns to guide awareness, training, and access checks rather than to rank employees. If your organization needs to review identifiable information, make sure the approach is clear to employees and consistent with internal policies.
Also distinguish Microsoft 365 Copilot activity from Copilot Chat activity. They are not necessarily interchangeable measures. Check the report’s definitions so you know what activity is included before comparing results across tools or periods. Microsoft’s measurement and reporting guidance provides additional context.
Reports are not always immediate. Microsoft says Copilot activity for a given day typically appears in the usage report within 48 hours of that day ending in UTC, according to its usage report documentation. A blank or delayed last-activity date may therefore need a later check before you conclude that a user has not engaged.
For sensitive work, usage reporting should sit alongside responsible access and data practices. A review of SharePoint permissions before using Copilot can help organizations consider whether people have appropriate access to the information they work with.
Frequently asked questions
How can I see who is using Microsoft 365 Copilot?
Open the Copilot usage report in the Microsoft 365 admin center and review its user and activity views. User identities are hidden by default, so the report may show aggregated information rather than names.
What does Microsoft count as an active Copilot user?
The report counts users with qualifying Copilot activity during the selected period. Active status shows recorded activity, not how often someone uses Copilot or whether the results were useful.
Can I see Copilot usage by app?
The report includes app-level activity, which can help you see where employees are using Copilot. Use the patterns to identify where a workflow-specific example or support may be helpful.
Does the report show whether employees are getting good results?
No. Usage and prompt activity do not measure accuracy, work quality, productivity gains, or business value. Use the report to guide follow-up conversations and assess outcomes separately.
Use metrics to guide the next step
Microsoft 365 Copilot usage reports are most useful when you compare enabled and active users, inspect app-level patterns, and follow up on gaps without treating activity as a measure of performance. AI Services Near Me serves businesses throughout Florida and Georgia and offers a free AI consultation. If you want help reviewing rollout adoption and identifying practical support needs, that is a straightforward next step.