When you open Copilot Chat in Microsoft Teams, Edge, or the standalone copilot.microsoft.com site, you may see the error message “This account is not supported.” This message blocks you from sending any prompts or accessing Copilot features. The root cause is typically a licensing mismatch, a conditional access policy, or an account type that Microsoft does not allow for Copilot Chat. This article explains why the error occurs and provides step-by-step fixes for each scenario.
Key Takeaways: Fixing the Copilot Chat Account Not Supported Error
- Microsoft 365 admin center > Billing > Licenses: Verify that each user has an eligible Copilot license assigned.
- Azure AD > Conditional Access > Policies: Check if a policy blocks Copilot Chat from accessing Microsoft Graph or Bing resources.
- Account type check in Microsoft 365 admin center > Users > Active users: Ensure the account is a work or school account, not a personal Microsoft account.
Why Copilot Chat Blocks Your Account
The “This account is not supported” error appears when Copilot Chat cannot validate your account against the required licensing or authentication policies. Copilot Chat supports three account types: Microsoft Entra ID work accounts, school accounts, and personal Microsoft accounts with a Copilot Pro subscription. If your account does not match one of these types, or if the license is missing, Copilot Chat refuses the session.
There are three common triggers for this error:
Missing or Incorrect Copilot License
Copilot Chat requires one of the following licenses: Copilot for Microsoft 365, Copilot Pro, or a free Copilot account with a Microsoft Entra ID. If the license is not assigned or has expired, the service returns the unsupported account error. This is the most frequent cause for enterprise users.
Conditional Access Policies Blocking Authentication
Your organization may have a conditional access policy that restricts which apps or services a user can access. If the policy does not include Copilot Chat or blocks access to resources like Microsoft Graph or Bing, the authentication process fails and the error appears.
Unsupported Account Type
Copilot Chat does not support guest accounts, shared mailboxes, or accounts from unverified domains. If your account is a guest in the tenant or uses a domain that is not verified in Microsoft Entra ID, Copilot Chat treats it as unsupported.
Steps to Fix the Account Not Supported Error
Follow these methods in order. Each method resolves a different cause. Test Copilot Chat after each method before moving to the next.
Method 1: Verify and Assign the Correct License
- Open the Microsoft 365 admin center
Go to admin.microsoft.com and sign in with a Global Admin or Billing Admin account. - Navigate to Billing > Licenses
Select the subscription that includes Copilot. Look for “Copilot for Microsoft 365” or “Copilot Pro.” - Check the assigned users count
If the license pool shows zero available licenses, purchase additional seats from Billing > Purchase services. - Assign the license to the affected user
Go to Users > Active users, select the user, click the Licenses and apps tab, check the box for Copilot, and click Save changes. - Wait 15 minutes and test Copilot Chat
License assignment can take up to 15 minutes to propagate. Open Copilot Chat and send a test prompt.
Method 2: Review Conditional Access Policies
- Sign in to the Microsoft Entra admin center
Go to entra.microsoft.com and sign in with a Conditional Access Administrator or Global Admin account. - Go to Protection > Conditional Access > Policies
Review all enabled policies. Look for policies that target “All cloud apps” or specific apps like “Microsoft Graph” or “Bing.” - Check if the policy blocks Copilot Chat
If a policy blocks access to Microsoft Graph or Bing, Copilot Chat will fail. Edit the policy and add a user exclusion for the affected account, or add a grant control that allows access. - Add Copilot Chat as an excluded app
In the policy, under Cloud apps or actions, set the Include tab to “All cloud apps” and the Exclude tab to “Microsoft Copilot” or “Copilot Chat.” Save the policy. - Test Copilot Chat
Sign out of all Microsoft services, sign back in, and open Copilot Chat.
Method 3: Verify Account Type and Domain
- Open the Microsoft 365 admin center
Go to admin.microsoft.com and sign in with a Global Admin account. - Go to Users > Active users
Find the affected user and open their profile. - Check the account type
Under the Account tab, verify the User type is “Member” not “Guest.” If it is a guest account, Copilot Chat does not support it. Remove the guest account and invite the user as a member if necessary. - Check the domain status
Go to Settings > Domains. Confirm the user’s domain appears with a status of “Healthy.” If the domain is unverified, add a DNS TXT record to verify it. - Test Copilot Chat
After changing the account type or verifying the domain, wait 30 minutes and test Copilot Chat again.
If Copilot Chat Still Shows the Error After the Main Fix
Copilot Chat Works in One App but Not Another
If Copilot Chat works on copilot.microsoft.com but fails in Microsoft Teams, the issue is likely a per-app conditional access policy. Go to Microsoft Entra admin center > Protection > Conditional Access > Policies. Find the policy that targets the Teams app. Add a grant control that requires multi-factor authentication or a compliant device. Then test Copilot Chat inside Teams again.
Copilot Returns “This Account Is Not Supported” After a License Change
If you recently changed the user’s license from Copilot for Microsoft 365 to a different plan, the license removal takes effect immediately but the new license may take up to 30 minutes to provision. During this window, Copilot Chat may show the error. Wait 30 minutes, then sign out and sign back in to all Microsoft apps. If the error persists, go to Microsoft 365 admin center > Billing > Licenses and confirm the new license is active.
Copilot Chat Fails for All Users in the Tenant
If every user in your tenant receives the error, the problem is likely a tenant-wide conditional access policy or a service outage. Check the Microsoft 365 Service Health dashboard at admin.microsoft.com > Health > Service health. If no outage is reported, review your tenant’s conditional access policies for any policy that blocks “All cloud apps” for all users. Create a test user excluded from all policies and test Copilot Chat with that account.
Copilot Free vs Copilot for Microsoft 365 vs Copilot Pro: Account Support Comparison
| Item | Copilot Free | Copilot for Microsoft 365 | Copilot Pro |
|---|---|---|---|
| Supported account types | Personal Microsoft account, Microsoft Entra ID work or school account | Microsoft Entra ID work or school account only | Personal Microsoft account only |
| License required | None | Copilot for Microsoft 365 license assigned by admin | Copilot Pro subscription paid by user |
| Conditional access impact | Not affected by tenant policies | Affected by tenant conditional access policies | Not affected by tenant policies |
| Guest account support | Not supported | Not supported | Not supported |
| Shared mailbox support | Not supported | Not supported | Not supported |
The “This account is not supported” error in Copilot Chat is almost always caused by a licensing gap, a conditional access policy, or an unsupported account type. By following the three methods in this article, you can identify which factor is blocking your account and apply the correct fix. After resolving the issue, test Copilot Chat in both the web interface and the Teams app to confirm the fix is complete. As a best practice, audit your tenant’s conditional access policies quarterly to ensure new apps like Copilot Chat are not inadvertently blocked.