Proud to see @Cephable at #MSIgnite this week.
Our agents run on our fine-tuned Gemma models via Windows ML, and MXC lets Windows enforce what they can touch. Local models decide. Windows enforces.
Public beta in early December: cephable.com/coming-soon-man…
Thanks @mixen@baldwin_ng
With Replit Desktop, Agent can work with files in folders you share, build useful tools, and help turn local data into reports you can share through Replit’s cloud.
Agent builds and runs apps locally, and each build runs in its own sandbox powered by @Microsoft Execution Containers and @NVIDIA OpenShell.
Explore: replit.com/desktop
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.
We are deeply sorry for the disruption this incident has caused our customers and partners. We know the trust they place in our services and take that responsibility extremely seriously. We are seeing broad recovery and stability across our services.
This was a technical issue not related to cyber or AI / agents. The incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change. We have addressed the underlying issue and continue to restore service to remaining customers and regions.
Given the scale of demand, we restored services gradually, validating stability at each stage. While this took longer, it helped ensure a stable restoration.
We will provide a full post-incident report once our review is complete.
Project Zenith is here!
Built with @Microsoft, it's now available on our new Ryzen AI Halo, powered by Gorgon Halo.
Less time setting up. More time building, experimenting, and bringing ideas to life.
Coming soon to more @AMD powered devices.
More freedom to build. More possibilities to unlock.
Llama is a great Windows app, built on WinUI 3 and bringing Local AI to everyone
Get it here - apps.microsoft.com/detail/9P…
Thank you Jeff and @huggingface team! 🙌
Just minutes ago, I had the pleasure to announce Llama for Windows during the .NET conf keynote, thanks @Microsoft for having me!
Llama for Windows brings Local AI to the people.
Your AI. On your PC. Easy and free.
Fully private. No terminal, no set up.
App is open source, and powered by llama.cpp
Download it today at llama.app - and soon from the Windows Store!
Congrats @MorganFunto@ggerganov and team for the launch.
Today at @Adobe MAX we are announcing more ways to create on @Windows! 🎨 🙌
Photoshop, Premiere, After Effects and Substance 3D are optimized for high performance, tools and templates from Adobe Express directly in Microsoft Photos and more!
blog.adobe.com/en/publish/20…
We've been early adopters of Rust since 2018 and a lot of our infra, voice tech, and even some of the current client is already Rust, the holy grail was getting the whole client there. That means Electron goes away, and so does React Native, mobile keeps native UI but shares app code with desktop via Rust. We hope to get it into testing with users soon™. (And it's not Tauri, it's GPUI, so good guess everyone.)
Alright, back to staring at the WoW Forever login screen.
For most people, 8 GB is a great fit for what they do every day. And we’re continuing to make that experience even better.
The latest Windows 11 updates make 8 GB PCs up to 20% more responsive, with multitasking up to 40% faster in our lab tests. You’ll feel it in everyday moments like opening Start, launching an app or getting back to a tab.
Available today, with more improvements to come: blogs.windows.com/windowsexp…