My Service Support

O365 Outage and Service Status

Updated 2026-08-17 · 940 words

Be the first to rate this page

How to Check the O365 Status Page

For official service-health information, open {site} and look for Microsoft 365 service health or Service status. Microsoft now uses the Microsoft 365 name for services that many people still call Office 365 or O365.

If you are a work or school user, your organization’s Microsoft 365 administrator can check the detailed Service health area in the admin center. That view may show incidents and advisories affecting your organization. If you are not an administrator, ask your IT team whether it has received a service-health notice.

On the O365 status page, look for:

  • An incident or advisory posted for the service you cannot use.
  • A recent start time and update time.
  • A description matching the problem you are seeing.
  • A statement about affected users, regions, features, or organizations.
  • A notice that Microsoft is investigating, applying a fix, or monitoring recovery.

Do not assume there is an O365 outage just because one sign-in attempt fails. An official notice, reports from multiple users, or failures across separate networks provide stronger evidence.

Is O365 Down or Is It a Local Issue?

When asking “is O365 down,” first identify the scope of the problem. A widespread incident often affects several people at about the same time and may appear in the official O365 service status information. A local issue may affect only one account, browser, device, network, or organization.

Use these quick checks:

  1. Ask a coworker whether the same service is failing for them.
  2. Check whether another Microsoft 365 service opens normally.
  3. Try a private browser window or a different supported browser.
  4. If permitted, switch between Wi-Fi and a mobile connection.
  5. Try another device without changing the account password.
  6. Check for messages from your organization’s IT team.

If one browser fails but another works, clear the affected browser’s Microsoft sign-in cookies and restart it. If one device fails, restart the device and confirm its date and time are correct. If only your account is affected, contact your administrator. Security rules, account locks, expired sessions, or license changes can resemble an outage without being systemwide.

O365 Email Outage Checks

An O365 email outage may involve Exchange Online or Outlook. Common signs include messages that remain in the Outbox, delayed incoming mail, repeated connection prompts, folders that stop syncing, or an online mailbox that will not open.

Check whether the problem affects sending, receiving, syncing, mailbox access, or all four. Send one short test message to a trusted coworker and note the time. Do not send the same message repeatedly, because several copies may be delivered when service resumes.

Compare the browser mailbox with the desktop or mobile app. If the browser works but an app does not, the problem may be an expired session, an app update, a damaged local cache, or a device connection issue. If neither works for several users and the official notice mentions Exchange Online or Outlook, an O365 email outage is more likely.

Also check the Outbox, storage warnings, offline mode, and the device’s internet connection. A single oversized attachment or mailbox rule can affect one message without indicating an O365 outage.

How to Read O365 Outage Updates

Microsoft’s updates usually identify the affected service, the user impact, the current investigation stage, and the time of the latest update. Read the impact description carefully. An incident affecting calendar access, for example, does not necessarily explain a sign-in failure.

  • Investigating: Microsoft is gathering information and identifying the cause.
  • Identified: The likely cause or affected component has been found.
  • Mitigating or applying a fix: Work is underway to reduce the impact.
  • Monitoring: Service is recovering, but Microsoft is checking whether the improvement continues.
  • Resolved or service restored: Microsoft reports that the incident is over, though individual apps may still need to reconnect or sync.

Compare the posted timestamps with the time your trouble began. Note whether times are shown in your local zone or another zone. Later updates can narrow or expand the affected users. Treat any next-update time as a communication target, not a guaranteed restoration time.

What to Do During an O365 Outage

During a confirmed O365 outage, avoid changes that may create a second problem. Do not repeatedly reset your password, remove the account from every device, or reinstall applications unless your administrator directs you to do so.

  1. Save open work locally if your organization permits it.
  2. Record the error message, affected service, and approximate start time.
  3. Check administrator notices and the current O365 outage status.
  4. Tell your IT team if your symptoms differ from the official description.
  5. Use an approved alternative communication method for urgent work.
  6. Retry at reasonable intervals instead of refreshing continuously.

Follow your organization’s security and data-handling rules. Do not move confidential files or conversations to a personal account merely because the normal service is unavailable.

What to Do After Service Is Restored

After the O365 service status changes to restored or resolved, close stale browser tabs and start a new session. Sign in once with your usual account. If sign-in succeeds, open the affected service and confirm that its main features work.

For email, check the Outbox, Sent folder, Inbox, and folder synchronization. Queued messages may send automatically, so review them before sending replacements. Allow desktop and mobile apps time to reconnect and download changes.

If an app remains stuck, restart it and then restart the device. Update the app through your organization’s approved process if needed. If the browser works but the app still fails, report that difference to IT. Include the error text and the time service was restored. A continuing problem on one account or device after the wider incident ends may need separate troubleshooting.

Was this page helpful?

Be the first to rate this page