Reports of Microsoft Copilot hiccups are spreading online, but as of July 21, 2026, there’s no sign of a global outage. Instead, users are hitting a tangle of local failures—blank panes, endless spinners, sign-in loops—that masquerade as a full service meltdown. The real story is more nuanced, and it starts with understanding that “Copilot” now means many different things.

Why “Copilot is down” isn’t always what it seems

Microsoft’s Copilot brand has ballooned far beyond the original Bing chat integration. Today, “Copilot” can refer to the standalone Windows app, the consumer website, the Edge sidebar helper, Microsoft 365 Copilot Chat, paid features inside Word and Excel, GitHub Copilot, security tools, and even custom agents built by organizations. Each of these services runs on its own infrastructure, with distinct authentication flows and dependencies.

That fragmentation creates a diagnostic headache. Two colleagues might both insist “Copilot is down,” yet one is struggling with a damaged app package, while the other is blocked by a corporate access policy or an expired license. A successful response from copilot.microsoft.com does not prove your organization’s tenant is healthy; a GitHub Copilot outage does not mean your Windows Copilot app should be blank. The visible interface is only one link in a long chain that includes Microsoft identity servers, cloud-hosted models, content delivery networks, and—in enterprise settings—Microsoft Graph, Exchange, SharePoint, and compliance filters. A break anywhere in that chain can bring Copilot to a halt even when Windows itself is running fine.

This guide walks you through isolating the problem, applying targeted fixes, and avoiding the aggressive steps that can make things worse. We’ll cover what to do whether you’re a home user, a power user on a work machine, or an IT admin managing a fleet.

The quick check: Is it you or Microsoft?

Before you reset anything, run a five-minute isolation test. This will tell you whether the issue is global, tied to your account, locked to your device, or caught in your network.

  1. Open Copilot in a private browser window. Go to copilot.microsoft.com in an InPrivate or Incognito session. This bypasses cached cookies and extensions that often corrupt sessions. If it works here, your normal browser profile likely holds damaged site data.
  2. Sign in with the same Microsoft account. A successful private session proves the cloud service and your account are healthy; the fault lies in the browser’s stored state or a conflicting extension.
  3. Test another browser. Switch to Edge, Chrome, or Firefox. If Copilot loads there, the original browser or its policies are to blame.
  4. Try another network. Disconnect Wi-Fi and connect via a mobile hotspot. This instantly rules out your router, DNS provider, corporate proxy, or VPN.
  5. Try another device. Use your phone or a second PC. If Copilot works on a different machine with the same account, the problem is device-specific.
  6. Try another account, if possible. A different Microsoft account that works points to a license, age, region, or tenant policy issue.
  7. Check official service health. Consumer users can glance at a status checker like DownDetector; enterprise users should open the Microsoft 365 admin center’s Service Health dashboard for tenant-specific advisories.

Interpreting the results is straightforward. Copilot dead across multiple devices and networks for the same account? Investigate account eligibility, licensing, or a cloud incident. Dead for several unrelated accounts across different networks? A broader Microsoft-side problem becomes plausible. Works on a hotspot but not Wi-Fi? Focus on your router, DNS, proxy, or VPN. Works in a private window? Clear only Copilot-related site data—don’t nuke your entire browser profile just yet.

Fixing the Windows Copilot app

If the web version works but the dedicated Windows app shows a blank screen, endless spinner, or “Something went wrong” message, the app itself or its runtime dependencies are likely broken. The current Windows Copilot experience runs as a standalone application, not the deeply integrated taskbar panel from earlier Windows 11 releases, so app repair and reinstallation are effective first steps.

First, ensure Windows and the app are up to date.
Open Settings > Windows Update, install all pending updates, and then open the Microsoft Store, go to the Library, and check for app updates. A mismatch between an old Copilot package and updated Windows components can cause launch failures.

Use the built-in repair tools.
Navigate to Settings > Apps > Installed apps, find Microsoft Copilot, and select its advanced options. Here you’ll find three escalating controls:
- Terminate stops the app and background processes. Try again immediately.
- Repair tries to fix the app without deleting its local data. This often resolves rendering or authentication issues.
- Reset removes local app state, including cached authentication tokens. You’ll need to sign back in, but it clears stubborn broken cache entries.

If repair and reset don’t cut it, uninstall Copilot through Settings, restart your PC, and reinstall the official app from the Microsoft Store. Avoid third-party download portals.

The WebView2 wildcard.
Some Windows apps use Microsoft Edge WebView2 to render web content inside an app window. If multiple web-backed apps show blank content or crash, the WebView2 runtime may be corrupted. Update Microsoft Edge to its latest version first; this often refreshes the shared WebView2 component. If issues persist, administrators on managed devices should check that application-control software hasn’t accidentally blocked or removed WebView2 components.

Getting Copilot back in Microsoft Edge

Edge sidebar failures require a different playbook. Microsoft’s own troubleshooting documentation (published at learn.microsoft.com) emphasizes account eligibility, connectivity to service endpoints, authentication state, and group policies that can silently disable Copilot.

Update and restart Edge completely.
Check edge://settings/help for updates. After installing the latest version, close all Edge windows and verify in Task Manager that no msedge.exe processes remain before reopening. Lingering processes can preserve a broken session.

Clear site data, not your whole profile.
Before you delete the profile, open edge://settings/clearBrowserData, go to “Cookies and other site data,” and clear data associated with Copilot and Microsoft sign-in pages. Restart Edge and sign in again. A private Edge window remains a handy comparison—if Copilot works there, the regular profile is the culprit.

Disable extensions strategically.
Privacy blockers, VPN extensions, ad blockers, and script filters can break Copilot. Disable all extensions temporarily, and if Copilot works, re-enable them in groups to find the offender.

