Azure Local
March 14, 2023

Windows Server and Azure Local licensing

Untangles the licensing options for Windows Server and Azure Local, covering both infrastructure and workload costs.

Licensing is usually the most complicated part of choosing a platform, and the answer depends on several factors. It helps to split it into two parts: licensing the infrastructure and licensing the workloads that run on it. In some cases the infrastructure licence also covers the workloads. This post, first published in 2023, walks through the options for Azure Local (formerly Azure Stack HCI) and for Windows Server, using the same example cluster throughout.

Azure Local

With both Windows Server and Azure Local you license the physical cores of every processor in a host. Azure Local can be licensed in three ways, and support through Azure is included in every option. Additional VMs, AKS, AVD and SQL Managed Instance running on top may be included, or may need their own licences or charges. We use X as the price, because X depends on your type of contract or subscription and can change over time.

Option 1: Azure consumption per core per month

In the Azure pay-per-use model, every physical core in a server is charged at X euros or dollars per month. For example, a 4-node cluster with 2 CPUs per host and 10 cores per CPU works out as follows:

  • 2 CPUs x 10 cores per CPU = 20 cores per host
  • 4 hosts x 20 cores = 80 cores

That makes a total of 80 cores times X per month. This doesn’t include licences for the Windows VMs that run on top. For those you need a Windows Server Standard or Datacenter licence covering every host. AKS workloads are charged separately per vCPU on your Azure subscription.

Option 2: Windows Server subscription per core per month

With the Windows Server subscription, both the cores and the VMs are licensed. Only the physical cores are charged, and all Windows VMs on the cluster are included in the fee. With the same example cluster:

  • 2 CPUs x 10 cores per CPU = 20 cores per host
  • 4 hosts x 20 cores = 80 cores

The 80 cores are charged at X per month. X is higher than in option 1 because the VM licences are included. All Windows VMs on the cluster are covered, but AKS VMs still need to be licensed the same way as in option 1.

Option 3: Windows Server Datacenter with active Software Assurance

With Windows Server Datacenter licences with Software Assurance, the calculation is different. When all physical cores in the cluster are licensed with Windows Server Datacenter with active Software Assurance, Azure Local itself is free to use. That means no X per physical core per month. This applies only to Azure Local. A Windows Server cluster, with or without a SAN, is licensed differently, as the next section explains.

AKS on Azure Local is also free of charge in this case. And as with every Datacenter licence, you can run unlimited Windows VMs on the cluster under the same licence. Depending on the lifetime of the hardware, the number of AKS clusters and the number of Windows VMs, you can work out which licensing option is the most efficient.

Some OEMs also offer licence packs with the hardware purchase that work in a very similar way to this option.

Windows Server (HCI or SAN solutions)

As described above, Windows Server is also licensed per physical core for every CPU in a host. There are two options for Windows Server. Before choosing, it’s important to know the key differences between Windows Server Standard and Windows Server Datacenter, listed in the table below.

Licence featureWindows Server StandardWindows Server Datacenter
2 virtual machines included✔✔
Unlimited virtual machines included✘✔
Software-defined features (such as Storage Spaces Direct and Software Defined Networking)✘✔

So if you want to use Storage Spaces Direct and build an HCI solution on Windows Server, you need a Datacenter licence.

Option 1: Standard or Datacenter licence

Buy a Windows Server Standard or Datacenter licence for every physical core in the host. A base licence covers 16 cores (two 8-core CPUs). With the 10-core CPUs in our example, each host needs two additional 2-core packs.

  • 2 CPUs x 10 cores per CPU = 20 cores per host
  • 4 hosts x 20 cores = 80 cores

To license those 80 cores you need:

  • 4 Windows Server licences of 16 cores each: 4 x 16 = 64 cores
  • 8 core packs of 2 cores each: 8 x 2 = 16 cores

So in total you need 4 Windows Server licences and 8 core packs to cover all cores. You can choose Standard or Datacenter, but if you build an HCI solution with Storage Spaces Direct you have to choose Datacenter, because Storage Spaces Direct is a Datacenter feature (see the table above). Otherwise it depends on how many Windows VMs you want to license.

Option 2: Standard licence and Windows Server subscription

Option 2 only suits organisations that use a SAN solution with a limited number of Windows VMs, or organisations that want to move to an OPEX model. A recurring monthly licence fee can be very attractive when you only need a few licences, or when you scale your VM licences up and down often. But at some point there is a crossover: with more VMs you can end up paying much more in the long run. Where that point lies depends on your environment and needs.

Want help working out which licensing option is cheapest for your cluster? Get in touch.

Let’s talk it through

One conversation is usually enough to see where the value is for your organization, whether that’s in cost, risk, or everyday management. No slides required.