Quick answer: Check Microsoft's live service status before changing Outlook or Teams. During the November 12-14 Microsoft 365 disruption, email and Exchange-dependent features were affected. At our latest check, Microsoft reported sustained recovery while monitoring the email backlog. Preserve drafts, confirm urgent messages by an approved alternative channel, and use an existing Teams meeting link if the calendar will not load.
Last checked: 14 November 2026, 8:41 am AEST / 13 November, 22:41 UTC. This is a dated incident guide, not a live status feed. Use Microsoft's status page for changes after that time.
Is Outlook still down after the November Microsoft outage?
The widespread outage began on November 12 UTC, reaching November 13 in Australia. Microsoft initially tracked Exchange Online mailbox access under EX1550543 and confirmed that users in any region could be affected.
At our check, Microsoft's public page still showed Service degradation. Its update, dated 13 November at 22:00:36 UTC, reported sustained service recovery and continued monitoring of queued email before closure. Recovery was progressing; that was not confirmation that every mailbox or delayed message had recovered.
Microsoft described these affected workflows:
- Outlook and Exchange Online: mailbox access through the browser, desktop, and mobile connections, plus delayed email delivery.
- Teams: calendar, scheduling, invitations, and other Exchange-dependent features. Microsoft said most core calls, meeting joins, group chats, and channel messages remained functional.
- Other Microsoft 365 features: some Copilot, admin, protected-content, and sharing workflows. Access to files stored directly in SharePoint remained functional according to the notice.
This guide focuses on work and school Microsoft 365 accounts. For a personal Outlook.com, Hotmail, or Live account, check the separate consumer-product status on Microsoft's page rather than assuming the business incident explains your problem.
Need to send an urgent email now?
- Keep the draft and attachments. Save important text in an approved local document if needed. Preserve the queued original while you establish whether it was delivered.
- Check Sent Items and Outbox for the correct account. A Sent Items entry alone does not establish that the recipient received it. Confirm a deadline-sensitive message by phone or another approved channel before resending.
- Compare the same account in Outlook on the web once. Use your organization's usual sign-in page. If webmail works, it may let you continue; it can fail during the same Exchange incident, so it is not a guaranteed workaround.
- Tell the recipient about the delay through an approved alternative. Ask IT which route to use for confidential documents. Keep work mail and attachments within your organization's approved systems.
Repeatedly sending the same message can create duplicates as service recovers. If a message bounces, retain its error code and time privately for IT; a rejection needs different follow-up from a message still queued for delivery.
Teams calendar missing, but a meeting is starting?
Try the existing join link in a saved invitation or meeting chat. Microsoft's join-by-link instructions support joining through the browser or desktop app. A working link may let you join while the calendar is unavailable; access rules and other faults can still prevent it.
If you cannot retrieve the invitation, ask the organizer through an approved channel for the existing link or dial-in details, if available. Keep meeting links and passcodes private. Creating another calendar invitation may depend on the same affected service.
Should I reinstall Outlook, clear Teams, or reset my password?
Check the service incident first. Reinstalling an app or deleting an Outlook profile cannot restore Microsoft's backend service and can add recovery work. Preserve unsynced content before considering any reset. Use account recovery only when there is separate evidence of an account problem.
In classic Outlook, Send/Receive > Work Offline should be off when you intend to reconnect. New Outlook and webmail have different controls. A local offline setting and a Microsoft outage can coexist.
Outlook still not working when service recovers
Compare the same account in webmail and the desktop app, then retry the original task:
- Webmail and desktop both fail: ask IT to check the tenant's service health, mailbox, and account. Admins can use Health > Service health in the Microsoft 365 admin center; the public status page is a fallback if the portal cannot load.
- Webmail works but the desktop shows Disconnected: follow the Outlook connection checks.
- A message remains queued: use the Outlook Outbox guide, preserving the message and checking delivery before another send.
- Outlook will not open at all: use the Outlook startup guide.
For an agreed test message, verify receipt as well as Sent Items. For meetings, verify that you can join the intended meeting. A green status page or an app opening does not by itself prove that your original task is working again.
Get help with a remaining local Outlook problem
Againly can help investigate local evidence and propose a plan for review. Microsoft service recovery, email queues, tenant settings, and account permissions remain with Microsoft or your administrator. During a confirmed service outage, use the status and continuity steps above first.
Diagnose my remaining Outlook problem
Sources and status checks
- Microsoft live service health status
- Microsoft's regional-scope confirmation for EX1550543
- How to check your organization's Microsoft 365 service health
- Microsoft: cannot send or receive messages in Outlook
- Microsoft: join a Teams meeting
- Associated Press: outage began November 12