Office 365 Health Status and Service Updates

Current Office 365 Health Status

For the latest official Office 365 health status, check Microsoft’s service status page or the Service health dashboard in the Microsoft 365 admin center. Microsoft now uses the Microsoft 365 name for many services that were previously called Office 365.

The public status page shows known problems that may prevent customers from reaching Microsoft 365 services or signing in to the admin center. It is useful when you cannot access your organization’s dashboard. The admin dashboard provides more specific information based on your organization and its services.

Do not assume that a blank page, slow connection, or single error message confirms an outage. Look for an active incident or advisory that names the affected service, feature, or region.

How to Check Service Health

1. Open {site} and find the Microsoft 365 admin center.
2. Sign in with an administrator account that has permission to view service health.
3. Open Health in the navigation menu, then select Service health. You may also see a Service health card on the admin center home page.
4. Review the Overview tab for active incidents, advisories, and the current state of each service.
5. Select an issue title to read its scope, latest update, and restoration progress.

Global Reader, Service Support Administrator, and Helpdesk Administrator roles may be able to view health information, depending on the organization’s permissions. Regular users usually need to ask their workplace or school administrator to check the tenant-specific dashboard.

If the admin center itself is unavailable, use Microsoft’s public service status page. From {site}, search for “Microsoft service status” and choose the official Microsoft result. The public page is less specific than the signed-in dashboard but can confirm certain broadly reported problems.

Understanding Status Messages

Status wording tells you both the type of problem and the stage of Microsoft’s response:

• Service operational means Microsoft is not reporting an active issue for that service.
• Investigating means Microsoft is reviewing reports or diagnostic information and has not yet confirmed the full cause or scope.
• Service degradation means the service remains available, but some users or features may be slow, unreliable, or unavailable.
• Service interruption means access to a service or important feature is unavailable for affected users.
• Restoring service means Microsoft has taken corrective action and is working to return the service to normal.
• Extended recovery means the immediate problem has been addressed, but complete recovery is taking additional time.
• Service restored means Microsoft reports that the affected service has recovered.

An incident normally describes an unplanned disruption. An advisory may describe limited impact, degraded performance, or a situation that requires attention without representing a complete outage. Read the full notice because a general status label does not show whether your organization, users, or features are included.

Check a Specific Microsoft 365 Service

On the Service health page, find the service table and review the Health column. Select Exchange Online for email and calendar problems, Microsoft Teams for meetings or messaging, SharePoint Online for sites and shared content, or OneDrive for file access and synchronization.

Open any active notice beside the service. Check the user impact, affected features, geographic scope, and available administrator actions. A service can be operational overall while one feature has an advisory, so compare the notice with the exact task that is failing.

If several services fail at once, also examine notices concerning identity, authentication, network access, or Microsoft 365 for the web. A shared dependency can affect more than one product.

What to Do During an Outage

If an official notice matches your symptoms, avoid repeatedly changing passwords, reinstalling applications, or altering organization-wide settings. Record the incident identifier and follow Microsoft’s updates. Use an approved alternate work method if your organization has one.

If no matching incident appears, make a few quick checks:

• Try the same service in a private browser window or a different supported browser.
• Check whether another user in the same organization has the same problem.
• Switch between Wi-Fi and another trusted network, if available.
• Restart the affected app and device, then install pending supported updates.
• Confirm the device clock and time zone are correct.
• Note the exact error message, time, service, account type, and action that failed.

A problem affecting one device points toward local software or network settings. A problem affecting one account may involve permissions, licensing, or account configuration. A problem affecting many users in the same organization may require administrator investigation even when Microsoft reports the service as operational.

Incident History and Updates

Select an incident or advisory in Service health to open its details. Microsoft’s updates may include the time of each message, reported user impact, affected features, current investigation, mitigation work, and the next expected update point. The newest entry normally appears in the incident timeline.

Use the issue identifier when reporting the problem internally or contacting support. After restoration, the notice may include a closure summary with the cause, start and end times, and follow-up information. Administrators can also review resolved issues in the Service health history. Planned maintenance and broader service changes may appear in the Message center instead of as an active outage.

Contact Microsoft Support

If the Office 365 status health information shows no relevant incident and the problem continues, an administrator can open Help and support in the Microsoft 365 admin center. Search for the symptom, follow the suggested diagnostics, and create a support request when the automated guidance does not solve it.

Include the affected service, incident identifier if one exists, exact error text, first observed time with time zone, number of affected users, troubleshooting already completed, and whether the problem occurs on another device or network. Regular users should contact their organization’s IT administrator, who can check tenant-specific health and account configuration before escalating the case to Microsoft.