Microsoft admits some emails bounced during Outlook service outage

📅 2026-11-22

Abstract:

Microsoft admitted that during the global Outlook service outage that occurred on November 12, some emails sent to consumer mailboxes failed to be delivered, and senders received bounce notifications. Microsoft also disclosed that the failure also affected a number of email security features and announced a series of improvements to prevent similar incidents from happening again.

This large-scale failure caused millions of users around the world to be unable to access Outlook, Exchange Online, and multiple Microsoft 365 services. The services were restored after about 12 hours. A preliminary incident report previously released by Microsoft stated that the fault originated from a software defect introduced in July 2026; the defect combined with a decrease in server capacity and an increase in Microsoft Teams traffic eventually triggered a cascading failure, which at one time caused more than 80% of Microsoft's network gateway servers to become unresponsive.

During the outage, Exchange Online was unable to process emails normally, and a large number of emails were backlogged waiting for delivery. Microsoft has extended the email delivery retry window from 24 hours to 48 hours to avoid delayed emails being bounced back to the sender. Microsoft confirmed that all corporate emails queued for delivery were eventually delivered, and no corporate emails were found to be permanently lost.

Things are different for consumer users, however. Microsoft acknowledged that some delayed emails sent to consumer mailboxes that have been inactive for more than 30 days have expired, and senders have received non-delivery reports as a result. Microsoft did not release the specific number of affected emails, nor did it say how many users received bounce notifications.

Microsoft's final incident report also disclosed that the outage affected many important email security capabilities in Microsoft Defender for Office. Among them, the zero-hour automatic cleaning function is delayed due to the inability to obtain the latest threat intelligence; this function usually automatically removes malicious emails after they are delivered, so the affected emails may not be cleared in time as usual.

Microsoft also confirmed that users are experiencing issues opening URLs protected by Safe Links. Depending on your organization's security policies, some users may see the "Skip verification" option when Safe Links attempts to verify a URL.

Security managers are also affected and have difficulty releasing or deleting quarantined messages, managing allow and block lists, and performing message repair operations. The impact also extends to Microsoft Purview, where policy changes, security alerts and processing activities may be delayed, involving functions such as data loss prevention, electronic data display, internal risk management and audit search.

To prevent a recurrence of similar failures, Microsoft plans to adjust the traffic distribution design and limit Teams failover to the affected area by the fourth quarter of 2026. By the first quarter of 2027, Microsoft plans to divide network gateway capacity into different resource pools according to different workloads to prevent problems with one service from affecting other services.

Microsoft also plans to expand the scope of load testing and use traffic patterns closer to production environments for testing on its latest high-core servers. Other improvements include establishing faster recovery processes for widespread server failures, improving the ability to diagnose Windows changes, increasing server capacity, narrowing the scope of regional failures, and preventing recovering servers from being overwhelmed by traffic surges again.

Microsoft also admitted that the first customer notification was sent out about 20 minutes after the widespread impact began. The company plans to improve the automatic failure notification mechanism by the end of 2026 to communicate with users in a more timely manner when similar events occur.

Related tags

Related articles

Comments

0/500
Captcha (click to refresh)
No comments yet