Microsoft Teams Bug Prevents Access to Embedded Office Files

Microsoft Teams users worldwide are facing a significant service disruption this Thursday morning, as embedded Microsoft Office documents fail to load within the collaboration platform.

Reports began surfacing at 06:00 UTC, with both enterprise and individual users unable to open Word, Excel, and PowerPoint files directly in Teams channels and chats.

The incident breaks a key feature of Teams, which normally allows seamless in-line co-authoring and real-time collaboration without switching to separate Office apps.

Incident TM1143347 Causes Continuous Loading

Microsoft has officially acknowledged the problem under incident ID TM1143347 on the Microsoft 365 Service Health Dashboard.

Affected users clicking on an embedded document are met with one of the following symptoms:

• A perpetual loading spinner (<div class="loader"></div>) that never resolves.
• An error banner stating “We ran into a problem opening this file. Please try again later.”
• A blank or white screen in the Teams viewer frame.

Diagnostic logs indicate repeated HTTP 500 and 502 responses when Teams attempts to fetch the document rendering service endpoint (https://api.office.com/render/v1).

Preliminary root-cause analysis suggests a misconfiguration in the document processing pipeline within Azure Functions, resulting in failed “GetEmbeddedFile” API calls to SharePoint Online and OneDrive for Business.

In a bulletin posted at 08:15 UTC, Microsoft’s advisory notes:

textIncident TM1143347: Users may be unable to open embedded Office docs in Teams.  
Status: Investigating  
Scope: Global impact on Teams clients (desktop, web, mobile)  

Engineers are currently collecting telemetry from Graph API endpoints and reviewing Azure Application Insights traces to identify the faulty microservice.

Recommendations for IT Administrators

While the engineering team works on a permanent fix, several temporary workarounds can restore document access:

1. Open in Browser
   • Right-click the embedded file and select “Open in Browser” to launch it via Office for the web.
2. Open in Desktop App
   • Use the context menu option “Open in Desktop App”, invoking ms-word:ofe|u|<file-URL> or ms-excel:ofe|u|<file-URL> protocol handlers.
3. Download Local Copy
   • Click “Download”, then open the file from the local drive in Word, Excel, or PowerPoint.
4. Access via SharePoint/OneDrive
   • Navigate to the underlying document library URL (e.g., https://contoso.sharepoint.com/sites/TeamName/Shared Documents) and open files directly.

IT administrators should continuously monitor the Microsoft 365 Service Health Dashboard for updates on TM1143347.

No estimated time of resolution has been provided, but Microsoft has categorized the issue as high priority.

Implementing the above workarounds can help mitigate productivity losses until a full restoration is announced.

Find this Story Interesting! Follow us on LinkedIn and X to Get More Instant Updates