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
  • Planner Premium Isn't Project Online — So What Is the Gap?
    Nov 8 2026

    Microsoft Project Online is approaching retirement - or, in this case, its retirement date has already passed. But replacing a project management platform is not as simple as moving tasks from one product to another.

    In this episode of Support Engineering Weekly, Alex and Maya examine the architectural differences between Project Online and Planner Premium, and why treating Planner Premium as a one-to-one replacement can put important business processes at risk.

    We begin by separating project execution from enterprise project and portfolio management. Planner Premium is well suited to structured collaborative execution, including task dependencies, milestones, timelines, and critical paths. But enterprise workloads may also depend on resource capacity planning, complex timesheets, financial forecasting, and cross-project management capabilities that require a different approach.

    The discussion explores Planner Premium’s technical boundaries, including task, resource, custom field, successor link, and project duration limits. We then examine the illusion of equivalence: why workload visibility is not the same as enterprise resource management, and why portfolio views do not automatically unify every project management system.

    From there, we look at the hidden dependencies that make migrations difficult: Power Automate flows, custom Power Apps, APIs, reporting, financial systems, governance, and the need to establish an authoritative plan of record.

    Alex and Maya then walk through a fit-gap assessment approach, from identifying the business capabilities teams actually use to classifying requirements, validating dependencies, selecting the right destination, and testing complex workloads in a pilot.

    Finally, we explore how different workloads may need different destinations—including Planner Basic, Planner Premium, Project Server, Dynamics 365 Project Operations, Project desktop, or archival for inactive projects.

    The central lesson: Don't replace the product. Replace the capability.

    Disclaimer: This episode discusses the Microsoft Project Online retirement date of September 30, 2026, which has already passed. The episode is being published after that date because an earlier publication slot was not available. The discussion reflects the retirement timeline referenced during the original recording.

    Chapters

    00:00 — The Retirement Deadline and the Assumption

    02:01 — Project Execution vs. Enterprise PPM

    04:35 — Planner Premium's Technical Boundaries

    07:44 — Visibility vs. Resource Management

    11:29 — Dependencies, Governance, and Migration Risk

    17:12 — Routing Workloads to the Right Platform

    20:01 — Archive What No Longer Needs a Home

    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
    21 mins
  • Microsoft Weekly — November 2–6, 2026
    Nov 6 2026

    Microsoft 365’s latest updates are reshaping how users communicate and collaborate—but beneath the cleaner interfaces, this week’s incidents reveal just how fragile cloud routing and data pipelines can be. Alex and Maya examine changes across Microsoft Teams, Teams Rooms, and Viva Engage, including minimized meeting controls, new chat sections, private event chat, and dynamic audiences.

    Then, they connect the user-facing symptoms to the infrastructure behind them: Exchange Online quarantine failures caused by a missing tenant identifier, duplicate emails triggered by abnormal SMTP headers, Copilot chat histories that appeared to vanish because of regional synchronization issues, and Copilot Cowork traffic throttled by an internal API loop. They also explore delayed usage reports, stale Copilot health data, and Microsoft Purview audit-log backlogs—and why reporting delays do not necessarily mean data loss.

    The episode closes with three practical lessons for support engineers: communicate UI changes before users are surprised by them, understand the fragility of backend routing and automated defenses, and distinguish telemetry pipeline problems from service or data loss. As Microsoft 365 services become more interconnected, dependency mapping and blast-radius analysis will matter more than ever.

    This episode is based on the Microsoft Message Center and Service Health updates covered for November 2–6, 2026.

    Chapters

    00:00 Introduction: When Cloud Services Break

    02:38 Microsoft 365 Collaboration Changes

    08:18 Exchange Quarantine and Secure Failure

    10:10 SMTP Forwarding and Duplicate Emails

    12:05 Copilot Routing and API Loops

    16:30 Telemetry Pipelines and Admin Visibility

    20:30 Three 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
    24 mins
  • Planner Premium: When Task Management Becomes Project Management
    Nov 1 2026

    When does a simple task list stop being enough to manage a project?

    A team can coordinate everyday work perfectly well with a basic task board. But when activities become interconnected, dependencies start affecting delivery dates, and leadership needs visibility into project risks, tracking individual tasks is no longer enough.

    In this episode of Support Engineering Weekly, Alex and Maya explore how Microsoft Planner Premium moves work management beyond basic task coordination into structured project delivery.

    The discussion begins with the four-stage Work Management Journey, from individual tasks and team coordination to structured projects and enterprise portfolio management. We examine the differences between Planner Basic and Planner Premium and explain why project complexity is driven by relationships between tasks rather than simply the number of items on a board.

    From there, we explore dependencies, milestones, timeline views, and critical path analysis. We look at how these capabilities help project managers understand cascading delays, identify delivery bottlenecks, and manage the actual constraints of a project rather than simply tracking incomplete tasks.

    The conversation then turns to licensing. Using a practical implementation example, Alex and Maya explain why organizations should assign licenses according to individual responsibilities rather than automatically licensing every project participant for premium capabilities. The discussion also examines how separating task execution from strategic schedule management can support better project governance.

    We then address the retirement of Project Online and what it means for organizations planning their next work management platform. Planner Premium is not an automatic replacement for every Project Online workload. We explore the enterprise decision framework and the different paths involving Planner Premium, Project Server Subscription Edition, and Dynamics 365 Project Operations.

    The episode also examines the four-stage adoption approach: assess, pilot, govern, and scale. We discuss why successful adoption requires measurable behavioral evidence, why the organization must provide the project management method, and how administrators can evaluate whether teams are genuinely using structured planning capabilities.

    Finally, Alex and Maya explore the evolving AI experiences in Planner, distinguishing Planner Agent from Copilot in Planner. We examine how AI can accelerate project creation and reporting while also introducing the risk of generating poorly governed plans at greater speed.

    The central lesson is simple: Planner provides the mechanics, but the organization must provide the method. Technology can make structured project delivery possible, but human governance, accountability, and sound project practices remain essential.

    Chapters

    00:00 — When Task Lists Stop Being Enough

    02:15 — From Tasks to Structured Projects

    05:53 — Dependencies and Critical Path

    09:11 — Premium Licensing by Role

    13:00 — Project Online Retirement and Migration Paths

    18:00 — Adoption, Governance, and AI in Planner

    22:26 — Choosing the Right Work Management Model

    Learn more

    The full technical article, references, and supporting resources are available through the Support Engineering Blog.

    Show More Show Less
    25 mins
  • Microsoft Weekly — October 26–30, 2026
    Oct 30 2026

    This week on Support Engineering Weekly, Alex and Maya explore the growing tension between rapid AI innovation and the reliability of the infrastructure supporting it. Microsoft is expanding Copilot capabilities with features such as bilingual consecutive interpretation, while introducing new consumption reporting and billing alerts. But behind these advances, administrators are encountering failures in SharePoint knowledge agents, Copilot file pickers, chat history, and agent experiences. We examine how missing configuration parameters, legacy authentication fallbacks, distributed cache synchronization, and incorrect URL routing can disrupt even the newest AI-powered services.

    We then investigate a less visible but equally important challenge: the reliability of Microsoft's reporting and telemetry pipelines. Delayed Microsoft 365 usage reports, stale Copilot health data, and missing Defender for Servers baseline visibility demonstrate why a reporting failure should not automatically be mistaken for data loss. Alex and Maya explain how ETL processing, schema mismatches, infrastructure migrations, and growing backlogs can disconnect dashboards from otherwise healthy services. We also examine mandatory infrastructure changes, including the retirement of Microsoft Defender Advanced Hunting APIs in favor of Microsoft Graph Security API, and the transition of Teams Android device management into the Teams Rooms Pro Management portal.

    Finally, we look at how shared dependencies create unexpected user-facing failures. From stalled cross-tenant migrations to Outlook attachment problems caused by an Edge WebView update, blank contact cards, and Teams interface regressions, this week's incidents demonstrate how a change in one component can have consequences across an entire ecosystem. We close with three practical engineering lessons: reassess the blast radius of shared dependencies, treat API migrations as active engineering projects, and distinguish data-storage failures from reporting-pipeline problems. As AI agents become part of critical business workflows, we also consider how troubleshooting itself may need to evolve.

    This episode is based on the Microsoft Message Center and Service Health updates covered for October 26–30, 2026.

    Chapters

    02:04 - Copilot Innovation and Reliability

    08:01 - Reporting Pipelines and Telemetry

    11:53 - API Retirements and Migrations

    15:14 - Migration Infrastructure Failures

    16:18 - The Hidden Blast Radius of UI Bugs

    20:19 - Engineering Lessons for Cloud Support

    21:45 - The Future of AI Troubleshooting

    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
  • Apps, Workflows, or AI Agents? Choosing the Right Tool
    Oct 25 2026

    In this episode of Support Engineering Weekly, Alex and Maya examine the architectural differences between human interaction, deterministic execution, and adaptive reasoning. Rather than starting with a technology choice, the discussion starts with the nature of the work and asks which execution model best fits it.

    The episode begins with Power Apps and the role of applications in providing structured human experiences. It then moves into Power Automate and deterministic workflows, where triggers, rules, actions, expected outcomes, and auditability can be explicitly defined.

    The discussion then explores AI agents and the situations where reasoning, ambiguity, unstructured information, multiple knowledge sources, and dynamic tool selection make agentic execution useful. Alex and Maya examine why an agent should not simply replace a deterministic workflow and why bounded tools, permissions, escalation paths, and observability matter when agents can take action.

    The conversation then moves beyond the idea of choosing a single tool. Power Apps, Dataverse, Power Automate, AI agents, enterprise systems, and human decisions can be composed into a governed architecture, with each execution model responsible for the work it is best suited to perform.

    Finally, the episode examines business data, governance, security, ALM, monitoring, licensing, AI capacity, and human-review costs.

    The central lesson is simple: applications, workflows, and AI agents are not competing replacements for one another. They are different execution models that can coexist when architecture starts with the work.

    Chapters

    00:00 — Choosing the Right Execution Model

    05:09 — Apps for Human Interaction

    07:00 — Workflows for Deterministic Execution

    10:22 — Agents for Reasoning and Ambiguity

    14:50 — Composed and Governed Architecture

    19:00 — Data, Governance, and Total Cost

    22:44 — The Architecture Rule

    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
    25 mins