If Copilot reports that your tenant does not support a feature, first identify which feature, account, and app produced the message. The wording alone does not prove that your organization needs another subscription, and there is no universal “turn on Copilot for the tenant” switch that fixes every case.
This guide covers organizational Microsoft Copilot, formerly Microsoft 365 Copilot. It does not cover a personal Copilot subscription or Copilot Studio agent publishing. Official guidance checked October 14, 2026.
What the tenant-support message does—and does not—establish
A feature can be unavailable because of licensing, the signed-in tenant, an app requirement, a policy, or its rollout scope. Treat these as possibilities to investigate, not a diagnosis supplied by the error. Record the exact message and the action immediately before it appeared.
- Account: the affected app must be using the intended work or school account. A personal Microsoft account with a similar email address is not the same identity.
- Entitlement: access to eligible Copilot Chat does not establish access to every paid Copilot feature. Check the requested capability against the user’s assigned products.
- Scope: an error in a meeting, mailbox, document, or agent can have requirements that do not apply to ordinary chat.
Use Microsoft’s current requirements to check the specific workload. Do not use an old Teams version number or the presence of a Copilot icon as proof of support.
Check the account and entitlement before changing configuration
- Reproduce with the affected user. Save any open work. Check the account displayed in the app, the organization name, and whether the same action fails in the supported web version. If only one account fails, do not change tenant-wide settings.
- Ask an authorized license administrator to inspect the assignment. In the Microsoft 365 admin center, open Users > Active users, select the user, then Licenses and Apps. Confirm the intended base product and Copilot entitlement. The administrator should also inspect any disabled services and assignment errors, rather than assume that a checked product box means successful provisioning.
- Correct an actual assignment problem. If an approved license is missing, assign the available product and save. For a group assignment, resolve the group’s license error or membership issue. Do not remove the user’s base Microsoft 365 license as a troubleshooting reset. See Microsoft’s license-assignment procedure.
- Allow provisioning, then refresh. Microsoft’s Copilot deployment guide says some apps can take up to 24 hours to show Copilot after assignment. Restart or refresh the app and sign in with the licensed account. Fifteen minutes is not a guaranteed completion time.
- Test the original feature. A successful general chat does not establish that meeting recap or document editing works. Repeat the smallest safe version of the action that failed, with non-sensitive test content.
An administrator can use the Copilot License Details diagnostic linked from Microsoft’s requirements page to investigate the user. Copilot administration is under the admin center’s Copilot area; do not search for an undocumented global enable checkbox under Org settings.
If the error remains, narrow the failure before escalating
One user fails while a colleague succeeds
Compare the two accounts’ actual feature entitlements, assignment errors, tenant, and app version. Use the same harmless test document only when both people already have permission to it. A colleague’s success is useful evidence, but it is not a reason to copy their permissions wholesale or promote the affected user to an administrator.
The same user succeeds on the web but not on desktop
Record the desktop app’s build and update channel and ask IT to compare them with the supported configuration. Also check connected-experience policies. On managed devices, use the organization’s update process; do not bypass its controls or uninstall Office before establishing a client-specific problem.
Several users fail at the same time
Have the administrator check service health, recent licensing changes, and the tenant’s feature announcements. If authentication or connectivity is failing, provide the time and affected app to the identity or network team. Do not disable Conditional Access or security inspection across the organization to see whether the message disappears.
Only one workload or feature fails
Check that feature’s own requirements—for example, mailbox availability for email-grounded tasks or meeting policy for meeting features. Gather the feature name, app/build, affected account and tenant, timestamp with time zone, error or correlation ID if shown, and the result of the web-versus-desktop test. Send that evidence through the organization’s support channel. There is no evidence-based promise that repeating license changes will resolve every tenant-support error.