Microsoft Copilot Service Health: Where to Check Outages

When Copilot stops responding, fails to generate responses, or returns errors, you may suspect an outage rather than a local problem. Service disruptions on Microsoft’s side can affect Copilot across Microsoft 365 apps, the standalone website, and Windows. This article explains where to verify Copilot service health, how to interpret status messages, and what to do if an outage is confirmed.

Microsoft publishes real-time and historical health data through its admin portals and public dashboards. Knowing which tool to check saves time and prevents unnecessary troubleshooting. You will learn the three primary locations for outage information and how to distinguish a service issue from a client-side fault.

Why Copilot Service Health Status Matters

Copilot depends on cloud services hosted in Microsoft’s global data centers. When those services degrade or stop, Copilot cannot process prompts, access Microsoft Graph data, or generate responses. The root cause is not your device, your network, or your Microsoft 365 license. It is a service-side failure that Microsoft must resolve.

What triggers a service health incident

Microsoft defines a service incident as any event that impairs the availability or performance of a service. For Copilot, incidents include authentication failures, backend timeouts, data-source connectivity loss, and degraded response generation. Incidents can affect all users globally or a specific tenant region.

How Microsoft communicates incidents

Microsoft posts incident details to the Service health dashboard within 30 minutes of detection. Each incident includes a title, description, affected services, user impact statement, current status, and a timeline of updates. Incidents remain visible for 30 days after resolution.

Where to Check Copilot Service Health

Three locations provide Copilot outage information. The best choice depends on whether you are a Microsoft 365 admin, a user without admin rights, or someone who needs notifications on a mobile device.

Method 1: Microsoft 365 admin center service health dashboard

This dashboard is the most detailed source. It requires a Microsoft 365 Global Admin, Service Support Admin, or Reports Reader role. To access it:

1. Sign in to the Microsoft 365 admin center
   Go to admin.microsoft.com and sign in with an account that has admin privileges for your tenant.
2. Navigate to Health > Service health
   In the left navigation pane, click Health and then select Service health. The dashboard loads a list of all Microsoft 365 services.
3. Find Copilot in the service list
   Scroll to find Microsoft Copilot or Microsoft Copilot for Microsoft 365. The status column shows a green check mark for healthy, a yellow warning for advisory, or a red exclamation for an active incident.
4. Click the service name for details
   Clicking Microsoft Copilot opens the incident view. Read the User impact statement to understand what features are affected. Check the Status field — it shows Investigating, Restoring service, or Resolved.

Method 2: Public Microsoft 365 Service health status page

Microsoft offers a public page that lists major service incidents without requiring authentication. This page is useful for users who are not admins or who want a quick check before contacting IT support.

1. Open the public status page
   Go to status.cloud.microsoft.com in any browser. No sign-in is required.
2. Review the current status summary
   The page shows a table of services with All services healthy or a red banner listing active incidents. Scroll to Microsoft Copilot to see its status.
3. Click an incident for more detail
   If an incident is listed, click its title to expand the description, affected region, and last update time. The public page shows less detail than the admin dashboard but confirms whether a widespread outage exists.

Method 3: Microsoft 365 admin mobile app

The admin mobile app sends push notifications for new incidents and status changes. It is the fastest way for admins to learn about Copilot outages away from a desktop.

1. Install the Microsoft 365 admin app
   Download the app from the Apple App Store or Google Play Store. Sign in with your admin account.
2. Open the Health tab
   Tap the Health icon at the bottom of the screen. The tab displays a list of services and their current status.
3. Enable push notifications
   Tap the gear icon in the top-right corner, then tap Notifications. Toggle Service health to On. You will receive alerts when a Copilot incident is created or updated.

What to Do When a Copilot Outage Is Confirmed

If the service health dashboard shows an active incident for Copilot, you cannot fix the problem from your side. Follow these steps to minimize disruption and stay informed.

Check the user impact and estimated resolution time

In the incident details, read the User impact section. It describes which Copilot features are affected — for example, Users may be unable to generate responses in Word and Excel. The Estimated time to resolve field, if present, provides a target. If no estimate is given, watch the timeline for updates.

Subscribe to email notifications

In the Microsoft 365 admin center service health dashboard, click Preferences in the top-right corner. Under Email notifications, add your email address and select Microsoft Copilot as a service to monitor. You will receive an email when the incident status changes.

Communicate the outage to users

If you are an admin, inform your organization that Copilot is experiencing a service incident. Provide the incident ID and a link to the public status page so users can check the status themselves. Advise them to avoid retrying Copilot repeatedly, as this will not speed up resolution.

If Copilot Health Shows No Incident but Copilot Still Fails

When the service health dashboard shows all green but Copilot is not working, the problem is likely on your side. Common causes include network restrictions, browser cache issues, or misconfigured policies.

Copilot returns a generic error message

If Copilot displays Something went wrong or Unable to connect, check your network firewall. Ensure that the required endpoints for Copilot are allowed. Microsoft publishes the list at docs.microsoft.com under Office 365 URLs and IP address ranges. Blocked endpoints for login.microsoftonline.com or copilot.microsoft.com will prevent Copilot from working even when the service is healthy.

Copilot is grayed out in Microsoft 365 apps

If the Copilot button appears disabled in Word, Excel, or PowerPoint, the admin may have turned off Copilot for your tenant. Verify this in the Microsoft 365 admin center under Settings > Org settings > Microsoft Copilot. If the toggle is Off, request your admin to enable it.

Copilot works on one device but not another

This indicates a client-side issue. Clear the browser cache and cookies, or reinstall the Microsoft 365 app. For Windows, check that the Copilot app is not blocked by a group policy. Run gpresult /h gp.html in Command Prompt to review applied policies.

Item	Service Health Dashboard	Public Status Page
Access requirement	Microsoft 365 admin role	No sign-in needed
Detail level	Full incident timeline, user impact, affected regions	Summary description and status
Update frequency	Real-time with admin notifications	Updated within 30 minutes of incident change
Historical data	30 days of past incidents	Current incidents only
Best for	IT admins managing tenant health	End users verifying a suspected outage

You can now check Copilot service health using the Microsoft 365 admin center, the public status page at status.cloud.microsoft.com, or the admin mobile app with push notifications enabled. When an outage is confirmed, subscribe to email updates and communicate the incident ID to your team. As an advanced tip, set up a service health webhook in the admin center to automatically post incident updates to a Teams channel or Slack workspace for faster awareness.