A sales team in the middle of a pricing review. A finance group trying to open a workbook before a close. A project meeting where the presentation will not load. For part of Monday and Tuesday, those were the scenes playing out across Microsoft’s web-based workplace: users in Teams and in Office for the web found they could not open files at all. Microsoft confirmed the problem and said it was resolved about nine hours before this briefing went to press, an incident lifecycle that, by the standards of enterprise software, counts as a quick recovery.
The outage affected file access in web-based Microsoft 365 workflows. Users trying to open documents in Teams or in the browser versions of Word, Excel, PowerPoint and OneNote hit failures, disrupting the shared spreadsheets, approvals and presentations that modern offices run on. Microsoft tracked the incident as MO1329446 in the Microsoft 365 admin center and said final details would be provided there after the impact ended. The company did not publicly identify a root cause in its brief updates, directing administrators to the admin center for the full account.
The way the incident played out is as instructive as the outage itself. Microsoft did not initially announce a cause, and the public status updates were minimal. For most users, the first signal was a file that refused to open in Teams, followed by a fallback scramble: try opening from OneDrive, switch to the desktop app, ask the IT help desk whether the problem was local or global. The pattern is familiar to anyone who has lived through a cloud outage, and it explains why the incident drew attention out of proportion to its duration.
The scope of dependence is the story underneath. Microsoft 365 has become the default operating system of office work, and the browser has become its primary interface. When file opening fails across the suite, the blast radius covers document reviews, data analysis, meeting materials and daily team workflows simultaneously. A single incident in the file layer is experienced as a full work stoppage by the people who hit it, even when it lasts only hours.
The timing added friction. The incident landed at the start of a work week, when review cycles are front-loaded and teams coordinate schedules around shared documents. For organizations running web-first Microsoft 365 environments, where users expect files to open in the browser or inside Teams without switching applications, the fallback options were limited and varied by tenant settings, file type and permissions. Administrators spent Monday morning triaging reports and telling users the outage was not local.
The recovery was comparatively fast. Microsoft confirmed the fix and restored file access roughly nine hours after the problem emerged, and users were directed to refresh or retry. The company’s handling followed the modern playbook: confirm the incident, keep status minimal, point administrators to the admin center, and let the postmortem live where the IT department can find it. For most businesses, the cost was measured in lost hours on a Monday, not lost data.
The incident fits a pattern that enterprise customers have started to notice. Microsoft 365 has experienced several significant outages in the first half of 2026, including a wide incident in April that took down Teams, Outlook and Defender for business users in multiple regions. Individually, each outage is short and contained; collectively, they have made reliability a standing question in renewal conversations. A platform that everyone depends on gets a small margin for error, and the margin shrinks every time files will not open.
The broader lesson is about the fragility of web-first work. The shift to browser-based productivity delivered collaboration and mobility, but it also concentrated risk: when the file layer is in the cloud, every user inherits the cloud’s problems. The desktop app was once the fallback for a web failure; now the web is the default and the desktop is the fallback. Microsoft’s response to that inversion, from offline modes to sync improvements, has been steady, but incidents like this one show how much trust is riding on a few services. The outages have also pushed some enterprises to revisit their assumptions about redundancy, and a few have begun keeping critical files synchronized to local copies so the web layer is not the only path to a document.
For Microsoft, the incident is a footnote to a busy week that included major AI announcements and new hardware. For its customers, it is a data point in an ongoing calculation about how much of the office belongs in the browser. The files open again, and the work resumed, and the Monday-morning scramble will be forgotten by the end of the week. But the question of what happens when the file layer fails, and how fast the fallback works, is now part of every enterprise’s risk review, and this incident supplied fresh evidence on both sides of the ledger.
