A Microsoft 365 admin-center incident recorded for October 5–6, 2026, involved intermittent access failures for administrators. The available incident record does not confirm an outage affecting the Exchange Admin Center or Outlook. Check your tenant’s Service health details before treating an admin-portal problem as an email outage.
What happened in the October 5–6 incident?
PennO365’s incident-history extract records intermittent access problems in the Microsoft 365 admin center. It lists a start time of October 5, 2026, at 10:28 PM UTC, and an end time of October 6, 2026, at 6:16 AM UTC. The extract attributes the performance degradation and access failures to an unexpected influx of requests. Incident-history extract
According to that extract’s final update, Microsoft rolled infrastructure back to a previous build, changed API response behavior, turned off a recent service change, and reduced dropped calls. This account describes the incident record; it is not independent confirmation of the technical changes.
The record identifies the Microsoft 365 admin center, not the Exchange Admin Center or Outlook, as the affected service. It therefore does not establish that Outlook mail, calendar, sign-in, or other Microsoft 365 apps were down in the same incident. The Microsoft Learn guidance and public status page explain how to check service status, but do not independently confirm this specific incident. Microsoft Learn: How to check Microsoft 365 service health · Microsoft service status
Is Outlook or the Exchange Admin Center down?
The incident record alone cannot answer either question. An administrative portal failure is not proof that users’ mail service is unavailable. Likewise, trouble in Outlook does not necessarily mean the Exchange Admin Center is down. Confirm the affected service and symptom in your organization’s tenant-specific incident details.
First identify what is failing: opening the Exchange Admin Center, signing in to Outlook, or using a particular Outlook feature. Then note whether the problem affects one user, several people, or the whole organization, and whether it involves Outlook on the web, desktop, or mobile. These distinctions help an administrator match symptoms to a service-health notice rather than assume all Microsoft 365 services share the same outage.
Rank #2
How to check Microsoft 365 service health
- For a business or enterprise tenant: Ask a tenant administrator to open the Microsoft 365 admin center and go to Health > Service health. Check active incidents and advisories, then review issue history for a matching service and symptom. Microsoft says this is where administrators can view current service status and recent issues. Microsoft Learn: How to check Microsoft 365 service health
- If the admin center will not open: Check Microsoft’s public status page for known service issues. The public page separates consumer-product information from Microsoft 365 business and enterprise service health; Microsoft directs business and enterprise users to the admin center for detailed tenant status.
- If no matching issue is listed: When the admin center is accessible, an administrator can report the issue through Service health so Microsoft can assess whether it is widespread and service-originated. Include the affected service, approximate time, error text, and scope. A report is not a guarantee of a fix or restoration time. Microsoft Learn: How to check Microsoft 365 service health
- Recheck for updates: Use the official status information for the affected tenant or service. Do not assume a restoration estimate unless Microsoft publishes one for the specific incident.
What to include when reporting the problem
- The affected surface: Microsoft 365 admin center, Exchange Admin Center, Outlook on the web, Outlook desktop, or Outlook mobile.
- The task that fails: sign-in, mail flow, calendar, search, or administration.
- How many users are affected and whether they share the same tenant.
- When the problem began, the exact error text, and whether the behavior changes across devices or Outlook versions.
These details help describe and distinguish the symptoms; they do not establish that the October incident affected Outlook or guarantee that reporting will resolve a current outage.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →
