You open Microsoft 365 Copilot in Word, Excel, or Teams, and instead of generating a draft or answering a question, you see the message: Contact your admin. This means Copilot cannot verify your license or permissions. The error appears when your Microsoft 365 tenant does not have the required Copilot add-on subscription assigned to your user account, or when your admin has not enabled the service in the Microsoft 365 admin center. This article explains the exact causes of this error and provides step-by-step fixes you can apply yourself or ask your admin to run.
Key Takeaways: Fixing the Contact Your Admin Error in Copilot
- Microsoft 365 admin center > Billing > Licenses: Verify that the Copilot for Microsoft 365 add-on license is assigned to your specific user account.
- Microsoft 365 admin center > Settings > Org settings > Copilot: Enable the service for your tenant and confirm data access policies are not blocking Copilot.
- Ctrl+Alt+Delete > Sign out and sign back in: Force a license token refresh after a new Copilot license is assigned.
Why Copilot Displays the Contact Your Admin Message
The Contact your admin error in Copilot is a licensing and permissions gate. Copilot for Microsoft 365 is not included in standard Microsoft 365 E3, E5, or Business Premium subscriptions. It requires a separate add-on license that costs $30 per user per month at the time of writing. When your user account does not have this add-on license assigned, or when the Copilot service itself is disabled at the tenant level, the application blocks all functionality and returns the admin contact message.
Missing or Incorrect License Assignment
The most common root cause is that your IT admin purchased Copilot licenses but did not assign one to your user object in the Microsoft 365 admin center. Without this assignment, the Copilot application cannot validate your entitlement. The error appears immediately when you try to use any Copilot feature in Microsoft 365 apps.
Service Disabled at the Tenant Level
Even with a valid license, your admin may have disabled the Copilot service globally under Org settings. This blocks all users from accessing Copilot, regardless of their license assignment. The service toggle is a tenant-wide switch that overrides individual license assignments.
Data Access Policies Blocking Copilot
In some organizations, conditional access policies or data governance rules prevent Copilot from reading Microsoft Graph data. If Copilot cannot access the data it needs to generate responses, it may fall back to the Contact your admin error instead of returning a generic failure message. This is less common but occurs in tenants with strict compliance settings.
Steps to Resolve the Contact Your Admin Error
The following steps address all three root causes. You will need admin privileges in the Microsoft 365 admin center to complete steps 1 and 2. If you are a standard user, forward these instructions to your IT administrator.
Step 1: Verify and Assign the Copilot License
- Open the Microsoft 365 admin center
Sign in to admin.microsoft.com with an account that has Global Admin or Billing Admin role. - Go to Billing > Licenses
Select the Copilot for Microsoft 365 product from the list. If you do not see it, your tenant has not purchased Copilot licenses yet. Purchase at least one license from the Purchase services page. - Assign the license to the affected user
Click the user name in the Assigned users list, or click Assign licenses and search for the user. Check the box for Copilot for Microsoft 365 and click Assign. The license takes effect within 15 minutes. - Force a token refresh on the client machine
On the user’s device, press Ctrl+Alt+Delete, select Sign out, wait 30 seconds, and sign back in. This forces Microsoft 365 to issue a new authentication token that includes the Copilot license claim.
Step 2: Enable the Copilot Service in Org Settings
- Navigate to Settings > Org settings
In the Microsoft 365 admin center, go to Settings and select Org settings. - Find the Copilot service entry
Scroll to the Copilot section or use the search box. Click on Copilot to open its settings panel. - Turn on the service toggle
Set the toggle to On for the entire organization. If your tenant requires granular control, select Specific users or groups and add the affected user’s security group. Click Save. - Verify data access permissions
In the same settings panel, confirm that Allow Copilot to access Microsoft Graph data is enabled. Disabling this blocks Copilot from reading emails, files, and calendar events.
Step 3: Check Conditional Access and Data Policies
- Open Microsoft Entra admin center
Go to entra.microsoft.com and sign in with a Global Admin account. - Review Conditional Access policies
Navigate to Protection > Conditional Access > Policies. Look for any policy that targets the Microsoft 365 Copilot cloud app. If a policy blocks access, create an exclusion for the affected user or adjust the policy to allow Copilot. - Check Data Loss Prevention rules
In the Microsoft Purview compliance portal, go to Data Loss Prevention > Policies. If a DLP rule blocks Copilot from processing sensitive content, either remove the rule or add an exception for Copilot interactions. - Test Copilot again
Open any Microsoft 365 app such as Word or Teams. Click the Copilot icon and type a simple prompt such as Summarize the last email. If the error persists, restart the app completely.
If Copilot Still Shows Contact Your Admin After the Main Fix
Sometimes the error remains even after license assignment and service enablement. The following sections cover additional failure patterns and their fixes.
Copilot Works in One App but Not Another
This indicates a per-app licensing issue. Microsoft 365 Copilot is licensed per user across all apps, but some apps require a minimum version. Ensure the affected app is updated to version 2402 or later for Windows. In the app, go to File > Account > Update Options > Update Now. After the update, sign out and sign back in.
Copilot Error Appears in Microsoft Teams Only
Teams uses a separate authentication pipeline. Clear the Teams cache by closing the app, deleting the folder %appdata%\Microsoft\Teams, and restarting Teams. If the error persists, the admin must enable Copilot in the Teams admin center under Meetings > Meeting policies > Copilot.
Copilot Error Appears on Mobile Devices
The mobile version of Copilot relies on the same license as the desktop version. If the desktop version works but the mobile version shows Contact your admin, uninstall the Microsoft 365 mobile app, restart the device, and reinstall it from the official app store. Sign in with the same licensed account.
Copilot for Microsoft 365 vs Copilot Pro: Licensing Comparison
| Item | Copilot for Microsoft 365 | Copilot Pro |
|---|---|---|
| Target user | Enterprise and business users with a Microsoft 365 subscription | Individual consumers and power users |
| Required base plan | Microsoft 365 E3, E5, Business Basic, Business Standard, or Business Premium | No base plan required, but limited features without a Microsoft 365 subscription |
| Integration with Microsoft 365 apps | Full integration in Word, Excel, PowerPoint, Outlook, Teams, and Loop | Limited to Word, Excel, and PowerPoint on the web and desktop |
| Admin management | Managed in Microsoft 365 admin center with tenant-wide controls | Self-managed by the user with no tenant-level controls |
| Data access | Reads Microsoft Graph data including emails, files, and calendar items | Does not read Microsoft Graph data |
| Price per month | $30 per user | $20 per user |
If your organization uses Copilot for Microsoft 365, the admin must assign the correct license type. Copilot Pro licenses will not resolve the Contact your admin error because the enterprise version requires the $30 add-on.
You can now identify why Copilot displays the Contact your admin message and apply the correct fix. Start by verifying the license assignment in the Microsoft 365 admin center under Billing > Licenses. If the license is present but the error persists, enable the Copilot service toggle under Settings > Org settings. For persistent issues, check conditional access policies in the Microsoft Entra admin center. A final tip: after any license or policy change, always sign out and sign back in to force a token refresh. This single step resolves the error in most cases where the configuration is correct but the token is stale.