Another May, another Microsoft Build. I’ve been watching these keynotes for longer than I care to admit, and this year’s event in Seattle felt like the moment Microsoft’s AI strategy finally cohered into something you can evaluate as an engineering platform rather than a collection of impressive demos. The message was unmistakable: Microsoft wants Azure to be the place where AI applications get built, deployed, and managed — and they’re building the toolchain to make that argument compelling.
The Copilot Stack Matures#
The centerpiece of this year’s announcements was the evolution of what Microsoft calls the “Copilot Stack.” Rather than positioning Copilot as a single product, they’re now framing it as a layered platform that developers can build on. At the bottom: Azure AI infrastructure with the latest model hosting capabilities. In the middle: orchestration services for building agent-based applications. At the top: Copilot experiences embedded across Microsoft 365, Windows, and third-party applications.
What caught my attention was the Azure AI Foundry updates. The model catalog now includes not just OpenAI’s models but a growing roster of open-source alternatives — Llama, Mistral, Phi — all deployable with consistent APIs and monitoring. For teams that want to avoid vendor lock-in on the model layer while still getting enterprise-grade infrastructure, this is genuinely useful.
The new agent orchestration framework is perhaps the most ambitious piece. Microsoft is betting that the next wave of AI applications won’t be chatbots — they’ll be autonomous agents that can plan, execute multi-step workflows, and coordinate with each other. The tooling they showed for building, testing, and monitoring these agents is still early, but the direction is clear.
GitHub Copilot Goes Agentic#
The GitHub announcements at Build deserve their own section. Copilot Workspace — the feature that lets you go from issue to pull request with AI assistance — is getting significant upgrades. The new version can handle more complex, multi-file changes and includes better planning capabilities that show you what it intends to do before it does it.
More interesting to me was the deeper integration between GitHub Copilot and Azure DevOps pipelines. The vision they’re painting is one where AI assists not just in writing code but in reviewing it, deploying it, and monitoring it in production. Whether you find that exciting or terrifying probably says something about your relationship with automation.
I’ll admit I was skeptical about “agentic” coding when the term first started circulating. But after watching the demos — and more importantly, after talking to teams who are using early versions in production — I’m coming around. The key insight is that these agents work best not as autonomous coders but as highly capable assistants that handle the routine parts of software development while humans focus on architecture and design decisions.
.NET and Developer Tooling#
Buried under the AI headlines were some solid developer tooling updates. .NET 10 previews showed continued performance improvements and better cloud-native support. The new Aspire dashboard for distributed application development looks genuinely useful — finally, a sane way to manage the constellation of services that modern .NET applications depend on.
Visual Studio and VS Code both got updates focused on — you guessed it — AI integration. But the more practical improvements were around debugging distributed systems and profiling cloud-deployed applications. These are the kinds of features that don’t make keynote highlights but save developers hours of frustration in their daily work.
MAUI, Microsoft’s cross-platform UI framework, continues its slow march toward maturity. I remain cautiously optimistic here — the idea of sharing UI code across platforms is appealing, but the execution has been inconsistent. The performance improvements they showed were encouraging, though I’d want to see them validated in production scenarios.
The Competitive Landscape#
What makes Build 2025 interesting is the competitive context. Google I/O happened the same week, and AWS re:Invent is only months away. Each cloud provider is making its version of the same argument: “build your AI applications here.” Microsoft’s advantage is the integration story — Azure to GitHub to VS Code to Microsoft 365 is a remarkably complete pipeline if you buy into the ecosystem.
The risk for Microsoft is the same as it’s always been: complexity. The Azure portal already feels overwhelming for newcomers, and adding layers of AI services doesn’t simplify things. The teams I talk to who are most successful with Azure are the ones with dedicated platform engineers who can navigate the maze. That’s not a great story for the startup or mid-size company that just wants to deploy an AI feature.
Google’s counter-argument is simplicity and model quality. AWS’s counter-argument is flexibility and existing market share. The next twelve months will be fascinating to watch.
My Take#
Microsoft is doing something genuinely impressive at the platform level. The integration between Azure, GitHub, and the developer toolchain is deeper and more thoughtful than anything the competition offers. If I were starting a new enterprise project today and my team was already in the Microsoft ecosystem, the argument for going all-in on the Copilot Stack would be strong.
But I keep coming back to a fundamental concern: are we building applications that depend on AI capabilities we don’t fully understand? The agent orchestration demos were slick, but the failure modes of autonomous AI agents in production are still poorly characterized. I’d love to see Microsoft invest as heavily in observability and safety tooling for AI agents as they are in the agents themselves.
Build 2025 showed us where enterprise software development is heading. Whether we’re ready for that destination is a different question entirely.