Support Engineering Weekly cover art

Support Engineering Weekly

Support Engineering Weekly

By: Support Engineering Blog
Listen for free

This Season's Biggest Deal | $0.99/mo for 3 months + $20 Audible bonus

Auto-renews at $8.99/mo. after 3 months - terms apply.
Summary

Support Engineering Weekly is the podcast from the Support Engineering Blog, featuring technical conversations about Microsoft technologies, support engineering, troubleshooting, administration, architecture, operations, and modernization. Each week, we explore practical engineering challenges, technical decisions, and the deeper considerations behind keeping enterprise technology working.

Visit Support Engineering Blog at https://blog.sadhan.ch/

© 2026 Support Engineering Blog. All rights reserved.
Episodes
  • When Redundancy Fails: Inside Microsoft’s Network Stampede
    Nov 17 2026

    How can a routine network capacity upgrade trigger a global cloud outage — and why can the very systems designed to protect availability make the failure worse?

    In this Support Engineering Weekly bonus episode, Alex and Maya dissect Microsoft's November 2026 disruption through the lens of distributed systems, infrastructure reliability, and incident response.

    The discussion follows the failure chain from a latent bug exposed during a network traffic shift to overloaded secure connection processing, CPU exhaustion, and cascading server failures. It explores how Layer 7 health checks and automated traffic redistribution can unintentionally amplify an outage, why aggressive retries can turn degraded microservices into a self-inflicted traffic storm, and how overloaded infrastructure can even prevent engineers from regaining control of affected systems.

    The episode also examines the recovery challenges: isolating affected infrastructure, carefully reintroducing traffic, applying an upstream configuration fix, and protecting delayed email from being lost while backlogs cleared.

    Most importantly, this incident raises questions that every infrastructure and platform engineering team should consider:

    • Can your health checks distinguish an unhealthy server from an overloaded one?
    • Could your failover mechanisms amplify a failure instead of containing it?
    • Are your retry policies protected by circuit breakers, exponential backoff, and jitter?
    • Can your management plane remain accessible when the data plane is overwhelmed?
    • Does your redundancy strategy account for shared software defects, not just hardware failures?

    Because having more servers does not automatically make a system resilient. True resilience means being able to degrade gracefully, contain failures, and recover without allowing automated safeguards to become part of the problem.

    Listen to this special deep dive from Support Engineering Weekly for practical reliability lessons on load balancing, TLS connection handling, microservices, and designing systems that can survive unexpected failure patterns.

    Chapters

    00:00 - When Redundancy Fails

    02:00 - The First Signs of Failure

    05:00 - Capacity Loss vs. Traffic Spikes

    07:00 - How Health Checks Amplified Failure

    12:00 - The TLS Bottleneck

    16:40 - Retry Storms and Lost Control

    21:00 - Containment and Controlled Recovery

    24:00 - The Hidden Impact Beyond Email

    27:50 - Engineering Lessons for Resilience

    Learn More:

    For the full articles, references, and technical resources, visit the Support Engineering Blog at https://blog.sadhan.ch/.

    Show More Show Less
    33 mins
  • From Microsoft Announcement to Completed Change
    Nov 15 2026

    Microsoft 365 administrators deal with information from several places: the Microsoft 365 Roadmap, Message Center, and Service Health. But knowing where to find an update is only part of the challenge. The real question is: what happens after you read it?

    In this episode of Support Engineering Weekly, Alex and Maya explore why treating a Message Center notification as a completed task is one of the most dangerous operational habits in IT administration. Clicking Mark as read may clear a notification from your inbox, but it does not mean the change has been understood, assessed, implemented, or verified.

    We begin by distinguishing the roles of Microsoft's three information sources: the Roadmap provides visibility into what's coming, Service Health reports current service incidents, and Message Center communicates upcoming changes that may affect your environment. The discussion then focuses on turning Message Center notifications into structured, traceable administrative work.

    The episode also examines why retirement notifications require a different level of attention. Unlike a routine update, a retirement creates a deadline-driven migration requirement. Workload identification, dependency mapping, replacement selection, and migration execution become essential parts of the process.

    A particularly important distinction emerges during the discussion: deployment does not equal completion. A change is only ready to close when its outcome has been validated and the supporting evidence has been retained in a permanent system of record.

    The overall workflow is straightforward:

    Understand. Own. Assess. Validate. Act. Verify. Close.

    Because the goal isn't simply to clear your Message Center notifications. It's to know what changed in your environment, who was responsible, what was done, and whether it actually worked.

    Chapters

    00:00 - The Mark-as-Read Trap

    02:29 - Message Center Intake

    03:42 - Classifying Changes and Urgency

    06:13 - Ownership and Impact Assessment

    10:21 - Testing, Preparation, and Deployment

    13:48 - Validation and Evidence-Based Closure

    18:00 - Why Retirements Need a Different Path

    Learn more:

    The full technical article, references, and supporting resources are available through the Support Engineering Blog at https://blog.sadhan.ch/.

    Show More Show Less
    23 mins
  • Microsoft Weekly — November 09–13, 2026
    Nov 13 2026

    A server under pressure fails its health checks. Automated traffic management removes it from service, pushing even more load onto the remaining infrastructure. What was designed to protect the system becomes part of the failure itself. In this episode of Support Engineering Weekly, Alex and Maya examine the Microsoft 365 incidents reported between November 9 and 13, 2026, starting with a major multi-service disruption affecting Exchange Online, Teams, SharePoint, Copilot, Defender, and Purview. We unpack the engineering mechanisms behind the cascading failure, including overloaded TLS handshakes, automated health checks, the thundering herd effect, and the decision to extend Exchange Online message timeouts to 48 hours to protect delayed email from unnecessary delivery failures.

    Beyond the infrastructure outage, we investigate how distributed-system behaviour creates unexpected problems across Microsoft 365. We explore why Copilot Chat can display outdated conversation history even when the underlying data remains safe, how a latent state-management defect can surface during an infrastructure migration, and why a seemingly minor SMTP header change can trigger duplicate messages and downstream support tickets. We also examine an Exchange Online quarantine failure that raises an important security question: what happens when a system designed to isolate suspicious messages cannot determine where to store them? The discussion then moves to Copilot's integration with Edge for Business, including the interaction between browser-based writing assistance and data loss prevention policies.

    Finally, we look at the connection between front-end behaviour and back-end functionality through two unusual incidents: restored Microsoft Teams appearing invisible to users because of a client-side rendering issue, and Word for the web failing to open its audio-file selection dialog under specific Chromium browser window conditions. Across these incidents, one lesson keeps returning: the visible symptom is not necessarily where the failure begins. For support engineers, administrators, and IT professionals, understanding the dependencies between infrastructure, application state, security controls, and user interfaces is essential to troubleshooting modern cloud services.

    Chapters

    00:00 Introduction: When Recovery Makes It Worse

    01:33 The Cascading Infrastructure Outage

    06:11 Copilot Caching and Hidden State Bugs

    10:14 Copilot in Edge and DLP Boundaries

    11:35 Exchange Routing and Quarantine Failures

    16:18 Teams and Word: Front-End Failures

    20:51 Lessons for Support Engineers

    Learn more:

    Visit the Support Engineering Blog at https://blog.sadhan.ch/ for the full articles, technical references, and additional support-engineering resources behind the discussion.

    Show More Show Less
    23 mins
No reviews yet
In the spirit of reconciliation, Audible acknowledges the Traditional Custodians of country throughout Australia and their connections to land, sea and community. We pay our respect to their elders past and present and extend that respect to all Aboriginal and Torres Strait Islander peoples today.