Your Copilot is blocked because the request never carried a valid license entitlement, or because a network control between your device and Microsoft's endpoints rejected it. Microsoft 365 Copilot access depends on an assigned Copilot license in your tenant, and that license is checked on every request. When the check fails, the client shows a generic block rather than the real cause. The message is a symptom, not a diagnosis. This guide maps the mechanisms behind it, from Entra ID token claims to TLS inspection, and gives you a triage order that resolves most cases in minutes.

The two gates that produce a block

Copilot is not a single program. It is a layer that sits on top of Microsoft Graph, the search index, and the large language model orchestration service. A request has to clear two independent gates before any text is generated.

The first gate is identity and entitlement. When you sign in, Microsoft Entra ID issues an access token that encodes your tenant, your user object, and your assigned service plans. The Copilot service reads the service plan identifiers in that token. If the plan is absent, expired, or scoped to a different tenant, the service returns an authorization failure. The client renders that failure as an unhelpful "blocked" or "unavailable" state.

The second gate is network reachability. Even a fully licensed user can be blocked if the endpoint that serves Copilot cannot be reached. Copilot traffic goes to Microsoft 365 and Graph endpoints, not to the legacy webmail host. A firewall that allows the old host but blocks the newer service endpoints will pass email and fail Copilot.

Both gates must open. Fixing one and ignoring the other is why so many troubleshooting attempts stall.

Anatomy of the entitlement check

The entitlement check happens server-side, which is the counterintuitive part. Users often assume the desktop or web client decides whether they have Copilot. It does not. The client is a thin shell that requests a token and forwards it to the service.

The token contains a claims collection. Among those claims are assigned plans, each with a service plan identifier. Microsoft publishes these identifiers in its licensing documentation, and administrators can read them with a Graph query on the user's license details. The Copilot service compares the plan set against the feature it is about to serve. A missing plan produces a 403-class response at the service, which the client cannot distinguish from a network error.

There is a subtlety in how plans propagate. License assignment writes to the directory, and token issuance reads from the directory. The write and the read are asynchronous. A newly assigned license can take from minutes to a couple of hours to appear in a fresh token, because tokens are cached and refreshed on a schedule. Forcing a token refresh, by signing out and back in, shortens the wait. Clearing the client cache does not, because the cache is not the bottleneck.

A second subtlety is group-based licensing. If Copilot is assigned through a security group, the user must be a direct or transitive member. Nested groups work only when the tenant has enabled transitive membership evaluation for licensing. A user who appears to be in the right group can still lack the plan if nesting is not evaluated.

A third subtlety is the difference between having a Copilot license and having the underlying base license. Copilot is an add-on. It requires an eligible base subscription, and the add-on alone does not satisfy the prerequisite. An administrator who assigns only the add-on will see the user listed as licensed while the service still refuses to serve Copilot.

Quantified context: timing, thresholds, and blast radius

License propagation is usually measured in minutes, not seconds. Directory replication is fast within a region, but token refresh cadence is the limiter. Access tokens for Microsoft 365 typically live about an hour, and refresh tokens are used to mint new access tokens. A user who was just licensed may therefore wait up to roughly one token lifetime before the new claim appears, unless a refresh is forced.

Service-side throttling is a separate mechanism that can look like a block. When a tenant or user exceeds rate limits, the service returns throttling responses that clients sometimes render as "blocked." Throttling is transient and self-clearing, usually within seconds to minutes. A block that persists for hours is not throttling.

Conditional Access policy evaluation adds another timing layer. Policy changes can take effect within minutes but are evaluated at token issuance. A user who fails a newly applied policy will be blocked until they satisfy the policy, for example by completing multifactor authentication or moving to a compliant device.

The blast radius matters for diagnosis. If one user is blocked and colleagues are fine, the problem is almost always entitlement or device state. If an entire department is blocked, a group assignment or policy scoping is the likely cause. If an entire tenant is blocked across all clients, suspect a tenant-level policy, a licensing change, or a service incident.

Timeline of a typical block and recovery

Stage What happens Typical duration What you observe
License assigned Directory write completes Seconds Admin center shows the license
Token refresh New access token minted with plan claim Up to ~1 hour Old session still blocked
Client re-auth User signs out and back in 1–2 minutes Claim appears immediately
Network path check Firewall and proxy evaluate endpoints Immediate Failure logs at the gateway
Policy evaluation Conditional Access assessed Minutes Sign-in error or block page
Service propagation Feature flag and cache warm Minutes to hours Intermittent availability
Incident resolution Microsoft service restores Hours to days Tenant-wide impact clears

