Microsoft 365 Copilot Not Working

Overview

Microsoft 365 Copilot not working usually falls into one of four buckets: account access, browser or app session state, document permissions, or tenant configuration. The fastest fix is not to reinstall everything first. Start by confirming that Copilot fails in more than one surface, such as Word on the web and Word desktop, or Teams web and Teams desktop. Microsoft documents Copilot as a Microsoft 365 experience across supported apps, so troubleshooting should follow the surface where the failure appears, not just the brand name. Use Microsoft Copilot support for official product guidance, Microsoft’s Microsoft 365 Copilot requirements for prerequisites, and Microsoft’s supported browsers for Office on the web guidance when checking browser behavior.

Symptoms

The visible symptom can vary by app. Copilot may be missing from the ribbon, disabled in a chat pane, stuck loading, unable to summarize a document, or available in one Microsoft 365 app but absent in another. In Teams, the problem may look like Copilot not appearing in a meeting or chat context. In Word, Excel, PowerPoint, Outlook, or OneNote, it may appear as a button that does nothing or a prompt box that cannot use the current file. Avoid treating all of these as the same bug. A missing button points toward access, rollout, app version, or admin policy. A button that opens but cannot process content often points toward permissions, file location, or session state.

Why This Happens

Microsoft 365 Copilot sits across identity, Microsoft 365 apps, cloud files, and tenant controls. That makes failures look random when one layer is out of sync. A user can be signed into the wrong account in the browser while the desktop app uses the correct account. A document can be open locally while Copilot expects cloud-backed context from OneDrive or SharePoint. A browser extension can block authentication or storage. An admin can assign a license but still have app, privacy, or compliance settings that affect availability. Microsoft service health can also affect access, but current outage claims must come from your own Microsoft admin portal or an official Microsoft status surface such as Microsoft service health status. For tenant controls, admins should use Microsoft’s Microsoft 365 Copilot setup documentation and Copilot admin center guidance instead of relying on screenshots from older admin portals.

Quick Fixes Before Admin Changes

Use a narrow test path first. Open Microsoft 365 on the web, sign in with the expected work or school account, and test Copilot in the same app where it fails. Then repeat in a private window with extensions disabled. If Copilot works there, the issue is probably browser storage, cookies, cached credentials, or an extension. If it fails in every browser and app for one user, check account access and license assignment. If it fails for multiple users in the same tenant, check service health and admin configuration. This sequence avoids a common gotcha: reinstalling Office when the failure is actually an identity or tenant-side problem.

$ isolate surface
Browser → desktop app → mobile app
$ isolate identity
Correct account → license/access → tenant policy
$ isolate content
Cloud file → permissions → sensitivity or sharing context

Use the pattern below to avoid mixing causes:

For example, if Copilot appears in Word on the web but the Word desktop button is missing for the same account, treat that as an app or desktop session problem before changing tenant policy. If Copilot opens but cannot summarize one shared document while it works on a new OneDrive file, focus on that document’s permissions, location, or protection settings.

Check status, account, and basic access

Start with identity. In Microsoft 365 web apps, select the profile icon and verify the tenant account, not a personal Microsoft account or a different organization. In desktop apps, open the account screen and confirm the same identity. If you use multiple tenants, sign out of all Microsoft accounts in the browser, then sign in only to the target account. Admins should check license assignment and service health from official Microsoft admin surfaces. Microsoft’s official admin documentation is maintained under Microsoft 365 admin documentation, and Copilot-specific prerequisites are listed in Microsoft 365 Copilot requirements. Those are safer reference points for tenant-side checks than forum screenshots or cached search results.

Try a clean browser or app session

Browser state is one of the highest-value checks because it is reversible. Open a private or incognito window, sign in only to the affected Microsoft 365 account, and test the same Copilot action. Disable ad blockers, privacy extensions, script blockers, and enterprise browser add-ons for the test. If Copilot works in the private window, clear Microsoft 365 site data for the regular profile or create a fresh browser profile. If the issue only appears in Safari, Chrome, or Edge, treat it as a browser-specific problem first and compare against Microsoft’s Office on the web browser support. If the web app works but the desktop app fails, update Office, restart the device, and repair the app before changing account settings.

Check file, permission, or feature availability

Copilot can fail because the content context is not usable, even when the button appears. Test with a new document stored in OneDrive or SharePoint rather than a local file, email attachment, or synced copy with unresolved conflicts. Confirm that you can edit the file and that sharing permissions are not blocking the signed-in account. If a protected document, sensitivity label, retention policy, or external sharing rule is involved, ask an admin before bypassing it. This is the edge case many generic fixes miss: Copilot may be available to the user but unable to use the specific document context. The correct fix is content and permission cleanup, not browser cache deletion.

Run platform-specific checks

For Windows desktop apps, restart Office apps, install available Microsoft 365 updates, and use repair options if the problem is app-only. On macOS, quit the affected app completely before reopening it; account tokens can persist across windows. On iPhone or Android, update the Microsoft 365 app, Teams, Outlook, or the specific Office app, then test on Wi-Fi and mobile data. For Teams, compare web and desktop behavior because meeting, chat, and channel context can differ. For Outlook, test both classic and web experiences if both are available in your environment. Use platform isolation before escalating; it produces better support evidence than “Copilot is broken.”

Admin Checks for Microsoft 365 Tenants

Admins should verify three separate controls: the user’s account assignment, app availability, and service health. Do not assume that a working Copilot experience for one user proves tenant-wide health, and do not assume one affected user proves an outage. Check whether the user belongs to the expected tenant, whether required Microsoft 365 services are enabled for that account, and whether organizational policies restrict connected experiences or cloud-based features. Microsoft’s Microsoft 365 Copilot setup documentation and Copilot admin center documentation are the better sources for current admin controls. If multiple users report the same symptom at the same time, collect app names, platforms, timestamps, and screenshots before changing policy. That evidence makes Microsoft support escalation more useful and reduces the risk of breaking working users.

When to Use Each Fix

Use browser cleanup when Copilot works for the same account in another browser or private window. Use app repair when the web version works but a desktop app fails. Use file and permission checks when Copilot opens but cannot summarize, draft against, or reason over a specific document. Use admin checks when the Copilot entry point is missing for the same user across all apps and devices. Avoid reinstalling Microsoft 365 as a default first move; it is slow and often misses the actual cause. The best practical workflow is account first, session second, content third, platform fourth, admin escalation last.

If It Still Fails

If Microsoft 365 Copilot still does not work after clean-session, platform, and permission checks, collect exact evidence before escalation. Capture the app name, web or desktop surface, operating system, browser, signed-in account domain, approximate time, and whether the issue affects one user or many. Include screenshots of the missing button or failing Copilot panel, but avoid sharing sensitive document contents. Admins should check official service health and review account configuration. End users should contact their internal Microsoft 365 administrator first because many Copilot access issues are tenant-managed. If the admin path is unavailable, use Microsoft’s official support entry points rather than third-party outage pages.