Is Microsoft 365 Down? Check Service Status

Check the Current Microsoft 365 Status

Start with Microsoft’s official service-status information. Open {site}, find the Microsoft 365 support area, and look for service health or status. Check the time of the latest update so you do not mistake an older incident for a current problem.

An active incident may identify the affected service, reported symptoms, impact, and progress toward recovery. Microsoft may also label an item as an advisory when service still works but some users experience errors or reduced performance. Read the incident details carefully because Microsoft 365 includes separate services such as Exchange Online, Outlook, Teams, OneDrive, and SharePoint.

Do not assume Microsoft 365 is down merely because a third-party outage tracker shows a spike in reports. Those reports can reveal a pattern, but official service-health information is the better source for confirmation. If no public incident appears, continue with the checks below.

Is Microsoft 365 Down for Everyone?

To answer “is M365 down,” first find out how broad the problem is. Ask a coworker in the same organization whether the same feature fails. If possible, also check whether a different Microsoft 365 service works.

• If many users and several locations have the same symptoms, a widespread or organization-wide incident is more likely.
• If only one account is affected, the cause may be an account, license, security, or organization setting.
• If the service works on another device, the original browser, application, or device may be the issue.
• If it works on another network, the local internet connection, firewall, virtual private network, or filtering service may be involved.
• If the web version works but a desktop or mobile application does not, the installed application may have a connection or update problem.

Try a private browser window, then sign in normally without changing account settings. You can also switch between Wi-Fi and cellular data if both are available. A work-managed device may block that test, so follow your organization’s security rules.

Record the affected service, exact error text, time, device, network, and whether coworkers see the same issue. This makes it easier for an administrator or support agent to identify the scope.

Microsoft 365 Email Outage

An M365 email outage usually involves Exchange Online or Outlook. Possible signs include messages remaining in the outbox, delayed incoming or outgoing mail, repeated password prompts, a mailbox that will not load, sign-in failures, or connection and synchronization errors.

First, check whether you can open the mailbox in a browser. If browser email works but an installed mail application does not, the mailbox service may still be available. Check the application’s connection state and restart it once. Do not remove the account or create a new mail profile during a possible outage.

Send one small test message to a trusted recipient and note when it was sent. Avoid sending the same message repeatedly, because delayed copies may all arrive after service recovers. Check the outbox, drafts, sent folder, junk folder, and any delivery-failure notice. A message in the sent folder does not always prove that the recipient has received it.

If login fails, verify that you selected the correct work, school, or personal account. Do not repeatedly reset a password when other users report the same failure. Too many attempts can add an account lockout to the original problem.

What to Do During an M365 Outage

Use low-risk checks while you wait for confirmation or recovery:

1. Save open documents locally if your organization permits it. Give temporary copies clear names so they can be reviewed later.
2. Take a screenshot of the error and note the time, affected account, application, and action that failed.
3. Refresh the page once or restart the affected application once. Repeated retries can create duplicate messages or conflicting document copies.
4. Try the browser version or another approved device without changing security settings.
5. Check official updates and follow instructions from your organization’s administrator or help desk.
6. After recovery, confirm that mail has synchronized and that queued messages were sent before trying them again.

Do not delete mail, clear application data, remove a mailbox, rebuild a profile, uninstall software, or reset the device while an outage is suspected. Those actions can remove locally stored information or make recovery harder. Do not weaken multifactor authentication, firewall protection, or other security controls to restore access.

If work is urgent, use an alternative communication method approved by your organization. Never move confidential information into a personal account or an unapproved service.

Check Service Health as an Administrator

An authorized administrator can sign in through {site} and open the Microsoft 365 admin center. In the health area, review service health for active incidents and advisories. The dashboard can show affected services, user impact, current status, incident identifiers, update history, and recovery information available to that organization.

Open the relevant item and compare its stated symptoms with user reports. Note which users, regions, clients, or features appear affected. Review the latest update time and any recommended administrator action. Some information may be visible only after an authorized administrator signs in.

Administrators should also check message-center notices and their organization’s own monitoring, identity service, network, and recent configuration changes. Preserve error logs and incident identifiers. Avoid broad configuration changes unless evidence points to a local cause.

Contact Microsoft 365 Support

If no matching incident appears, an administrator can use the support option inside the Microsoft 365 admin center. Individual users should usually contact their organization’s help desk or Microsoft support through the official support area. Only an authorized administrator may be able to view organization-specific service health or open certain requests.

Prepare the tenant or organization name, affected service, number of affected users, first observed time with time zone, incident identifier if shown, exact error messages, and steps already tested. Include device type, operating system, browser or application version, network type, and whether the problem occurs in the browser and installed application.

Share screenshots only after hiding private mail, security codes, and personal information. Never send a password, verification code, recovery key, or full payment details. Keep the support case reference and add new symptoms or official incident updates to the same case instead of opening duplicates.