Read the table as a diagnostic ladder. Match your observed duration to the stage. A block that clears after a sign-out points to token caching. A block that survives a sign-out but clears after a firewall change points to the network gate.

Edge cases that mimic a block

Several conditions produce the same user-facing message without being a true block.

A browser extension that intercepts requests can inject headers or strip cookies. The service then rejects the request. Testing in a private window with extensions disabled isolates this cause in under a minute.

A stale client build can call a deprecated endpoint. The service retires old endpoints on a published schedule, and retired endpoints return errors the client maps to "blocked." Updating the client resolves it.

A proxy that performs TLS inspection can break certificate pinning or present a certificate the client does not trust. The request fails before it reaches Microsoft. Gateway logs show the interception.

A user signed into the wrong tenant, for example a personal account instead of the work account, will be blocked because the personal tenant carries no Copilot plan. The sign-in prompt often defaults to the last used identity, which may be personal.

A device that fails a compliance check is blocked by Conditional Access, not by Copilot itself. The fix is device remediation, not licensing.

Misconceptions worth retiring

The most common misconception is that clearing the browser cache fixes a block. Cache clears help with stale page assets, but entitlement and network failures live outside the browser cache. Clearing it wastes time and creates the illusion of progress.

A second misconception is that a Copilot license alone is sufficient. The add-on requires an eligible base subscription, and the base subscription must be active. A lapsed base license blocks Copilot even when the add-on is present.

A third misconception is that the block is a Microsoft outage. Outages happen, but they are tenant-wide and usually reported on the service health dashboard. A single-user block is almost never an outage.

A fourth misconception is that a firewall rule for the legacy webmail host covers Copilot. Copilot uses a broader set of endpoints, and Microsoft publishes the required endpoint list. Allowing only the legacy host leaves Copilot unreachable.

The professional caveat: clients are deliberately vague about authorization failures. Microsoft does not want to leak tenant configuration details to unauthorized users, so the client collapses many distinct server responses into one message. Treat the message as an index into a set of causes, not as a description of any single one.

Practical actions in order

Work the ladder from cheapest to most expensive. Most blocks resolve in the first three steps.

Confirm the account. Verify you are signed into the work tenant, not a personal account. Check the account tile in the client. Force a token refresh. Sign out completely, close all client windows, and sign back in. This refreshes the entitlement claim. Check license assignment. Have an administrator confirm both the Copilot add-on and the eligible base subscription on your account. Check group membership. If licensing is group-based, confirm you are a member and that nesting is evaluated. Test the network path. Try a different network, disable the proxy, and test in a private window. Gateway logs will show blocked endpoints. Review Conditional Access. Confirm your device meets compliance and your sign-in satisfies policy. Check service health. Confirm no tenant-wide incident is active.

Red-flag warnings: do not disable security controls tenant-wide to test Copilot; do not assign licenses to shared accounts; do not bypass Conditional Access with exclusion groups as a permanent fix; and do not treat a persistent tenant-wide block as a client bug.

Comparison of block signatures

Signature Likely gate Diagnostic clue Resolution path
One user blocked, others fine Entitlement License panel shows missing plan Assign plan, refresh token
Whole group blocked Group licensing Group membership or nesting error Fix group evaluation
Block persists after sign-out Base license or policy Base subscription lapsed Renew base license
Block on one network only Network Gateway logs show dropped endpoints Update firewall allowlist
Block after browser change Client or extension Private window works Disable extension, update client
Block on personal account Tenant identity Account tile shows personal Sign into work tenant

Limitations and what this cannot tell you

This guide describes stable mechanisms. It does not cover every tenant configuration, because licensing and Conditional Access are highly variable across organizations. The exact endpoint list, plan identifiers, and policy defaults change over time and should be read from Microsoft's current documentation rather than from any static article.

The troubleshooting order above resolves common cases, but it cannot diagnose a specific tenant without logs. Administrators should read sign-in logs, audit logs, and gateway logs together. A single log source will confirm one gate while hiding the other.

Microsoft does not publish the precise mapping between server responses and client messages, so some blocks will require a support case. When you open one, include the timestamp, the user principal name, the client type, and the correlation identifier from the client diagnostics. Those four fields let support trace the exact request.

Finally, availability of Copilot features varies by plan tier and region. A feature that is blocked for you may simply not be included in your subscription level, which is an entitlement outcome rather than a fault.