Why this release mattered

The spring 2012 release was a turning point for Windows Azure. Up until this point Azure was largely a PaaS-only platform built around Cloud Services (web roles and worker roles), which made sense for greenfield .NET applications but was a tough sell for anyone wanting to lift-and-shift existing workloads or run anything that didn’t fit the role model — Linux servers, off-the-shelf software, custom networking topologies.

The June 2012 announcements changed that. Azure Virtual Machines (then called “persistent VM roles”) brought real IaaS to the platform with support for Windows Server and Linux. Azure Virtual Network introduced site-to-site VPN connectivity, which together with the IaaS story made hybrid cloud a serious topic at Microsoft for the first time. Azure Web Sites — the predecessor of today’s App Service — also debuted, giving developers a much lighter-weight way to deploy web apps without dealing with role configuration.

The original announcements

Below please find some new information on Windows Azure and related information:

Enjoy and let me know if you have any questions!

Looking back

Reading these notes more than a decade later, it’s interesting how much of today’s Azure traces back to this exact release. App Service, Virtual Machines, and Virtual Network are still core building blocks, even if the surface around them has been reshaped repeatedly — ARM templates, then Bicep, the move to AAD-based identity for everything, the rise of managed Kubernetes via AKS, and the more recent push toward Azure Arc and full hybrid management.

The hybrid cloud framing in particular held up. What started as VPN tunnels and a few connector services in 2012 became ExpressRoute, Azure Stack, Arc-enabled servers and Kubernetes, and the broader idea that “cloud” includes whatever runs in your own data center as long as it’s managed through the same control plane. The 2012 announcements were the early signal of that direction.