Outlook Outage: What Microsoft 365 Users Should Check Before Resetting Anything

Shared mailboxes and delegated calendars are worth checking separately after access returns. Open the mailbox or calendar that had the problem and confirm the specific action you need, such as opening a folder or seeing an updated invitation. The main inbox loading is only one part of that check.

The Outlook outage that began on 12 November 2026 disrupted access to some Microsoft 365 work and school mailboxes and delayed email delivery. Microsoft’s service updates described problems with Exchange Online and several services that use it. If Outlook opens slowly, fails to load a mailbox or leaves a message pending, check your organisation’s service health before changing your password or reinstalling the app.

The incident covered Outlook on the web, Outlook desktop and other ways of connecting to Exchange Online. The underlying service hosts email and calendar data for many organisations. A problem there can show up on several devices at once even when those devices are working normally. Penn’s published Microsoft incident updates list the Exchange incident as EX1550543 and the broader Microsoft 365 incident as MO1550821.

Check the account and the affected service

Start by identifying the account that is failing. This incident reporting concerns Microsoft 365 services used by organisations. If you have more than one mailbox in Outlook, check which inbox is affected and report that detail to your IT team. An error on a work account alone gives the team a clearer starting point than a general report that Outlook will not open.

Trying Outlook on the web once can help distinguish an isolated desktop problem from a wider symptom. Both routes can depend on the same Exchange Online service. If the mailbox fails in both places and colleagues report similar errors, check the current incident before removing the account, clearing cached mail or repeating a sign-in recovery process. Keep the wording of any error and the time you saw it so IT can compare it with the advisory.

Where to verify whether your organisation is recovering

For administrators, Microsoft’s service health guide explains where to find the tenant dashboard. Look for the affected service and the relevant incident identifier. If the dashboard itself is unavailable, Microsoft’s public service health page can provide a wider service view. Employees and students can also check the notices from their own organisation’s help desk.

Reuters reported that Microsoft was restoring servers and moving traffic as it investigated why infrastructure had become unavailable. Published incident updates described incremental recovery. Use the latest status for your tenant when deciding whether to retry a stalled task. A successful sign-in on one device can occur while another mailbox operation is still slow.

Check mail and calendar actions after reconnecting

If you submitted a message just before the error, open Sent Items and the Outbox when your mailbox returns. Find the original message before pressing Send again. For urgent communication, use a channel your organisation already permits and record the time you sent the original. If a colleague is waiting for an attachment, confirm delivery with them once access is back.

Microsoft’s advisory also distinguished Teams features that depend on Exchange Online from core messaging and meeting functions. A colleague may be reachable in chat while the calendar or a new invitation still fails. Check an existing meeting link before recreating the appointment, and verify the event in your calendar once it loads.

When reporting a continuing issue, include the account type, the app or browser, the action that failed and the time in IST. That gives your help desk enough information to compare your experience with the incident and decide whether your device needs separate troubleshooting. Use the tenant advisory for the most recent recovery status.