Azure Stack: Hybrid, Compliant and Consistent by design.

Azure Stack is a Hybrid Cloud platform, the only one of its kind that empowers organizations to deliver Azure Services in their own datacenters. Azure Stack’s unique approach is intended to give organizations the flexibility and capacity they require to envision their journey to the cloud at their own pace. Azure Stack is deployed in an organization’s datacenter as an integrated system with 4-12 identical configurable nodes (varies as per choice of OEM) tailor-made to run Azure Stack by Microsoft’s strong network of OEM partners like HPE, Dell EMC, Lenovo, Huawei and more. Azure Stack also comes in a single node deployment flavor called the Azure Stack Development Kit. This deployment doesn’t demonstrate Azure Stack’s full capabilities but is a handy, less resource intensive option to evaluate and learn about the Azure Stack experience.

The full version of Azure Stack can be deployed in multiple ways (covered later), but it tends to deliver most value in a hybrid deployment scenario that lets the user combine the flexibility of a hyperscale public cloud like Azure and the low latency performance and control one gets in their own datacenters. Azure Stack can also be a perfect fit for workloads in premises that face sporadic connectivity to the internet. Process data locally on the Azure Stack integrated system and once connectivity is restored, seamlessly run analytics or other PaaS offerings on the cloud with that processed data. Azure Stack integrated systems have completely locked down infrastructure from a permissions and networking perspective and can be deployed disconnected from the public cloud. This kind of deployment is ideal in organizations with strict data regulation policies and where data sovereignty is of utmost concern. Not to mention even in a connected deployment, organizations can harness Microsoft’s vast range of security offerings on the world’s most compliant public cloud platform.

As mentioned earlier, Azure Stack integrated systems can be deployed connected or disconnected from the public cloud. These deployment modes are options provided to clearly define the pricing models, identity stores and in turn, the usage scenarios of the integrated systems. Say an organization deploys Azure Stack that can connect to the Azure public cloud as and when required. This gives the organization the option to choose between Azure Active Directory (AAD) and Active Directory Federation Services (ADFS) as their identity store. A connected deployment mode also gives the option to choose between a pay-as-you-go billing model or a capacity-based billing model. The pay-as-you-go model, as the name suggests is like buying an Azure Subscription, enabling the organization to be charged only for the resources they use. In a capacity-based billing model, the organization is required to purchase an Azure Stack capacity plan SKU whose price depends on the configuration of the integrated system they intend to deploy. Disconnected deployments of Azure Stack fit in when organizations intend to use the integrated system in a private cloud solution. In these deployments, ADFS is the only possible identity store but this doesn’t mean that the organization forfeits the choice to connect to Azure in the future.

As of 2018, the latest version of Azure Stack offers all the Azure infrastructure services like Virtual Machines, Scale Sets, Azure Storage, Azure Networking and Key Vault. Current PaaS offerings include the Azure App Service, Container Service (including Docker Swarm, Mesosphere and Kubernetes management templates), Azure Functions and SQL server resource provider. Besides this out of the box functionality, Azure Stack also provides users a plethora of services and IaaS/PaaS solution templates ready to deploy from Azure Marketplace and it also gives users the option to integrate their existing DevOps tooling (Jenkins, PowerShell, Visual Studio, etc.) with Azure Stack.

To conclude, moving to the cloud is an inevitability, and Azure Stack makes the journey of organizations that are currently on-premises to the cloud much more streamlined by giving them the flexibility of the hybrid operating model. Azure Stack enables organizations to generate simplicity and deliver results through truly consistent user experiences that form the backbone to any successful hybrid cloud model. Be it management and monitoring portals, IaaS & PaaS offerings or PowerShell and DevOps tools, Azure Stack on-premises looks and works exactly like Azure making it fit to be named an extension of Azure.

Get started with Azure Stack

One thought on “Azure Stack: Hybrid, Compliant and Consistent by design.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s