At @Microsoft Ignite, we’re sharing our next chapter, as Office and @MSFTCopilot evolve from a set of applications into a human-led, agentic system of work.
We’re making Word, Excel, PowerPoint, and Outlook more intelligent and introducing three new experiences: Today, Pages, and Workspaces. Together, they’re built for how work is changing.
You provide the context, guide the work, and own the result. AI moves the work forward without taking you out of the loop.
I can’t wait to see what you create.
Read more: https://t.co/ma8ttq1TET
#MSIgnite, #Microsoft365
More details on the root cause can be found in the Microsoft 365 Admin center, and an abridged version can be found below.
We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations.
The incident on Thursday, November 12th, 2026, was caused by three main factors that together caused a global outage for the networking gateway that fronts many Microsoft 365 services.
First, a latent defect caused servers to become overwhelmed and unresponsive under certain load conditions. This was due to lock contention inside an internal process which caused the machine to become unavailable. This defect was the result of a fix that was prepared specifically for Microsoft 365 networking gateway servers; neither the underlying defect nor the fix applies to broader Windows deployments.
The initial change in behavior first started deployment in July of this year. The update went through safe deployment and saturated globally over several weeks, during which time no issues were observed. For more than three months, the change was deployed worldwide without impact.
Our normal load testing did not detect the latent issue because the different traffic and SKU mix used in our test labs. The contention issue is worsened on machines with more cores and newer hardware; whereas our load testing tended to focus on our weaker hardware SKUs with fewer cores.
Second, a surge in load increased the likelihood for the networking gateways to encounter the contention. Within Microsoft 365, we maintain two independent and heterogenous network gateway systems designed for isolation and high availability. This allows many Microsoft 365 services to fail to/from them during outages or disruptions. Approximately fifteen hours before the outage, Teams failed over from the alternative networking gateway to the ‘primary’ gateway that also supports Exchange Online. This increased the load on the networking gateway and changed its traffic patterns. This type of failover is part of normal operations and is integral to standard Microsoft resiliency efforts.
Third, at the same time, nearly 14% of server capacity for the networking gateway was out of service due to an unrelated issue from the previous day. This server capacity was on track to be returned to active service through routine maintenance and health processes. The service had sufficient capacity headroom, so the reduction in server capacity had no impact on its own.
Taken together, the increased load and the reduced server capacity, caused the network gateway to encounter the latent bug from July. This caused requests to build up until servers ultimately stopped responding. This occurred during the peak window of traffic in the United States.
When servers lose connectivity, our traffic management systems automatically route users to other healthy endpoints. This happens often and is critical to avoiding any interruption due to hardware, software, or network defects and is normally what makes the service resilient. However, the redirected traffic increased the likelihood for the same problem to occur on the remaining endpoints. This caused a cascading failure from server to server as the same amount of load was spread across fewer servers. In less than two hours, the previously unknown defect was encountered across our fleet and rendered them unresponsive. At its lowest, more than 80% of servers were unresponsive.
Normally, the network gateway is composed of thousands of ‘capacity units’ which represent shards of capacity, hardware, and networking infrastructure. These ‘capacity units’ are then organized into regions. In this case, due to a separate issue, the normal bulkheads between these different partitions did not stop the cascading failure. This is what allowed the impact to spread across our network gateway infrastructure globally.
Several services like Teams, OneDrive, SharePoint, and Office apps failed out of the faulty network gateway infrastructure. That is why those services were restored earlier, with Teams chats and meetings functioning without issue for most of the outage. But not all services, like Exchange Online, can fail out of this network gateway.
Recovery took longer than usual because as servers returned to service, they were immediately overwhelmed by waiting traffic and became unresponsive again. Our normally automated recovery processes were not designed to restore service from this broad unresponsive state. Additionally, since the main code defect was a latent bug from several months previous, our normal rollback, flighting, and feature flags were unable to quickly revert the change.
After engineers confirmed the defect as the cause, we developed an update that returned the code path to the previously known good state. To effectively apply this fix, and to slowly bring the service online again, we took groups of servers out of service, applied the change, and restarted them before returning them to service. This process was carefully applied to large quantities of infrastructure at a time (e.g. 50%+ of a region).
The final Post-Incident Review (PIR) will provide more details later this week.
I want to share what we know so far. This was not a cyberattack or an issue caused by AI tooling. Our amazing team was able to work through a very challenging situation to restore service.
Our investigation points to technical challenges and failure modes (cascading failures + thundering herds at our network perimeter) that made recovery more difficult than normal. I'm working closely with the engineering team to complete the full post-mortem. We will publish the post-mortem shortly covering the step-by-step timeline and our many repair items to avoid similar outages in the future.
We take our responsibility to our customers seriously and will do everything we can to learn from this and prevent it going forward.
This update marks a new beginning for @Outlook Search. We’re introducing improvements to ranking and resilience, along with a new feedback loop that helps us improve with every search.
https://t.co/1vfd2bU7Bs
How Outlook Search is changing: ranking, resilience, and the feedback loop
Full blog: https://t.co/tmh1uNaCmD
Video created with Copilot Video Agent. Coming soon.
Great work, PowerPoint team! This was feedback customers shared early in the Copilot in PowerPoint journey. You keep sharing and we will keep listening.
Still repeating the same brand-specific instructions for every presentation?
Bring your organization’s brand expertise into Copilot in PowerPoint with shared custom skills in Brand Kit.
Give teams reusable, brand-specific workflows—so they can spend less time repeating instructions and more time shaping their message.
Your brand’s expertise. Shared across teams. Ready to use in PowerPoint.
Copilot for finance takes on the multi-step work of pulling data together and reconciling it in Excel. Being able to see exactly how Copilot got to a number will make this something finance teams can rely on during close. It's been great watching the team build that in from the start.
Finance teams help the business understand what's happening and decide what to do next. That takes expertise, and a lot of routine work to get to the insights.
Today we're introducing more than 25 new finance skills and plugins in Microsoft Copilot, across Excel and Cowork, to take on more of that work and give you more time for the insights.
Copilot understands accounting workflows and can work the way you do. Here's a variance analysis in Excel, using the formulas and layout you want.
I’m sorry this disrupted Office customers. An update inadvertently disabled Office for a subset of Office 2021 for Mac customers. We identified the issue early in deployment, limiting the impact to a small subset of customers.
We’ll learn from this and keep working to prevent it from happening again. Learn more: https://t.co/KtTgbxe6Et
Legal work runs on precision, and now Microsoft Copilott has 20+ purpose-built legal skills to match.
Building on the Legal Agent we introduced earlier, we're also bringing new partner-built plugins directly into Copilot. These are specialized tools designed around real customer problems, right where people already work in Office.
Looking forward to your feedback. More details below.
Give your legal team a head start. Use Copilot in Word to draft agreements and review contracts against your standards, or Cowork to take on broader, multi-step work across contracts, emails, meetings, and files.
Your trusted sources. Your standards. Your final say. https://t.co/ffVLrS3nV5
@DerekJohnsonSV Across the Office and Copilot ecosystem, we’re continuing to move beyond the status quo by making every interaction with the system easier and more natural.
We’re launching several exciting updates to Copilot Notebooks that help you bring artifacts and context together and turn it into work, all in one place!
Rolling out to Frontier now:
• Start with a goal: describe what you’re working on, and Copilot can build a notebook with relevant references from your work and the web.
• Bring the full power of Office into your notebook: view, edit and collaborate on Word, Excel, and PowerPoint files without leaving your notebook.
• Delegate work in context: ask Copilot to find and add references, synthesize project information, and create or edit files.
• Turn insights into interactive reports: create interactive reports with Copilot Pages.
• Explore your content through richer audio overviews: try Critique and Debate formats, and navigate longer overviews with topic-based episodes.
• Schedule recurring work: set up tasks like a daily brief or weekly status deck.
Blog for more details: https://t.co/oRfjtTAKuh
Please try it out and send us feedback!
Starting today, the full power of Microsoft Office is rolling out to the Copilot App in Frontier. We're bringing together the capabilities that your business runs on every day within Word, Excel and PowerPoint inside of the new OS for work.
This new experience supports your entire workflow, from the first prompt to the finishing touches. You can collaborate with others, use branded templates, and return to earlier iterations through version history as your work evolves. In the same workspace, you can choose from a robust library of frontier models or use the Auto router to match the right model to the task at hand.
Learn more in my blog post: https://t.co/yCarL7okGc
When customers trust us enough to share their own product evals, we are able to build a flywheel to improve the product together. A single cell that can hold an entire play is a great example, because every new way people use it shows us where to take Excel next.
An entire play, in one Excel cell. Then you ask Copilot what happened on third down passes. Quick look at how the NFL is using data types, and what we learned building it with them.
@MSFTCopilot
No matter where your work starts, whether in the Copilot app or the Office apps, you have the power to go from creation to collaboration.
Customers shouldn't have to choose between the latest models and the tools they rely on.
Looking forward to you giving it a try in Frontier soon. Learn more https://t.co/Hv67E1t6VC
We’re building Copilot as a new OS for work that spans every model, every form factor, and every task. Today, we’re announcing our biggest update to Copilot to date, bringing four things together:
· Autopilot: proactive and long-running agent built for the enterprise
· Code: build apps with Copilot, hosted inside your company’s tenant
· Home: Chat + Cowork together
· Office: now fully embedded in Copilot (and Copilot embedded in Office, of course!)
Plus, you can invoke Copilot in Teams, and we’re introducing Today, a proactive experience that surfaces the most important information from across M365 without needing to ask for it.
The way we work is changing and so are our workflows. This update brings AI into that flow, from answering a question, to building an app, to getting work done on your behalf.
@yusuf_i_mehdi The early web experience is a great comparison, because people didn't adopt the web all at once, they found one thing it made easier and kept finding more, and I think Copilot will grow into people's days in much the same way
@jeffteper SharePoint is the foundation of people's work context, and a lot of what makes an agent helpful is how well it can understand that context. It's great to see that foundation getting smarter right alongside Autopilot. Exciting day for the whole team.