AgentFlareSocial Pulse · AI · 2026-10-12 13:03 UTC
@satyanadella: Microsoft's Maia bet and capacity limits
Today we are announcing our biggest bet yet on our own silicon. Starting next calendar year, we will scale our Maia family to multi-gigawatt deployments, making it the primary inference system for …
You're reading the full report — free for humans and search engines.
The same content ships as a structured JSON dataset (normalized facts, sources and
citation arrays, no HTML parsing) so AI agents can consume it directly — metered per fetch via the open
HTTP 402 payment protocol.
crawlerAutoPrice=true · verify at https://esa.aisa.one/api/v1/access/verify
Today we are announcing our biggest bet yet on our own silicon. Starting next calendar year, we will scale our Maia family to multi-gigawatt deployments, making it the primary inference system for our own product and services. And we’re introducing Maia 300, which delivers 40% more tokens per watt compared to leading GPU-based systems. We are already deploying Maia 200 across the US, Europe, and Australia, delivering up to 1.7x more tokens per watt across experiences in Teams and Copilot. Our goal is to build on the full-stack efficiency gains we’ve already seen, while continuing to bring the latest innovations from across the ecosystem into our fleet.
Part of the conversation: Microsoft's Maia bet and capacity limits
@satyanadella says Microsoft is making its biggest bet yet on its own silicon, scaling Maia to multi-gigawatt deployments starting next calendar year. He says Maia 300 delivers 40% more tokens per watt than leading GPU-based systems, and Maia 200 is already deployed across the US, Europe and Australia. @thsottiaux says changes and more compute should very significantly decrease the 'Selected model is at capacity' error.
Why it mattersBoth posts concern inference compute: one is a chip strategy claim, the other a user-facing capacity fix.
Other posts in this conversation
Day 11/ We've landed a series of changes and more compute to very significantly decrease the occurrence of the disruptive "Selected model is at capacity. Please try a different model". When it does happen, it should also eventually just continue by itself and not just block on it. Let us know if you still see it out there in the wild and we'll take a look.
How it compares
This post ranks #6 of the 14 highest-engagement ai posts AgentFlare tracked on 2026-10-16, with 1.3× the median likes. See the full AI briefing.
How this page is made. Post text and engagement come from the AISA Twitter API (advanced search, top results). Conversation summaries are written from the post texts only; a post is the author’s claim, not a verified fact.
Sources & citations
- @satyanadella on X 2026-10-12 13:03 UTC
- AISA Twitter API