Your Microsoft 365 Copilot Adoption Report shows fewer users than the number of active Copilot licenses you have purchased. This mismatch makes it difficult to track actual usage and adoption across your organization. The root cause is usually a gap between license assignment and the service’s data aggregation pipeline. This article explains why the report undercounts licensed users and provides four proven fixes to restore accurate reporting.
Key Takeaways: Restoring Accurate Copilot User Counts in Adoption Reports
- Microsoft 365 admin center > Billing > Licenses: Verify every Copilot license is assigned to a user with an active mailbox; unassigned licenses never appear in adoption data.
- Microsoft 365 admin center > Reports > Adoption > Copilot: The report refreshes every 24 to 48 hours; check the Last Updated timestamp before troubleshooting.
- PowerShell command Get-MgUserLicenseDetail: Use this cmdlet to confirm which users actually have the Copilot service plan enabled; a license assignment alone is insufficient.
Why the Copilot Adoption Report Shows Fewer Users Than Licensed
The Copilot Adoption Report in the Microsoft 365 admin center pulls data from the Microsoft Graph activity logs and the license service plan status for each user. The report counts only users who meet three conditions simultaneously: they have an active Copilot license assigned, the Copilot service plan is enabled on their account, and they have performed at least one Copilot action within the report’s date range. If any of these conditions is missing, the user is excluded from the report.
The most common technical root cause is a delay in the license-to-service-plan propagation. When you assign a Copilot license through the admin center, the system adds the license to the user’s subscription but does not always immediately enable the Copilot service plan. This delay can last from 15 minutes to 24 hours. During this gap, the user is licensed but not recognized by the adoption service.
Another frequent cause is the presence of guest users or shared mailboxes that have been assigned a Copilot license. The adoption report filters out non-user objects by default. Guest users with a Copilot license will not appear in the report unless they have a full Microsoft 365 work or school account and an active mailbox.
Steps to Fix the Missing Licensed Users in the Copilot Adoption Report
Use the following methods in order. Each method addresses a specific gap in the license-to-report pipeline.
Method 1: Verify License Assignment and Service Plan Status
- Open the Microsoft 365 admin center
Go to Billing > Licenses. Select the Copilot for Microsoft 365 product from the list. Review the Assigned column. If it shows fewer licenses than you purchased, assign the unassigned licenses to active users. - Check a sample user’s service plan
In the admin center, go to Users > Active users. Select a user who should appear in the report. Under the Licenses and apps tab, expand Copilot for Microsoft 365. Confirm that the toggle for Microsoft Copilot for Microsoft 365 is set to On. If it is Off, toggle it On and save. - Use PowerShell to bulk-check service plans
Open Windows PowerShell as an administrator. Run the following commands:Connect-MgGraph -Scopes "User.Read.All", "Organization.Read.All"Get-MgUser -All | ForEach-Object { $license = Get-MgUserLicenseDetail -UserId $_.Id; if ($license.SkuPartNumber -eq "COPILOT_M365") { Write-Output "$($_.UserPrincipalName) - Copilot license assigned" } }
This lists all users with a Copilot license. If a user is missing from the list, they lack a license assignment.
Method 2: Force a Report Refresh by Triggering a Usage Signal
- Perform a Copilot action from a missing user’s account
Have a user who is licensed but missing from the report open Copilot in Microsoft Teams, Word, or Outlook. Send a message to Copilot, such as “Summarize my last three emails.” This generates a usage signal that the adoption service can capture. - Wait 24 to 48 hours
Open the Copilot Adoption Report again. Check the Last Updated timestamp at the top of the report. If the timestamp is older than 48 hours, the data pipeline may be stalled. Contact Microsoft Support if the report does not update after 48 hours.
Method 3: Remove Duplicate or Conflicting License Assignments
- Identify users with multiple Copilot licenses
In the admin center, go to Users > Active users. Select a user who is missing from the report. Under Licenses and apps, check if the user has both Copilot for Microsoft 365 and Microsoft 365 Copilot assigned. This can cause a service plan conflict. - Remove the duplicate license
Uncheck the box for the duplicate license type. Save the changes. Wait 30 minutes and then check the adoption report.
Method 4: Verify the User Object Type and Mailbox Status
- Confirm the user is not a guest or shared mailbox
In the admin center, go to Users > Active users. Select the missing user. Under the Account tab, check User type. It must be Member for the user to appear in the adoption report. Guest users with a Copilot license are excluded. - Verify the user has an active Exchange Online mailbox
Go to Exchange admin center > Recipients > Mailboxes. Search for the user. Confirm the mailbox status is Active. If the mailbox is inactive or in a soft-deleted state, the user cannot generate Copilot usage data.
If the Adoption Report Still Shows Missing Users After the Main Fix
The report has not refreshed since the license assignment
The Copilot Adoption Report updates once every 24 hours based on the previous day’s activity. If you assigned a license today, the user will not appear until the next scheduled refresh. Wait until the following day and recheck the report. You can find the exact refresh schedule in the admin center under Reports > Adoption > Copilot > Refresh schedule.
Copilot service plan is disabled by a conditional access policy
Some organizations use conditional access policies to block specific service plans. Check your conditional access policies in the Azure AD admin center > Security > Conditional Access. If a policy targets the Copilot service plan, it may prevent the service from recording usage data. Create a policy exception for the affected users or remove the Copilot service plan block.
User has never opened Copilot after the license was assigned
The adoption report counts only users who have performed at least one Copilot action. A user with a valid license who has never used Copilot will not appear. Instruct the user to open Copilot in any Microsoft 365 app and send a prompt. After the next report refresh, the user should appear with zero activity if they have not used Copilot, but they will be counted as a licensed user.
Copilot Adoption Report vs License Usage Report: Key Differences
| Item | Copilot Adoption Report | License Usage Report |
|---|---|---|
| Data source | Microsoft Graph activity logs | Azure AD license assignment records |
| User count logic | Licensed + active service plan + at least one Copilot action | Any user with an assigned Copilot license regardless of activity |
| Refresh frequency | Every 24 hours | Near real-time within 15 minutes |
| Includes guest users | No | Yes, if a license is assigned |
| Best use case | Measuring adoption and active usage | Auditing license inventory and assignment |
The License Usage Report under Billing > Licenses shows every user with an assigned Copilot license. Use this report as a baseline to confirm that all purchased licenses are assigned. If the License Usage Report shows the correct count but the Adoption Report does not, the issue is in the service plan status or activity signal, not in the license assignment.
You can now verify license assignments, force a usage signal, and check service plan status to fix the missing user count in the Copilot Adoption Report. Start by running the PowerShell script from Method 1 to identify users with a license but no service plan. Next, have those users perform a Copilot action to generate a usage signal. If the problem persists after 48 hours, check for duplicate licenses or conditional access policies blocking the Copilot service plan. For ongoing monitoring, set a weekly reminder to review the License Usage Report alongside the Adoption Report to catch assignment gaps early.