Microsoft Build wrapped up yesterday, and if there’s a single thread running through this year’s announcements, it’s this: Microsoft is systematically building the most integrated developer platform in the industry. From Azure to GitHub to VS Code to the underlying infrastructure, the pieces are fitting together in ways that should make both developers and competitors pay close attention.
Azure’s Cloud-Native Push#
The Azure announcements at Build were heavily focused on cloud-native development. Azure Container Apps — well, the early hints of what’s coming in that direction — point toward making container deployment dramatically simpler. The goal appears to be offering something between the full complexity of AKS (Azure Kubernetes Service) and the limitations of Azure Functions: a way to run containerized workloads without managing Kubernetes clusters yourself.
More practically relevant for many developers is the continued evolution of Azure Static Web Apps, which is now generally available. It’s a smart product that integrates static site hosting, serverless API backends, CI/CD through GitHub Actions, and authentication into a single service. I’ve been using it for a few side projects, and the developer experience is genuinely smooth — push to GitHub, and your site deploys automatically with a preview URL for pull requests.
The Azure Arc expansion was also significant. Arc is Microsoft’s hybrid and multi-cloud management layer, and the new capabilities around running Azure services on any Kubernetes cluster — including on-premises and on competing clouds — represent a serious strategic play. If you can run Azure SQL, Azure App Services, and Azure ML on your own infrastructure managed through the Azure control plane, the boundary between “Azure” and “not Azure” starts to blur in interesting ways.
GitHub and the Inner Loop#
The GitHub announcements were where Build got really interesting for my daily workflow. GitHub Copilot — the AI pair programmer built on OpenAI Codex — was the headline grabber. It’s currently in limited technical preview, and the demos showed it suggesting entire function implementations, test cases, and even documentation based on context and comments.
I haven’t gotten access yet, so I’ll reserve detailed judgment. But the concept is compelling: rather than AI replacing developers, it acts as an autocomplete system that understands code context at a much deeper level than existing tools. The training data (public GitHub repositories) raises questions about licensing and attribution that the community will need to work through, but the potential productivity impact is enormous.
Beyond Copilot, GitHub Codespaces going generally available is arguably the more impactful announcement for day-to-day development. Full VS Code development environments running in the cloud, preconfigured per repository through devcontainer.json, accessible from any browser. I’ve been using Codespaces in beta for months, and it’s changed how I think about development environments. No more “works on my machine” — the development environment is defined in code and runs identically for every contributor.
The combination of Codespaces for development, Actions for CI/CD, and Copilot for coding assistance gives GitHub a remarkably complete developer workflow. Add Packages for artifact management and the security features (Dependabot, code scanning, secret scanning), and Microsoft has assembled something that’s hard to match.
Power Platform and the Low-Code Angle#
Build also featured heavy investment in Power Platform, Microsoft’s low-code development suite. This is an area where I have mixed feelings. Power Apps and Power Automate are genuinely useful for certain categories of business applications — internal tools, workflow automation, data collection forms — that would otherwise either not get built or consume developer time on low-value work.
The new Power Fx language, based on Excel formula syntax, is an interesting choice. Given that hundreds of millions of people already know Excel formulas, building a programming language on that foundation makes a kind of pragmatic sense even if it makes language purists uncomfortable.
Where I get cautious is when organizations start building critical business logic in low-code platforms. The governance, testing, and maintenance challenges of low-code applications at scale are real and often underestimated. But as a complement to professional development rather than a replacement for it, Power Platform fills a legitimate gap.
.NET 6 Preview and the Performance Story#
The .NET 6 previews shown at Build continued the impressive performance trajectory. Hot reload for both ASP.NET Core and MAUI (the cross-platform UI framework replacing Xamarin.Forms) is a quality-of-life improvement that modern developers expect. The Minimal APIs feature in ASP.NET Core reduces the boilerplate for simple web APIs to just a few lines of code, bringing .NET closer to the simplicity of Express.js or Flask for straightforward services.
The performance benchmarks are genuinely impressive. .NET continues to dominate the TechEmpower framework benchmarks, and .NET 6 is pushing the numbers even further. For anyone who still thinks of .NET as the slow, Windows-only enterprise framework of the 2000s, it’s worth revisiting those assumptions.
My Take#
Microsoft’s strategy is becoming clearer with each Build conference: own the developer platform end-to-end. Azure for infrastructure, GitHub for code and collaboration, VS Code for editing, .NET for the runtime, and AI for assistance. Each piece reinforces the others, and the integration points are getting smoother every year.
What impresses me most is that they’re doing this while remaining genuinely open. VS Code is open source. .NET is open source. GitHub supports every language and framework. Azure runs Linux better than Windows in many scenarios. This isn’t the Microsoft of 2001 — it’s a company that understood, eventually, that developers choose platforms based on capability and openness, not vendor mandate.
The risk, of course, is that this integrated platform becomes a walled garden over time. But for now, the developer experience improvements are real, and competition from AWS and Google keeps everyone honest. If you haven’t looked at the Microsoft developer ecosystem recently, Build 2021 is a good reason to take another look.