At #MSIgnite, Satya is outlining our AI Platform for Work with Copilot + Microsoft IQ + Agent 365. The next big leap in the Copilot experience is #Autopilot which is launching today in Public Preview. I can't live without my Autopilot and excited to hear your feedback.
youtu.be/KtV_f3chj9A?si=ASig…
Kudos to @OmarShahine and team!
Huge congratulations @manikgupta and team for your announcement of Atlas today to transform travel - it’s much needed - excited to support you and the team!
Yogesh and I just raised $12M to help everyone experience more of the world.
Introducing Voyage Labs, and our first product: Atlas, a personal AI agent.
Just tell Atlas what you’re dreaming of:
• a beach escape
• a ski trip
• a weekend road trip
• a table for friends tonight
Atlas helps you plan it, book it, and keeps watch while you’re out there. The beta opens today, on the web and over text.
Our $12M seed round is led by Kleiner Perkins, alongside SignalFire, SVAngel and some incredible angels.
Every great story starts with someone leaving home.
Try Atlas now:
atlas.voyagelabs.ai@yogesh_jain30
#MSIgnite - Copilot Managed Runtime is GA!!!
Read the latest from Ryan Cunningham on how we've built a secure, robust platform for building apps across Copilot, Cowork, Code, Github, Studio and more with support for SharePoint, Dataverse, Fabric, and more -- all on a governable and observable app stack.
lnkd.in/p/gGm93GV8
Read this great blog from @OmarShahine - I love how he's built something new in a new way - while embracing with the best of Microsoft culture to dogfood the product to build the product every hour of the day
I’m incredibly proud of the Microsoft Autopilot Team. 7 months and 11 days ago our team had zero people and zero lines of code. In a short time we assembled some amazing AI builders in Microsoft to build something new.
Today we are bringing the first enterprise-grade autonomous digital teammate to life. It has its own identity, email, OneDrive and works where you work.
techcommunity.microsoft.com/…
The key to AI is context and in WorkIQ, #SharePoint is innovating faster than ever to bring the #1 data source for context from collaboration, processes, and knowledge to deliver better AI outcomes for you. The latest from #MSIgnite today:
techcommunity.microsoft.com/…
At #MSIgnite, we're making @MSFTCopilot the front door to Dynamics 365, by bringing intelligence, apps, agents, and business processes together like never before. aka.ms/D365Ignite2026
For years, I have reviewed my slides on the flight to #MSIgnite. But never this way… UX (Copilot, Teams w Autopilot) + IQ (M365 w SharePoint and D365) + A365 = the stack for the next era.
This year at Microsoft Ignite, we're excited to share how people and org context in Work IQ can enable richer Copilot and Cowork experiences. Learn more: msft.it/6015xDQa7
Using AI tools at work shouldn’t exceed your budget. In partnership with GigaOm, we compared Copilot to several leading tools and found that Copilot was more cost effective without sacrificing quality on both everyday and advanced AI tasks. See how Copilot stacks up in the full analysis: msft.it/6010xDg3e
Accelerate Salesforce Migration with Dynamics 365 Activate at #MSIgnite
Hands-on lab schedule to help you move quickly to a better experience and agentic platform at lower cost - now is the time.
ignite.microsoft.com/en-US/s…
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.
Agentify your business processes-the next era of business applications
Excited to share the latest next week in our session - Tues Nov 17 - 2PM - #msigniteignite.microsoft.com/en-US/s…