Profile testing without destruction.
Add a temporary Edge profile (edge://settings/profiles) and test Copilot without importing any extensions. If it works, your original profile is likely corrupted. Only then consider migrating to a fresh profile, after ensuring sync has completed and important data is backed up.

Policy pitfalls.
For enterprise users, the EdgeSidebarAppUrlHostBlockList policy is a common trap. If your organization uses a wildcard block (*) and an allow list, Copilot Chat requires specific internal URLs to be permitted. In Edge 146 and later, these are edge://discover-chat, edge://commercial-copilot-chat, and chrome-untrusted://commercial-copilot-chat. An administrator must check edge://policy and add any missing entries to the allow list, then restart Edge.

When you’re stuck in a sign-in loop

A sign-in loop doesn’t always mean your password is wrong. Copilot authentication involves multiple layers: your Microsoft account, your Edge profile, your Windows login, and app-specific sessions. Cached tokens, mismatched identities, or even an incorrect system clock can break the chain.

Sign out everywhere and start fresh.
Sign out of the affected Copilot interface, close it completely, and reopen it. In Edge, verify which profile is active and that Copilot is using the intended account.

Check your device’s time and date.
Incorrect system time can invalidate authentication tokens. Go to Settings > Time & language > Date & time, enable “Set time automatically,” and click “Sync now.” This is especially important after a BIOS reset, dual-boot clock drift, or prolonged battery failure.

Account eligibility matters.
Copilot isn’t available everywhere. Child accounts, unsupported regions, and certain license types won’t have access. The official Microsoft support article for Copilot on Windows reminds users to verify that the signed-in account meets age and platform requirements. Desktop editions of Windows 11 (Home, Pro, Enterprise) are supported; Xbox and other non-desktop SKUs are not.

For work accounts, check licenses and policies.
Microsoft 365 Copilot requires a specific license assignment and successful provisioning. Administrators should review sign-in logs, conditional access policies, and device compliance status in Azure AD / Entra ID.

Microsoft 365 Copilot: A workplace puzzle

Copilot problems inside Word, Excel, PowerPoint, Outlook, or Teams demand a different lens. Even if Copilot Chat works in the browser, in-app features can fail due to application builds, connected experiences settings, file formatting, or backend workload outages.

Verify the license and update channel.
Open an Office app, go to File > Account, and confirm that the correct Copilot license appears and that Office is fully updated. Organizations using controlled update channels may receive Copilot capabilities later than others.

Check connected experiences.
Microsoft 365’s privacy controls can disable cloud-backed features. If “connected experiences” are turned off—either by the user or by a tenant policy—Copilot buttons may vanish or fail to process document context. This is a policy setting, not a repair issue; reinstalling Office won’t override it.

File location and format.
Many Copilot operations work only with files stored in OneDrive or SharePoint and saved in modern formats like .docx or .xlsx. Local files, protected documents, or incompatible content can cause failures. Test with a simple new document saved to your organizational OneDrive.

Workload health is upstream.
If Copilot can’t summarize email or pull meeting context, the issue may lie with Exchange Online, SharePoint, Teams, or Microsoft Graph. A green chat interface doesn’t guarantee that all grounding services are available. Check the Microsoft 365 admin center’s Service Health for workload-specific incidents.

For IT teams: A systematic approach

When Copilot misbehaves across an organization, don’t ask every employee to clear their caches. Build an incident matrix first:

  • Which Copilot product (Windows app, Edge sidebar, M365 app, etc.) is affected?
  • When did failures start? Correlate with deployments, policy changes, or service advisories.
  • Which users and accounts? Note license types and authentication methods.
  • What are the symptoms exactly? Capture error messages and correlation IDs where available.
  • What networks are involved? Office LAN, home broadband, VPN, mobile hotspot?
  • Is there a known-good comparison? Does Copilot work for a user on a different device, network, or browser?

This matrix quickly distinguishes a tenant-wide service degradation from a proxy misconfiguration. Then, review recent changes: proxy rules, certificate inspection settings, browser policies, Office builds, Windows updates, or conditional access modifications. The timing alone doesn’t prove causation, but it narrows the hunt dramatically.

Preserve security controls. Don’t permanently relax TLS inspection or disable endpoint protection just to make Copilot load. If a mobile hotspot restores access, treat that as diagnostic evidence—not a production workaround. Organizational data must stay on approved networks.

What not to do

Aggressive troubleshooting often does more harm than good. Avoid these common missteps:

  • Don’t reach for registry cleaners or system optimizers. Copilot issues are rarely caused by corrupt system files, and a one-click “PC repair” tool won’t fix a cloud service outage, a borked token, or a tenant policy. If you genuinely suspect Windows corruption, use the built-in SFC and DISM tools—but only because other components are failing too, not just because Copilot threw an error.
  • Don’t delete browser or Windows profiles prematurely. A temporary test profile should always precede a profile apocalypse. If the test profile fails identically, the problem is elsewhere.
  • Don’t spiral into reinstalling the same app over and over. A clean reinstall that doesn’t help means the issue lies in authentication, WebView2, network filtering, or account eligibility—not the app binary.
  • Don’t ignore the simplest checks. Verify your internet connection, time settings, and account type before diving into advanced diagnostics.

The bottom line

As of July 21, 2026, there is no widespread Copilot outage. What users are experiencing—blank windows, endless spinners, or sign-in loops—is almost always a local, solvable problem. The key is to resist the knee-jerk assumption that everything is down, and instead isolate the failing surface. For most home users, that means testing the web version, comparing networks, and repairing or reinstalling the Windows app. For enterprise workers, it means engaging IT to check service health, licenses, and policies before any endpoint gets wiped. Copilot’s fragmented architecture is confusing, but it also means you’re never truly locked out: another door is almost always open.