This article is based on reporting originally published by Redmond Magazine in July 2017, covering announcements made at Microsoft’s Inspire conference in Washington, D.C.
What Is Azure Stack?
Azure Stack is Microsoft’s on-premises extension of its Azure public cloud platform. It allows enterprises and service providers to run their own instances of the Azure environment inside their own datacenters, using the same APIs, tooling, and management interfaces as the public Azure cloud. Rather than treating on-premises infrastructure as a separate silo, Azure Stack is designed to present itself as just another Azure region — enabling a genuinely consistent hybrid cloud model.
As Microsoft CEO Satya Nadella stated at the Inspire conference keynote: “We’re building out Azure as the first hyper-scale cloud that supports true distributed computing with Azure Stack.”
General Availability and Hardware Partners
After more than two years of development and preview programs, Microsoft announced at its 2017 Inspire conference that Azure Stack would reach general availability in September 2017. Hardware-integrated systems — sometimes called Azure Stack appliances — were to be delivered by a set of launch partners:
- Dell EMC — GA appliances available September 2017, based on PowerEdge R730XD systems, with follow-on hardware built on the then-new 14th-generation server platform using Intel Xeon Scalable (“Skylake”) processors.
- Hewlett Packard Enterprise (HPE) — GA appliances available September 2017.
- Lenovo — GA appliances available September 2017.
- Cisco — Appliances planned for later in 2017.
- Huawei — Appliances planned for Q1 2018.
Dell EMC had already launched a single-node developer edition of Azure Stack in May 2017 — priced at $20,000 — for teams wanting to evaluate the platform before production-grade systems became available. Full production appliances were planned to support up to 12 nodes.
A Common Application Model Across Cloud and On-Premises
The central value proposition of Azure Stack is developer consistency. Microsoft Corporate VP Julia White summarized it at the Inspire press briefing:
“You’re writing one set of code, you’re updating one set of code, you’re deploying one set of code but it is running in two places. In a Visual Studio dropdown, you can select Azure or Azure Stack. It’s that simple.”
Julia White, Corporate VP, Microsoft
This means DevOps pipelines, ARM templates, and CI/CD toolchains built for Azure are intended to work without modification against an Azure Stack deployment. Teams do not need to maintain separate infrastructure-as-code definitions or separate deployment scripts for on-premises versus cloud targets.
Supported Workloads at Launch
At general availability, Azure Stack was scoped to the most commonly used Azure capabilities. Supported workloads included:
Infrastructure as a Service (IaaS)
- Virtual Machines — Standard VMs and Windows Server images
- Storage — Azure Blob, Table, and Queue storage
Platform as a Service (PaaS)
- Azure App Service — Including Web Apps, Mobile Apps, API Apps, and Azure Functions
- SQL Server — Running in Azure Stack VMs, enabling database-as-a-service patterns
Services planned for the near-term roadmap at the time included IoT Hub and Azure Data Services. Microsoft Senior Product Director Mark Jewett noted that while native Azure Data Services were not yet available, SQL Server running inside Azure Stack VMs could fill that gap in the interim.
Serverless Computing with Azure Functions On-Premises
One of the more significant technical capabilities included from day one was support for Azure Functions via the App Service offering. This means organizations could run event-driven, serverless workloads entirely on-premises — a scenario not previously easy to achieve with competing platforms at the time.
Nadella positioned serverless as the next major wave in application architecture at the keynote:
“Virtualization has been amazing, but now this new era of micro services, containers and serverless [computing] is going to be fundamentally transformative to the core of what we write as applications.”
Satya Nadella, CEO, Microsoft
By including Azure Functions in the Azure Stack App Service, Microsoft was enabling organizations to adopt serverless patterns without requiring all workloads to reside in a public cloud — a key concern for regulated industries and data-sovereign environments.
Target Use Cases
Azure Stack was positioned to address several scenarios where running workloads entirely in a public cloud is impractical or prohibited:
- Data sovereignty and compliance — Industries or jurisdictions requiring that data remain within specific geographic or organizational boundaries.
- Disconnected or intermittent connectivity — Edge computing scenarios such as cruise ships, oil rigs, remote mining sites, or military deployments where reliable internet access cannot be guaranteed.
- Legacy system modernization — Organizations wanting to build new cloud-native applications that interact with existing on-premises systems without a full cloud migration.
- Consistent hybrid operations — Teams wanting a single control plane, API surface, and toolchain across both public cloud and on-premises deployments.
Underlying Infrastructure: Windows Server 2016 Technologies
Azure Stack is built on the software-defined infrastructure capabilities introduced in Windows Server 2016, including:
- Storage Spaces Direct — Hyper-converged storage using local disks across nodes
- Hyper-V — Virtualization layer for running VMs
- Windows Containers — Container runtime support consistent with Azure
These components allow Azure Stack to deliver a consistent software-defined infrastructure layer that mirrors what Microsoft operates in its public Azure regions, making the common API and management model technically feasible.
How Unique Is Azure Stack’s Hybrid Approach?
Microsoft’s claim of being “the first” true hybrid cloud offering was contested even at launch. Competing solutions from VMware and OpenStack-based appliance vendors had been addressing hybrid cloud scenarios for years before Azure Stack reached general availability.
However, Microsoft’s specific differentiation — and the claim that partners like Dell EMC supported — was the shared control plane: a single Azure Resource Manager (ARM) API surface, portal experience, and toolchain that spans both environments without requiring separate management interfaces. Paul Galjan, Senior Director of Product Management for Dell EMC Hybrid Cloud Platforms, commented at the time: “It is unique. It fits into a niche in the market that no other software vendor is offering anything quite like it.”
Whether that control-plane consistency is a sufficient differentiator for a given organization depends heavily on how deeply invested that organization already is in Azure tooling and skill sets.
Key Takeaways for DevOps Teams
- Azure Stack enables a single ARM-based deployment pipeline that targets both Azure public cloud and on-premises infrastructure.
- DevOps teams can use the same Visual Studio tooling, Azure CLI, PowerShell modules, and ARM templates for both environments.
- Serverless workloads via Azure Functions can be hosted entirely on-premises, reducing dependencies on public cloud connectivity for event-driven architectures.
- PaaS capabilities reduce the operational overhead of managing individual VMs for application hosting — even in disconnected or regulated environments.
- The hardware comes pre-integrated from validated OEM partners, reducing the infrastructure complexity traditionally associated with on-premises private cloud deployments.
Note: This article reflects announcements and plans as of July 2017. Azure Stack has continued to evolve significantly since then, including the introduction of Azure Stack Hub, Azure Stack Edge, and Azure Stack HCI as distinct product lines.