{"id":119389,"date":"2025-10-30T14:38:32","date_gmt":"2025-10-30T14:38:32","guid":{"rendered":"https:\/\/www.sperrysoftware.com\/Email-Tools\/?p=119389"},"modified":"2026-03-30T15:28:04","modified_gmt":"2026-03-30T15:28:04","slug":"microsoft-azure-outage-what-happened-why-safeguard-send-was-affected-and-what-were-doing-about-it","status":"publish","type":"post","link":"https:\/\/www.sperrysoftware.com\/Email-Tools\/microsoft-azure-outage-what-happened-why-safeguard-send-was-affected-and-what-were-doing-about-it\/","title":{"rendered":"Microsoft Azure Outage: What Happened, Why Safeguard Send Was Affected, and What We’re Doing About It"},"content":{"rendered":"
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n

On October 29, 2025, Microsoft experienced a significant global outage that affected millions of users and businesses worldwide. For eight hours\u2014from approximately 12:00 PM ET to 8:00 PM ET\u2014core Microsoft services, including Microsoft 365, Azure, Xbox Live, and Minecraft, were largely unavailable. As a developer of Outlook add-ins that depend on Azure infrastructure, Sperry Software’s\u00a0Safeguard Send for Microsoft 365<\/strong>\u00a0was also temporarily impacted. Here’s what happened, why it mattered, and how we’re responding.<\/p>\n<\/div>\n

\n

The Root Cause: A Configuration Error at Azure Front Door<\/strong><\/h2>\n

The outage was triggered by an inadvertent configuration change in\u00a0Azure Front Door (AFD)<\/strong>, Microsoft’s global content delivery and traffic routing service. Azure Front Door sits in front of hundreds of Microsoft services\u2014think of it as a massive traffic director that routes requests to the right destination at lightning speed.\u200b<\/p>\n

The faulty configuration caused Azure Front Door nodes across the global infrastructure to fail to load properly. As traffic was rerouted to remaining healthy nodes, those surviving nodes became overwhelmed by the sudden surge. This cascading failure created a domino effect: Microsoft 365 authentication systems went down, which in turn caused Outlook to fail, which prevented on-send add-ins like Safeguard Send from operating.\u200b<\/p>\n

The worst part was that the Azure Portal\u2014Microsoft’s primary tool for diagnosing and responding to infrastructure problems\u2014was itself inaccessible because it also depends on Azure Front Door. Microsoft engineers had to work around this “bootstrap problem” by temporarily routing the portal away from AFD, buying themselves time to identify and roll back the problematic configuration.\u200b<\/p>\n

Why Safeguard Send and Other Outlook Add-Ins Were Affected<\/strong><\/h2>\n

When the outage occurred, users of Safeguard Send and other on-send add-ins began experiencing issues. Here’s the technical reason why:<\/p>\n

Outlook add-ins like Safeguard Send are cloud-hosted services that live in Azure. When users enable an on-send add-in, Outlook maintains a connection to retrieve the add-in code from Azure infrastructure. During the outage, Outlook couldn’t reach these Azure-hosted services, so the add-in became unreachable.\u200b<\/p>\n

By default, Outlook has a security-first design: if an on-send add-in cannot be reached, Outlook blocks email from sending. This is intentional\u2014it prevents users from accidentally bypassing security or compliance controls because the add-in is unavailable. As a result, users saw the message “Safeguard Send is working on your request” in perpetuity, with Outlook spinning in a wait loop.\u200b<\/p>\n

Importantly, this affected all on-send add-ins<\/strong>, not just Safeguard Send\u2014including add-ins from Microsoft itself and hundreds of independent developers.\u200b<\/p>\n

Users without add-ins installed were unaffected and could send emails normally.\u200b<\/p>\n

What We Learned and What’s Next<\/strong><\/h2>\n

1. We’re Attending the Microsoft Office Developers Meeting<\/strong><\/p>\n

On November 8, 2025, the Microsoft Office Developers community will hold their monthly meeting to discuss the outage with hundreds of add-in developers from around the world. We will participate and learn about potential improvements for future resilience.<\/p>\n

[Nov 13, 2025 Update: Insights from the Microsoft Office Developers Meeting<\/strong><\/p>\n

At the November 8 Microsoft Office Developers meeting, dozens of frustrated add-in developers representing tens of thousands of affected users shared their experiences. The feedback was clear: the Azure Front Door outage had a cascading impact far beyond what Microsoft’s initial messaging suggested. Developers reported that even add-ins hosted outside Azure (on AWS and other providers) failed to load because core dependencies like Office.js were unreachable due to the AFD outage. Most concerning was the timeline: while Microsoft began posting status updates at 17:27 CET (5:27 PM), the outage had actually started at 09:27 AM CET (9:27 AM)\u2014meaning users were without communication or guidance for over 8 hours.<\/p>\n

The Microsoft Outlook specialist acknowledged the problem and confirmed the team is working on a long-term solution. Notably, even alternative technologies like Safeguard Send Core<\/a> (which uses Smart Alerts designed to allow email sending if the add-in is unreachable) were also blocked during the outage, indicating the issue was at the platform level, not specific to any particular add-in architecture. One practical workaround discovered by an IT Admin was composing emails on desktop, saving them to Drafts, then sending via mobile\u2014a hassle, but it worked. We’re adding this mobile workaround to our dashboard emergency response guidance going forward.]<\/p>\n

\n

2. We Recommend Configuring Outlook’s Default Send Behavior<\/strong><\/h2>\n<\/div>\n

To help protect your organization against future outages affecting on-send add-ins, we strongly recommend reviewing our article on\u00a0How to Change the Default Send Behavior of Outlook When Using Safeguard Send for Microsoft 365<\/span><\/a>.<\/p>\n

By changing a simple registry key, you can configure Outlook to allow emails to send even if Safeguard Send cannot be reached. This means:<\/p>\n