Microsoft confirmed that it restored file access for Microsoft Teams and Office for the web on June 1, 2026, after a service incident (tracked as MO1329446) left users unable to open documents. The outage, which primarily affected Excel for the web and file sharing within Teams, disrupted workflows for an undisclosed number of Microsoft 365 tenants.

The issue first surfaced earlier in the day when users reported that clicking on files in Teams or attempting to open Excel workbooks in a browser resulted in error messages or unresponsive pages. Microsoft quickly acknowledged the problem through its service health dashboard and began investigating the root cause.

A Closer Look at the Incident MO1329446

The incident ID MO1329446 was assigned to a problem affecting the file access layer of Microsoft 365—specifically, the services that handle document previews and editing in Teams and Office for the web. According to Microsoft’s preliminary post-incident review, the core issue stemmed from a configuration change that inadvertently severed connectivity between authentication services and the backend file storage systems.

While Microsoft has not disclosed the full technical details, the scenario is familiar to IT administrators: a routine update or adjustment can cascade into a broader service degradation when dependent APIs fail to handshake properly. In this case, users clicking on a Word, Excel, or PowerPoint document in Teams saw a spinning progress indicator that eventually timed out. In Office for the web, documents refused to load, displaying generic “We’re having trouble opening this file” messages.

The impact was not universal. Microsoft’s telemetry indicated that the problem was concentrated in certain geographical regions and for tenants using specific authentication configurations. Organizations that rely heavily on single sign-on providers or conditional access policies may have been disproportionately affected, though Microsoft has not confirmed this correlation.

Scope and Duration

The incident began at approximately 08:30 UTC on June 1 and was mitigated by 14:15 UTC, meaning the outage lasted just under six hours. For businesses in the Americas, that timeframe disrupted the start of the workday; for European users, it spanned the late morning and early afternoon.

Microsoft classified the incident as a “Service Degradation” rather than a full outage because core Teams communication features (chat, calls, meetings) remained functional. Only file access—opening and editing documents—was impaired. However, for organizations that have embedded document collaboration into their workflow, the degradation was effectively an outage. Workers could not access shared spreadsheets, review reports, or co-author proposals.

The incident’s scope highlights the deep interdependency between Microsoft Teams and the broader Microsoft 365 ecosystem. Teams relies on SharePoint Online and OneDrive for Business to store files, and on Office Online servers to render them. A break anywhere in that chain can render files inaccessible, even if the underlying storage is intact.

Microsoft’s Response and Remediation

Once the issue was escalated, Microsoft’s engineering teams traced the problem to the recent configuration change and initiated a rollback. The rollback gradually restored file access as the change propagated through the service fabric. Microsoft posted regular updates on the Microsoft 365 admin center and via Twitter (@MSFT365Status), informing admins of progress.

By 12:00 UTC, Microsoft reported that they had identified the cause and were deploying the fix. Two hours later, they confirmed that file access was fully restored for most users, with a small residual impact for a subset of tenants that cleared by 14:15 UTC.

The company also issued a preliminary post-incident report (PIR) within 24 hours through the service health dashboard, which provided a high-level root cause analysis. A more detailed final PIR is expected within five business days, as per Microsoft’s standard incident response policy. Admin forums have been abuzz with speculation about whether this incident was related to ongoing updates to the Microsoft 365 authentication stack or a change in the Office Online rendering engine.

What We Can Infer About MO1329446’s Cause

Although Microsoft has not released the full PIR, several clues point to an authentication token issue. During the outage, users were able to see file lists in Teams and SharePoint but could not open files. That pattern suggests that the metadata service was healthy, but the service that issues short-lived access tokens for file rendering failed. This is consistent with a misconfiguration in the token issuing service—perhaps a certificate expiry or a change in the allowed token audience.

If that’s the case, the fix would involve reverting the configuration or renewing the certificate. Microsoft’s statement that a “rollback” resolved the issue supports this theory. Fortunately, rolling back configuration is relatively quick once the change is identified, which explains the 6-hour duration: about 3 hours to diagnose and 3 hours to deploy the fix.

User Impact and Community Reaction

During the outage, users flocked to social media and IT community forums to share their frustration. Many reported that they resorted to downloading files and opening them in desktop applications as a workaround—a viable but inefficient fallback. However, that workaround required the desktop apps to be installed and licensed, and it broke real-time co-authoring.

Administrators on Reddit’s r/sysadmin noted that the incident exposed a vulnerability in cloud-dependent workflows. “We’ve moved everything to Teams and SharePoint; when that breaks, nobody can work,” one user commented. Others criticized Microsoft’s communication pace, claiming that the service health dashboard was slow to update during the first hour.

That said, seasoned IT pros acknowledged that Microsoft’s response matched its typical pattern and that the rollback resolved the issue without requiring tenant-level actions. The biggest takeaway from the community was a renewed emphasis on having fallback options: desktop versions of Office, local file copies for critical documents, and clear communication plans for when outages occur.

Understanding the Incident Management Pipeline

When an issue like MO1329446 is detected, Microsoft follows a multi-tier incident response process. The first line of defense is automated monitoring that catches anomalies in service metrics—such as a spike in 5xx HTTP errors or a drop in successful authentication handshakes. Once an alert fires, a duty engineer assesses the scope and, if necessary, declares a “service incident” that triggers a dedicated incident response team.

