Is Microsoft Copilot down?

Understanding Microsoft Copilot availability

Microsoft Copilot availability can vary by feature, account, region, device, and connection. A problem may appear as a page that will not load, repeated sign-in prompts, failed prompts, missing conversations, timeouts, or responses that never complete. These symptoms do not always indicate a platform-wide outage.

Microsoft's official service-status portal is the primary status source for this page. Compare its information with the behavior you observe in Copilot. Testing a private browser window, another browser, device, or network can help distinguish a broader service problem from local browser, account, or connectivity issues.

If Copilot loads and accepts prompts but produces an incomplete, unexpected, or low-quality answer, the service is reachable. Treat that as a response-quality or feature-specific problem rather than automatically classifying it as an availability outage.

Troubleshooting Microsoft Copilot problems

Check for a wider service issue

• Review Microsoft's official service-status portal.
• Record the exact symptom and when it began: blank page, failed prompt, sign-in loop, missing conversation, timeout, or displayed error.
• Test Copilot in a private browsing window, then try another browser or device. If the same failure occurs across different environments, a service-side or account-platform issue becomes more plausible.

Do not treat one failed browser session as proof of a Copilot outage. Status information may also differ by feature, account, region, or connection.

Browser and device causes

If Copilot works in another browser or device, focus on the original browser rather than the wider service. Reload the page, test a private window, and temporarily disable extensions that modify scripts, cookies, privacy controls, or network requests. For a redirect or sign-in loop, clear site data for Copilot using the browser's normal site-data controls. Avoid clearing unrelated data unless necessary.

Account and sign-in causes

If the page loads but authentication repeatedly fails, confirm that you are using the intended Microsoft account and sign out and back in once. Test another browser or device to determine whether the issue follows the account or remains limited to the original session. If only one feature or conversation is unavailable while other Copilot functions work, document that narrower symptom instead of reporting a complete outage.

Network, DNS, and connection causes

Try a different connection, such as a mobile network, when appropriate. If Copilot works there, investigate the original network's VPN, proxy, firewall, content filter, or DNS configuration. A hostname-resolution failure points toward DNS or filtering; a refused connection or repeated timeout points toward the connection path or an intermediate control. These errors can occur even when Copilot is available to other users.

API and integration issues

No API domain is recorded for this service. Do not assume that an error in another Microsoft endpoint, application integration, or developer workflow has the same status as the Copilot web experience. For an integration problem, record the exact endpoint, request context, response, and time of failure, then compare that evidence with the web experience.

When to report a likely broader issue

A broader service or platform issue is more plausible when Copilot fails consistently across browsers, devices, and separate networks, particularly when the official status portal also reports a related incident. Preserve the time, symptom, affected feature, account context, and displayed error so the issue can be diagnosed without repeating unrelated local changes.