When Copilot stops responding, the cause is rarely a single thing. Microsoft Copilot is not one product but a family of experiences that share a name: the Copilot website, the Windows taskbar button, the Edge sidebar, and the Copilot features baked into Microsoft 365 apps like Word, Outlook, and Teams. Each of these runs through a slightly different stack, so “Copilot not working” can mean a blank chat box on the web, a greyed-out button in Windows, a missing icon in your Office ribbon, or a request that hangs forever. This guide walks through the most common reasons, gives you a clear order of steps to fix it, and shows you how to tell whether the problem is on Microsoft’s side or yours. You can always check the current Copilot status on our live dashboard before you spend time troubleshooting.
First, work out which Copilot you mean
Before troubleshooting, pin down where Copilot is failing. The fixes differ a lot depending on the surface, and a problem in one place does not always mean the others are affected.
- Copilot on the web – the chat experience you open in a browser. Mostly affected by sign-in, browser issues, and server load.
- Copilot in Windows – the taskbar or Start menu entry. Tied to your Windows version, regional rollout, and your account.
- Copilot in the Edge sidebar – the panel on the right of the browser. Sensitive to Edge updates, extensions, and sidebar settings.
- Copilot in Microsoft 365 – the assistant inside Word, Excel, Outlook, Teams, and friends. This requires a specific paid license and is the most common source of “I do not even see Copilot” confusion.
Once you know which one is broken, the rest of this guide is much faster to apply.
Account, sign-in, and licensing problems
The single most frequent reason Copilot will not work is an account or licensing mismatch. This is especially true inside Microsoft 365, where Copilot is a separately licensed add-on rather than something every account gets automatically.
You are signed in with the wrong account
Many people have both a personal Microsoft account and a work or school account, and the browser quietly defaults to one of them. Copilot features, history, and licensing are tied to the specific account you are signed in with. If Copilot looks limited, refuses to load chat history, or hides features you expect, check the account avatar in the top corner and switch to the correct one. In a work environment, your organization may only have enabled Copilot for certain accounts or groups.
Your plan does not include the feature
The Copilot inside Word, Excel, and Outlook is gated behind a paid license that an administrator has to assign. If the Copilot button is simply missing from your Office apps, the most likely explanation is that no license has been assigned to your account, not that anything is broken. Personal users sometimes hit a similar wall when a free tier does not include a feature that a paid tier does. Confirm what your plan actually covers before assuming an outage.
Authentication tokens have gone stale
Sometimes the account is right and the license is right, but the sign-in session has expired or become corrupted. Signing out completely and signing back in forces a fresh authentication token and clears a surprising number of “it just spins” problems. On the web, this often resolves issues faster than any other single step.
Regional rollout and availability
Copilot features do not arrive everywhere at once. Microsoft rolls capabilities out by region, by language, and sometimes by account type, so a feature a coworker in another country has may not have reached you yet. This is not a fault and there is no fix beyond waiting, but it explains why two people on identical hardware can see different things.
If you are using a VPN, your apparent region can shift to wherever the exit server is, which occasionally causes Copilot to behave as if you are somewhere it is not fully available. Try disabling the VPN to see whether availability changes. Some experimental or preview features are also limited to specific channels or insider builds, so a missing capability may simply mean you are on the stable track.
Browser and extension conflicts
For the web app and the Edge sidebar, the browser environment is a common culprit. Copilot relies on modern web technology, persistent connections, and scripts that ad blockers and privacy extensions can interfere with.
- Cached files are stale. A half-loaded or outdated cache can leave Copilot stuck on a blank screen. Clearing the cache and cookies for the Copilot and Microsoft domains often fixes it.
- An extension is blocking scripts. Content blockers, script blockers, and aggressive privacy tools can strip out the very requests Copilot needs. Test in a private or incognito window, where extensions are usually disabled by default. If Copilot works there, an extension is the problem.
- The browser is out of date. Old browser versions can fail silently on newer web features. Update to the current release.
- Edge sidebar is turned off. If the Copilot panel is missing in Edge specifically, check the browser settings for the sidebar and the Copilot toggle before assuming a wider failure.
If you are not sure whether the issue is your browser or Microsoft’s servers, our guide on how to tell if an AI service is down or it is just you walks through the isolation steps in detail.
Server load and capacity
Like every large AI service, Copilot runs on shared infrastructure that can get overwhelmed during peak demand or when a new feature drives a spike in usage. When that happens you may see slow responses, requests that time out, generic “try again later” messages, or a model that refuses to start generating. None of these are things you can fix from your end. They tend to clear on their own as load eases or as Microsoft adds capacity.
The useful move here is to confirm whether others are affected rather than retrying endlessly. Our Copilot status page tracks responsiveness and gathers user reports, so you can see at a glance whether the slowdown is widespread. If you want to understand the broader patterns behind these events, our explainer on why AI tools go down covers the common categories of disruption.
Network and firewall issues in work environments
Copilot problems are disproportionately common on managed corporate and school networks, and the reasons are usually local rather than a Microsoft outage. Workplace networks frequently sit behind firewalls, proxies, and content filters that can block the endpoints Copilot needs to reach.
- Firewall or proxy blocking. If IT has not allowlisted the Microsoft and Copilot service endpoints, requests never complete. This often shows up as Copilot loading the interface but never returning an answer.
- Conditional access policies. Some organizations restrict which devices, locations, or network conditions can use AI features. A compliant laptop on the office network may work while the same account on a personal device does not.
- Data and admin controls. Administrators can disable Copilot entirely, restrict it to certain groups, or turn off specific capabilities for compliance reasons. If Copilot vanished overnight across a whole team, an admin policy change is the prime suspect.
- DNS and captive portals. Guest networks and hotel or airport Wi-Fi with sign-in pages can silently break the connection.
If you are on a work device and nothing else here helps, your IT or admin team is the fastest path to a fix, because the controls that matter are on their side.
A step-by-step fix list
Work through these in order. Most people are back up well before the end of the list.
- Check the live status first. Open the Copilot status page. If it is down for everyone, stop here and wait, because no local fix will help.
- Reload and retry once. Refresh the page or restart the app. Transient glitches often clear on a single reload.
- Confirm your account. Check the avatar in the corner and switch to the correct personal or work account.
- Sign out and back in. This refreshes your authentication and resolves a large share of “stuck” sessions.
- Test in a private window. If Copilot works in incognito, disable extensions one by one to find the offender.
- Clear cache and cookies. Clear them for the Copilot and Microsoft domains specifically, then reload.
- Update everything. Update your browser, the Windows build, and your Office apps. Restart afterward.
- Disable your VPN. Rule out a region mismatch caused by the VPN exit location.
- Switch networks. Try a different network, such as a phone hotspot, to rule out a firewall or proxy.
- Check your license. Confirm your plan actually includes the Copilot feature you expect, especially inside Microsoft 365.
- Contact IT or support. On a managed device, your admin can check policies and allowlisting that you cannot see.
How to tell if Copilot is down for everyone
The fastest way to separate a Microsoft outage from a local problem is to look for corroboration. A genuine outage shows a cluster of reports appearing at roughly the same time, across different networks and regions. A local issue shows up only for you, and the service works fine for colleagues or on a different device.
Our Copilot status page combines automated monitoring with crowd-sourced reports, so a spike in reports alongside degraded response checks is a strong signal that the problem is on Microsoft’s side. You can also scan the full live dashboard to see whether related services are struggling at the same time, which sometimes points to a shared infrastructure event. If you want to understand exactly how we determine status, our methodology page explains the checks behind the numbers.
When you have confirmed it is a real outage, the practical question becomes what to do with the time. Our guide on what to do when an AI tool is down covers sensible next steps, and if you need to keep working, the roundup of AI alternatives to use during an outage gives you options. You can also compare neighbors like ChatGPT, Claude, and Gemini on their own status pages.
When it is not really an outage
Plenty of “Copilot not working” reports turn out to be expected behavior rather than failure. It helps to recognize these so you do not burn time chasing a fix that does not exist.
- Content was declined. Copilot may refuse certain requests by design. That is a policy response, not a bug.
- A feature is region-locked. A capability a coworker has may not have rolled out to you yet.
- The license does not cover it. Missing Office integration usually means an unassigned license, not a broken app.
- Usage limits were reached. Some tiers cap how much you can use within a window, and you may need to wait for it to reset.
If you have ruled all of that out and the live data shows everything healthy, the problem is almost certainly local, and the step-by-step list above is your fastest route back. For broader troubleshooting habits that apply across every AI tool, the guides hub is a good place to start, and the companion piece on why ChatGPT is not working covers many of the same isolation techniques from a different angle.
The short version
When Copilot is not working, check the live status first so you know whether to troubleshoot at all. If it is healthy for everyone else, the cause is usually your account, license, browser, or network, and the ordered fix list resolves the vast majority of cases. If it is down across the board, there is no local fix, so save your effort, switch to a backup tool if you need one, and check back once reports settle. Keeping the Copilot status page handy turns a frustrating guessing game into a two-minute diagnosis.
Frequently asked questions
Why is Copilot not showing up in my Microsoft 365 apps?
The most common reason is licensing. Copilot inside Word, Excel, Outlook, and Teams is a separately assigned paid add-on, so if no license has been assigned to your account, the button simply will not appear. Confirm with your administrator that a Copilot license is assigned to you, then make sure your Office apps are updated and you are signed in with the licensed account rather than a personal one.
How do I know if Copilot is down for everyone or just me?
Look for corroboration. A real outage produces a cluster of user reports across different regions at the same time, while a local issue affects only you. Check our Copilot status page, which combines automated monitoring with crowd-sourced reports. If response checks are degraded and reports are spiking together, it is on Microsoft's side. If everything looks healthy, the problem is almost certainly local to your account, browser, or network.
Why does Copilot work for my coworker but not for me?
Several things can cause this. Copilot features roll out by region, language, and account type, so a capability may not have reached you yet. You may also be on a different plan or license tier, signed in with the wrong account, or affected by an admin policy that enables Copilot only for certain groups. On a work device, conditional access rules can also allow some users while blocking others.
Can a firewall or work network block Copilot?
Yes, and this is common on managed corporate and school networks. Firewalls, proxies, and content filters can block the endpoints Copilot needs, causing it to load the interface but never return an answer. Conditional access policies and admin controls can also restrict or disable it entirely. Test on a different network, such as a phone hotspot, to confirm, then contact your IT team, since the relevant controls are on their side.
What should I do first when Copilot stops responding?
Check the live status before anything else, because if Copilot is down for everyone, no local fix will help and you will only waste time. If the status looks healthy, reload once, confirm you are signed in with the correct account, then sign out and back in to refresh authentication. From there, test in a private browser window, clear the cache for Microsoft domains, and update your browser and apps.