Microsoft Teams File Outage Resolved, but IT Teams Still Need to Check Fallbacks

A Microsoft Teams file outage on June 1 has been resolved, but IT teams still have cleanup work to do. The incident blocked some users from opening files in Teams and Office for the web, disrupting access to documents used across Microsoft 365 workflows.

Microsoft later said service was restored, but had not publicly explained the root cause as of June 2, according to a Microsoft advisory. Administrators should confirm tenant impact, document the outage window, and test fallback paths for critical files.

What Microsoft confirmed

The incident was logged under Microsoft 365 admin center reference MO1329446. Microsoft investigated file-access failures in Office for the web and Teams, with affected apps including Excel for the web and PowerPoint for the web, reported by BleepingComputer.

Impacted users saw the error: “Office Online services aren’t available right now. We’re working to restore all services as soon as possible,” according to the same advisory. Microsoft did not specify affected regions or tenant scope. Its initial analysis pointed to “a potential cross-service issue impacting Office for the web experiences,” without naming what failed.

Microsoft marked the issue resolved at about 1:36 p.m. EDT June 1. The company said it recovered without specific engineering actions, leaving the root cause under investigation.

Without a public root-cause explanation, IT teams still do not know what failed or whether Microsoft has taken steps to prevent a repeat. The incident also lands as Teams admins are tracking other platform changes, including Microsoft’s planned retirement of Teams Together Mode on June 30.

A Teams file-access issue can quickly become a broader Microsoft 365 workflow problem. Microsoft says files uploaded to Teams channels are stored in SharePoint, while files sent in chats are stored in OneDrive for Business.

What IT teams should do now

The first step is to check MO1329446 in the Microsoft 365 admin center and confirm whether your tenant was affected. Microsoft says its Service health dashboard shows active incidents, issue history, affected services, user impact, status updates, and, when available, post-incident reports.

Administrators should record the outage window for help desk reviews, continuity planning, vendor conversations, and later workaround assessments. Those records also help separate availability problems from security incidents, a distinction that matters as Microsoft 365 accounts remain a target for attacks such as Kali365 device-code phishing.

IT teams should verify whether desktop Office apps, synced files, and direct SharePoint or OneDrive access remained available. A web access failure does not always mean every document path failed, and browser bugs can also force users onto alternative access paths.

Organizations that rely on Teams channels for project work, approvals, client documents, or incident response should confirm whether users could still reach and edit critical files during the outage.

If the answer is unclear, IT teams should define an alternative access plan using locally installed Office apps, OneDrive sync for priority folders, documented SharePoint locations, or escalation procedures for time-sensitive work. They should also watch for any Microsoft follow-up that explains the root cause or provides preventive steps related to MO1329446.

Also read: A recent Windows Update bug shows why Microsoft admins need clear rollback, documentation, and patch-recovery plan.