This team pulls in engineering owners from relevant service teams: Teams, SharePoint, Office Online, and possibly Azure Active Directory. They work in a “war room” to diagnose and mitigate. The primary goal is always to restore service as quickly as possible, often by rolling back a recent change, even if the exact root cause is not yet fully understood.

Post-restoration, the team conducts a root cause analysis that results in a preliminary PIR within 24 hours and a final PIR within five days. These reports are available in the Service Health Dashboard and, for certain high-severity incidents, may also appear in the Microsoft 365 Admin Center Message Center. Admins are advised to review these reports carefully; they often contain action items for tenant configuration changes that can prevent similar issues.

What This Means for Microsoft 365 Administrators

Even after service is restored, admins have work to do. Here are the steps that forward-thinking IT teams are taking in the aftermath of MO1329446:

1. Review Your Service Health Dashboard Configuration

Ensure that you have configured email alerts for service incidents and that they reach the right people. During MO1329446, notifications from Microsoft were delayed for some tenants, possibly due to misconfigured notification settings. Verify that your admin contacts are up to date in the Microsoft 365 admin center.

2. Dig Into the Incident’s Impact on Your Tenant

Don’t assume your users were unaffected. Use the “Service Health” history in the admin center to see exactly when the issue started and ended for your tenant. Cross-reference that with your own help desk tickets and user reports. If users experienced issues outside the official incident window, document that for your own records—sometimes regional nuances mean impact lasts longer for specific tenants.

3. Leverage PowerShell for Automated Health Checks

Savvy admins can use the Microsoft 365 Service Health API or the MSOnline PowerShell module to programmatically pull incident details. For example, you can schedule a script to query the service health and send alerts to a Teams channel. This ensures that even if the admin center is sluggish, you get the information you need. A quick script snippet:

Connect-ExchangeOnline
$health = Get-ServiceHealth | Where-Object { $_.Service -like "*Teams*" }
$health.Incidents | Format-Table -AutoSize

This method bypasses the UI and can be integrated into your existing monitoring stack.

4. Assess Your Dependency on Web-Only Clients

If your organization relies heavily on Office for the web (for example, to avoid desktop app deployment), incident MO1329446 is a wake-up call. Consider building a plan to fall back to desktop apps when the web services degrade. This might involve pushing out the desktop versions via Microsoft 365 Apps for enterprise and ensuring users know how to open documents from OneDrive locally.

5. Communicate Transparently with Your Users

Send a post-incident summary to your organization. Explain what happened (in plain language), what users experienced, and how they can work around future incidents. This builds trust and reduces help desk calls the next time an outage strikes. Microsoft provides a template in the Message Center; adapt it for your audience.

6. Contribute to Microsoft’s Post-Incident Investigation

If you observed any unusual behavior that wasn’t captured in Microsoft’s reports—such as sporadic permissions errors or affected applications beyond those listed—submit a service request with detailed logs. Microsoft engineering uses this data to refine its risk assessment for future updates.

The Bigger Picture: Cloud Reliability in the Modern Workplace

Incidents like MO1329446 are not unique to Microsoft. All major cloud providers occasionally suffer service disruptions. What matters is how quickly they recover and how transparently they communicate. In this case, Microsoft restored service in less than a day and began sharing root cause details promptly. That’s a solid response by industry standards.

Still, each incident chips away at the trust organizations place in “always-on” cloud services. For Microsoft, the pressure is immense because Teams has become the workplace hub for hundreds of millions of users. A six-hour file access glitch can cost businesses real money in lost productivity.

Microsoft has invested heavily in making its cloud more resilient, employing techniques like safe deployment rings, gradual rollout, and automated rollback triggers. However, no system is foolproof. The fact that a configuration change could knock out file access across regions suggests that even with these safeguards, the interdependencies in the Microsoft 365 service graph are staggeringly complex.

Looking Forward: What Admins Should Watch

In the coming days, admins should look out for the final PIR from Microsoft, which may contain more precise timelines and detailed remediation steps that Microsoft plans to take to prevent recurrence. Often, these reports reveal interesting technical details—like which specific API endpoint failed or what monitoring gap allowed the issue to persist.

Additionally, keep an eye on the Microsoft 365 Roadmap. Post-incident, there’s often a flurry of new features aimed at improving resilience: better offline support for Teams files, more granular service health alerts, or improved diagnostic tools for admins.

Microsoft hasn’t announced any specific changes directly tied to MO1329446 yet, but the incident will likely accelerate ongoing efforts to decouple file access from core Teams communication services. That architectural shift could mean that in the future, a file access hiccup won’t even register for most users because the local cache takes over seamlessly.

Conclusion

The restoration of file access on June 1, 2026, after incident MO1329446 brings relief to Microsoft 365 users and admins alike. But it’s not the end of the story. Now is the time to learn from the disruption: tighten alerting, strengthen fallback plans, and prepare your organization for the next incident—because there will be a next one.

By staying informed and proactive, IT administrators can turn a vendor outage from a catastrophe into a manageable hiccup. And that’s exactly the value that experienced admins bring to the table.