Microsoft Weekly — September 7–11, 2026

This week on Support Engineering Weekly, Alex and Maya examine a set of Microsoft 365 incidents and updates that reveal just how deeply connected modern cloud services really are. A shared access configuration created a cross-service blast radius, while telemetry failures produced misleading reporting and downstream service behavior that turned incomplete data into real operational impact. The discussion then moves into several targeted regressions across Outlook and Microsoft Teams, including unwanted Outlook add-ins, malformed shared-channel links, and failures affecting run-only workflows. The episode also looks at two very different forms of intentional disruption: an internal Microsoft resiliency drill that affected Copilot Chat suggestion pills, and TLS interception by network infrastructure that can make a customer-side security appliance look like a Microsoft cloud outage. The episode closes with two Message Center updates administrators should prepare for: more granular Microsoft 365 Copilot usage exports and the upcoming Rewrite with Copilot feature in Edge for Business. Together, these changes highlight a broader support-engineering lesson: authentication, telemetry, network controls, and data-governance policies can all determine how cloud services behave at the user interface. This episode is based on the Microsoft Message Center and Service Health updates for September 7–11, 2026, together with the supporting technical source material used for the episode. Chapters 00:00 - Hidden Microsoft 365 Dependencies 02:03 - When the Access Layer Fails 05:37 - Telemetry Failures and Bad Data 11:04 - Outlook and Teams Code Regressions 15:17 - Copilot Drills and TLS Interception 18:26 - Copilot Analytics and Edge Rewrite 22:25 - Three Key Support Engineering Lessons 23:43 - Resilience in AI-Driven Interfaces Learn more: The full technical source material, references, and supporting information are available through the Support Engineering Blog at https://blog.sadhan.ch.