Microsoft Azure Stack

Microsoft, founded in 1975 and headquartered in Redmond, Washington, evolved from dominating PC operating systems (MS-DOS and Windows) into a broad technology provider spanning software, devices, digital services, and cloud. Since launching Azure in 2008, cloud services have become central to Microsoft’s shift toward a global digital service model, with Azure positioned as a leading cloud platform behind AWS. Yet full public-cloud migration remains unrealistic for many organizations due to technical constraints, regulatory compliance, and legacy application requirements, forcing hybrid deployments that compound operational overhead and expose incompatibilities between on-premises and cloud-native architectures, tools, and DevOps practices.

Azure Stack is Microsoft’s response: a turnkey, fully integrated hardware-and-software system delivered through partners such as Dell EMC, HPE, and Lenovo, designed as a native extension of Azure. It aims to provide consistent hybrid cloud operations by reusing the same APIs, management experiences, development tools, and application model across on-premises and Azure, including integrated support and (typically) unified billing with pay-as-you-use pricing. Core use cases include edge/disconnected scenarios, highly regulated workloads that must remain local, and application modernization where teams want cloud architectures (serverless, microservices, PaaS) while deploying on-premises without code changes.

Architecturally, Azure Stack mirrors Azure with layered infrastructure, a service delivery framework, and Azure Resource Manager as the unifying control plane. Initial services span IaaS (VMs, containers, networking, storage, Key Vault) and selected PaaS (App Service, Functions, Service Fabric, Container Service, Cloud Foundry). However, Azure Stack is explicitly “a work in progress,” initially limited in available services and scalability, with long-term success hinging on Microsoft’s ability to deliver timely service parity and third-party marketplace compatibility. For Azure-invested organizations, the Azure Stack Development Kit is recommended to assess hybrid readiness.

• Microsoft is headquartered in Redmond, Washington, USA and was founded in 1975.
• Microsoft entered the cloud computing market in 2008 with the Azure platform.
• Microsoft Azure is positioned as second only to AWS in the cloud service provider market.
• Azure Stack is delivered as a fully integrated hardware, software, and service package via hardware partners such as Dell EMC, HPE, and Lenovo.
• Azure Stack integrates billing and technical support into Azure, producing a single monthly bill in typical deployments.
• Azure Stack follows a pay-as-you-use model with no upfront costs or licensing fees for connected deployments.
• Disconnected Azure Stack systems can use a capacity-based pricing model with a fixed yearly fee.
• Azure Stack’s initial release is limited to a single scale unit per region and a single region per deployment.
• Azure Stack Development Kit is a free single-server deployment intended for development or testing.
• The first delivery of Azure Stack integrated systems was planned for September 2017.

• “However, despite multiple advantages of moving business apps to the cloud, a 100% migration to the public cloud is still not a feasible option for the foreseeable future.”
• “This does not just lead to a massive maintenance overhead; a bigger problem is that traditional on-premises applications and apps developed for the cloud are designed, developed and operated in fundamentally different ways…”
• “Implementing the same DevOps practices across hybrid environment has been every developer’s dream since the early years of cloud computing…”
• “The opposite approach – designing apps ‘cloud-first’ but being able to deploy them on premises as well – looks much more promising, at least in theory.”
• “Azure Stack is a native extension of Microsoft’s Azure public cloud, providing the same core IaaS and PaaS services, implementing the same application model and supporting the same APIs, management and development tools.”
• “The number of potential usage scenarios that are unlocked with this hybrid cloud approach could fill a book…”
• “Availability of new and updated Azure services on Azure Stack is perhaps the most complicated and most crucial factor for the future development of the platform.”
• “This unified application model ensures consistent developer and DevOps experience between Azure and Azure Stack.”
• “It must be stressed however that Azure Stack is still a work in progress.”
• “As usual, the devil is in the detail: the future success or failure of Microsoft’s hybrid cloud platform depends solely on the company’s ability to deliver on their promise.”