Microsoft Office 365 Outage and Service Status

Check the Current Microsoft Office 365 Status

Start with Microsoft’s official service-health information. Open {site} and look for Microsoft 365 service status or service health. This is the best place to confirm a Microsoft Office 365 outage because Microsoft can post active incidents, advisories, affected services, and progress updates there.

Look for a notice marked as an incident, interruption, degradation, or advisory. Read which service is affected, when Microsoft first identified the problem, and whether the notice applies to your region or organization. An issue with Exchange Online may affect email while Teams, OneDrive, or other Microsoft 365 services continue working.

Check the time on the newest update. An old notice may describe a resolved event rather than a current outage. Do not rely on an estimated restoration time unless it appears in an official Microsoft update.

Is Microsoft Office 365 Down for Everyone?

A failed sign-in or a page that will not load does not always mean Microsoft Office 365 is down for everyone. Compare what you see with the official Microsoft Office 365 service status and test the problem in a controlled way.

• Ask a coworker in the same organization whether the same service fails for them.
• Try another Microsoft 365 app. If email fails but another app works, the issue may affect only one service.
• Try a different device while using the same account.
• Switch between Wi-Fi and cellular data if both are available.
• Check whether other unrelated sites or apps load normally.
• Note whether the problem affects one account, several users, or the entire organization.

If many users, devices, and networks show the same failure and Microsoft reports a matching incident, a widespread service problem is likely. If only one account or device is affected, focus on local settings, sign-in access, or an organization-specific restriction.

Review Service Health in the Admin Center

Authorized administrators can see organization-specific information in the Microsoft 365 admin center. Sign in through the official Microsoft site, open the health area, and select service health. Access depends on the administrator role assigned to the account.

Review both active incidents and advisories. Open the relevant entry to check:

• The affected Microsoft 365 service or feature.
• The reported user impact and symptoms.
• Whether the organization may be affected.
• The incident identifier and current status.
• The time of the latest Microsoft update.
• Any temporary guidance supplied by Microsoft.
• The history of earlier updates and recovery actions.

Administrators should compare Microsoft’s description with reports from their users. Save the incident identifier and update times because they can help when communicating internally or contacting support. Continue checking the same entry until Microsoft marks the incident resolved, then confirm that service has returned for affected users.

What to Do During an Office 365 Outage

When Microsoft confirms an outage, avoid repeated password changes, app reinstalls, or major account changes. Those actions usually do not restore a service affected on Microsoft’s side and may create another sign-in problem later.

1. Check whether another Microsoft 365 app remains available.
2. Preserve open work. Copy important text to a local note or save the file locally if the app allows it.
3. Do not repeatedly refresh a page if unsaved work is still visible.
4. Switch networks once to rule out a local connection failure.
5. Record the service name, error message, time, and incident identifier.
6. Follow official updates and wait for confirmed restoration.

If work is urgent, use an approved process already provided by your organization. Do not send sensitive information through an unapproved personal account or service. After Microsoft reports recovery, close and reopen the affected app, sign in again if requested, and test the action that previously failed.

Troubleshoot When No Outage Is Reported

If Microsoft reports no matching incident, the problem may involve the browser, app, connection, account, or organization. These checks are for cases without a confirmed outage.

• Confirm that the device has a working internet connection.
• Check the entered account name for typing errors and make sure you are using the intended work, school, or personal account.
• Open a private browsing window or try another supported browser.
• Clear only the relevant Microsoft sign-in cookies if the page is stuck in a sign-in loop.
• Close and reopen the Microsoft 365 app, then check for an available app update.
• Restart the device if several apps are behaving unexpectedly.
• Ask an administrator whether the account is active and properly authorized.

Keep the exact error message rather than summarizing it as “not working.” A code, timestamp, screenshot, and description of the failed action can reveal whether the issue is tied to authentication, permissions, a device, or one Microsoft 365 service.

Contact Microsoft Support

An organization user should usually contact the workplace or school administrator first. The administrator can review organization-specific service health, check account status, and determine whether other users are affected. An administrator should seek official Microsoft help when no relevant incident appears, the reported impact does not match the official notice, or service remains unavailable after Microsoft reports recovery.

Individual users without an organization administrator can open {site}, choose the support option, and follow the prompts for the affected Microsoft product. Use only the official support path shown there.

Before requesting help, prepare the account email address, organization name if applicable, affected app or service, exact error text, incident identifier, device and browser or app used, and the approximate time the problem began. Explain which networks and devices were tested, whether other users are affected, and which troubleshooting steps were already completed. Never send a password, verification code, or recovery code to a support representative.