Skip to content
Artwork for Support Engineering Weekly
Support Engineering Weekly · October 2 · 21 min

Microsoft Weekly — September 28–October 2, 2026

This week on Support Engineering Weekly, Alex and Maya examine a series of Microsoft 365 incidents that reveal a common engineering pattern: as cloud services become more deeply connected, failures increasingly occur in the connective tissue between systems rather than in the systems themselves. The episode begins with Microsoft’s transition from SharePoint One-Time Passcodes to Microsoft Entra B2B for external sharing, and what that means for legacy sharing links, guest identities, Conditional Access, and help-desk preparation. From there, the discussion moves into Teams device-management consolidation, iOS enrollment failures, and a Windows Autopilot routing issue where an internal network change caused seemingly unrelated device-management operations to fail. The deeper dive focuses on Microsoft 365 Copilot, including licensing failures, agent deployment problems, traffic-related capacity issues, and a particularly significant semantic-indexing gap that left Exchange Online email available in storage but absent from Copilot's semantic understanding. The episode then turns to traditional Office clients, examining a Word PDF-save failure that redirected files into a hidden legacy cache location, an Exchange Online add-in synchronization issue, and a Teams workflow regression involving run-only permissions. The common thread is silent and indirect failure: systems can appear healthy while an underlying dependency, routing path, synchronization pipeline, or indexing process is no longer behaving as expected. For support engineers, that raises a difficult question for the AI era: how do you troubleshoot a system that is functioning normally while quietly operating on incomplete information? Chapters 00:00 - Cloud Dependencies Under Stress 01:47 - SharePoint External Access Changes 05:43 - Teams Device Management Consolidation 06:43 - Intune Routing and Autopilot Failure 10:03 - Copilot Licensing and AI Index Gaps 13:02 - Copilot Scale and Agent Failures 14:05 - Office Clients and Cloud Dependencies 16:44 - Exchange Add-ins and Teams Workflows 19:28 - The Enterprise AI Monitoring Challenge 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.

0:00 · Cloud Dependencies Under Stress-21:21

transcript

No transcript — this publisher did not publish one.

show notes

This week on Support Engineering Weekly, Alex and Maya examine a series of Microsoft 365 incidents that reveal a common engineering pattern: as cloud services become more deeply connected, failures increasingly occur in the connective tissue between systems rather than in the systems themselves.

The episode begins with Microsoft’s transition from SharePoint One-Time Passcodes to Microsoft Entra B2B for external sharing, and what that means for legacy sharing links, guest identities, Conditional Access, and help-desk preparation. From there, the discussion moves into Teams device-management consolidation, iOS enrollment failures, and a Windows Autopilot routing issue where an internal network change caused seemingly unrelated device-management operations to fail.

The deeper dive focuses on Microsoft 365 Copilot, including licensing failures, agent deployment problems, traffic-related capacity issues, and a particularly significant semantic-indexing gap that left Exchange Online email available in storage but absent from Copilot's semantic understanding. The episode then turns to traditional Office clients, examining a Word PDF-save failure that redirected files into a hidden legacy cache location, an Exchange Online add-in synchronization issue, and a Teams workflow regression involving run-only permissions.

The common thread is silent and indirect failure: systems can appear healthy while an underlying dependency, routing path, synchronization pipeline, or indexing process is no longer behaving as expected. For support engineers, that raises a difficult question for the AI era: how do you troubleshoot a system that is functioning normally while quietly operating on incomplete information?

Chapters

00:00 - Cloud Dependencies Under Stress

01:47 - SharePoint External Access Changes

05:43 - Teams Device Management Consolidation

06:43 - Intune Routing and Autopilot Failure

10:03 - Copilot Licensing and AI Index Gaps

13:02 - Copilot Scale and Agent Failures

14:05 - Office Clients and Cloud Dependencies

16:44 - Exchange Add-ins and Teams Workflows

19:28 - The Enterprise AI Monitoring Challenge

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.

links1

chapters

9 chapters