How to Track Copilot License Adoption by Department

Tracking Copilot license adoption by department helps you measure return on investment and identify teams that need more training. Without department-level reporting, administrators often rely on manual surveys or incomplete usage logs. Microsoft 365 provides built-in tools in the admin center and usage analytics to break down adoption by organizational unit. This article explains how to configure department mapping, generate adoption reports, and interpret the data for actionable decisions.

Why Department-Level Adoption Tracking Matters

Copilot licenses are typically purchased per user and assigned globally. Without department-level data, you cannot tell whether the Marketing team uses Copilot daily while Engineering has zero activations. This blind spot leads to wasted spend and missed training opportunities. Microsoft 365 usage reports aggregate data from Copilot interactions across Word, Excel, PowerPoint, Outlook, Teams, and the Copilot pane. When you sync the Department attribute from Entra ID, the reports automatically group these interactions by department. The result is a clear view of which departments have adopted Copilot and which have not yet activated their licenses.

Prerequisites for Department-Level Reporting

Before you can see department data in Copilot reports, three conditions must be met. First, each user must have the Department attribute filled in Entra ID. Second, the Microsoft 365 admin role must include at least Reports Reader permissions. Third, Copilot usage data must be flowing — users must have performed at least one Copilot action in the past 28 days. If any of these conditions are missing, the reports will show zero department data or display users under an empty department category.

Steps to Configure Department Mapping for Copilot Reports

Follow these steps to populate the Department attribute in Entra ID and verify that Copilot reports can group users by department.

1. Open Entra ID user management
   Go to the Microsoft Entra admin center at entra.microsoft.com. Select Users then All users. Click a user to open their profile.
2. Edit the Department attribute
   On the user profile page, select Edit under the Properties section. Scroll to the Job info section. In the Department field, enter the department name exactly as you want it to appear in reports. Click Save.
3. Bulk update Department for multiple users
   From the All users list, select multiple users by checking the boxes. Click Bulk operations then Bulk update. Download the CSV template, fill in the Department column for each user, upload the file, and confirm the changes. This method is faster for organizations with hundreds of users.
4. Sync Department from on-premises Active Directory
   If you use hybrid identity, the Department attribute syncs automatically from on-premises Active Directory via Microsoft Entra Connect. Verify that the Department attribute is mapped in the synchronization settings. In Entra Connect, go to Synchronization Service Manager then Metaverse Search to confirm the attribute value.
5. Verify department data in Entra ID
   After updating, wait 30 minutes for propagation. Export a list of users with the Department column to confirm the values are correct. Use the Microsoft Graph PowerShell command Get-MgUser -All | Select-Object DisplayName, Department to verify programmatically.

Generating Copilot Adoption Reports by Department

Once department data is populated, you can view adoption reports in the Microsoft 365 admin center and in the Power BI usage analytics template.

Method 1: Microsoft 365 Admin Center Reports

1. Navigate to the Copilot usage report
   Go to the Microsoft 365 admin center at admin.microsoft.com. Select Reports then Usage. Scroll down to the Copilot for Microsoft 365 section and click View report.
2. Filter by department
   In the report, click the Filter button at the top right. In the filter panel, select Department from the dropdown. Choose one or more departments to view. The chart and table update to show only users in the selected departments.
3. Export raw data
   Click the Export button to download a CSV file. The CSV includes columns for User, Department, Product, Last Activity Date, and Total Actions. Open this file in Excel to create pivot tables or charts for each department.

Method 2: Power BI Usage Analytics Template

1. Download the Microsoft 365 usage analytics template
   Go to the Microsoft 365 admin center > Reports > Usage. Click Get Power BI template. Download the PBIX file.
2. Connect to your tenant data
   Open the PBIX file in Power BI Desktop. When prompted, sign in with your Microsoft 365 admin account. The template automatically pulls Copilot usage data from your tenant.
3. Create a department adoption dashboard
   In Power BI, add a slicer for Department. Create a clustered column chart with Department on the axis and Active Users on the value axis. Add a second chart for Total Copilot Actions per Department. Save the report and publish it to the Power BI service for sharing with stakeholders.

Common Issues When Tracking Copilot Adoption by Department

Department column shows blank or N/A for all users

This occurs when the Department attribute is not populated in Entra ID. Run a bulk update to fill the Department field for all users. If you use hybrid identity, check the synchronization schedule in Entra Connect. The attribute may not sync if it is not mapped in the configuration.

Copilot usage report shows zero users for a department

The report only counts users who have performed at least one Copilot action in the past 28 days. If a department has assigned licenses but no activity, the report will show zero active users. This indicates that the department needs onboarding or training. Review the license assignment for that department and send activation instructions.

Department names are inconsistent across users

Variations like Sales, Sales Dept, and Sales Team create separate groups in the report. Standardize department names during the bulk update. Use a controlled list of department names and enforce it through HR data or a naming convention policy in Entra ID.

Power BI template does not show Copilot data

The Power BI template may not include Copilot data if you downloaded an older version. Ensure you download the latest template from the admin center. If the template still lacks Copilot fields, create a custom Power BI report using the Microsoft 365 Usage Reports dataset available in the Power BI service.

Admin Center Report vs Power BI Dashboard: Key Differences

Item	Admin Center Report	Power BI Dashboard
Data freshness	Up to 48-hour delay	Up to 24-hour delay with scheduled refresh
Department filtering	Built-in filter dropdown	Custom slicers and cross-filtering
Custom visualizations	Limited to chart and table	Full Power BI chart library
Sharing	Export CSV or share link	Publish to workspace or email subscription
Historical trend analysis	Last 28 days only	Up to 180 days with archive

You can now generate department-level Copilot adoption reports using the admin center or Power BI. Start by populating the Department attribute in Entra ID for all users. Next, review the Copilot usage report weekly to identify departments with low activity. For deeper analysis, set up a Power BI dashboard with department slicers and trend lines. An advanced step is to create a scheduled email subscription in Power BI that sends the department adoption report to each department manager every Monday morning.