Applies to: Azure Local 2311.2 and later; Windows Server 2022
This article explains key differences between Azure Local and Windows Server and provides guidance about when to use each. Both products are actively supported and maintained by Microsoft. Many organizations choose to deploy both as they are intended for different and complementary purposes.
When replacing a datacenter primarily running VMware, Azure Local is typically not the optimal solution, as it is better suited for specific distributed scenarios, like retail stores, manufacturing facilities, or branch offices. Azure Local is optimized for distributed sites with fewer than three clusters of 16 nodes, especially when there are latency or regulatory constraints. Instead, we recommend Azure VMware Solution, which is specifically designed for VMware workload modernization and datacenter replacement.
When to use Azure Local
Azure Local is Microsoft's premier hyperconverged infrastructure platform for running VMs or virtual desktops on-premises with connections to Azure hybrid services. Azure Local can help to modernize and secure your datacenters and branch offices, and achieve industry-best performance with low latency and data sovereignty.
Use Azure Local for:
The best virtualization host to modernize your infrastructure, either for existing workloads in your core datacenter or emerging requirements for branch office and edge locations.
Easy extensibility to the cloud, with a regular stream of innovations from your Azure subscription and a consistent set of tools and experiences.
All the benefits of hyperconverged infrastructure: a simpler, more consolidated datacenter architecture with high-speed storage and networking.
Note
When using Azure Local, run all of your workloads inside virtual machines or containers, not directly on the cluster. Azure Local isn't licensed for clients to connect directly to it using Client Access Licenses (CALs).
For information about licensing Windows Server VMs running on an Azure Local instance, see Activate Windows Server VMs.
When to use Windows Server
Windows Server is a highly versatile, multi-purpose operating system with dozens of roles and hundreds of features and includes the right for clients to connect directly with appropriate CALs. Windows Server machines can be in the cloud or on-premises, including virtualized on top of Azure Local.
Use Windows Server for:
A guest operating system inside of virtual machines (VMs) or containers
As the runtime server for a Windows application
To use one or more of the built-in server roles such as Active Directory, file services, DNS, DHCP, or Internet Information Services (IIS)
As a traditional server, such as a bare-metal domain controller or SQL Server installation
For traditional infrastructure, such as VMs connected to Fibre Channel SAN storage
Compare product positioning
The following table shows the high-level product packaging for Azure Local and Windows Server.
Attribute
Azure Local
Windows Server
Product type
Cloud service that includes an operating system and more
Operating system
Legal
Covered under your Microsoft customer agreement or online subscription agreement
Has its own end-user license agreement
Licensing
Billed to your Azure subscription
Has its own paid license
Support
Covered under Azure support
Can be covered by different support agreements, including Microsoft Premier Support
Where to get it
Download from the Azure portal or comes preinstalled on integrated systems
Microsoft Volume Licensing Service Center or Evaluation Center
Runs in VMs
For evaluation only; intended as a host operating system
Yes, in the cloud or on premises
Hardware
Runs on any of more than 200 pre-validated solutions from the Azure Local Catalog
Runs on any hardware with the "Certified for Windows Server" logo. See the WindowsServerCatalog
The following table compares the management options for Azure Local and Windows Server. Both products are designed for remote management and can be managed with many of the same tools.
Attribute
Azure Local
Windows Server
Windows Admin Center
Yes
Yes
Microsoft System Center
Yes (sold separately)
Yes (sold separately)
Third-party tools
Yes
Yes
Azure Backup and Azure Site Recovery support
Yes
Yes
Azure portal
Yes (natively)
Requires Azure Arc agent
Azure portal > Extensions and Arc-enabled host
Yes
Manual 1
Azure portal > Windows Admin Center integration (preview)
Yes
Azure VMs only 1
Azure portal > Multi-cluster monitoring for Azure Local
Yes
No
Azure portal > Azure Resource Manager integration for clusters
Yes
No
Azure portal > Arc VM management
Yes
No
Desktop experience
No
Yes
1 Requires manually installing the Arc-git statusConnected Machine agent on every machine.
Compare product pricing
The table below compares the product pricing for Azure Local and Windows Server. For details, see Azure Local pricing.
Azure Local is a hyperconverged infrastructure (HCI) cluster solution that hosts virtualized Windows and Linux workloads and their storage in a hybrid on-premises environment. Azure hybrid services enhance the cluster with capabilities such as cloud-based monitoring, Site Recovery, and VM backups, as well as a central view of all of your Azure Local deployments in the Azure portal.
Azure HPC is a purpose-built cloud capability for HPC & AI workload, using leading-edge processors and HPC-class InfiniBand interconnect, to deliver the best application performance, scalability, and value. Azure HPC enables users to unlock innovation, productivity, and business agility, through a highly available range of HPC & AI technologies that can be dynamically allocated as your business and technical needs change. This learning path is a series of modules that help you get started on Azure HPC - you
As a Windows Server hybrid administrator, you integrate Windows Server environments with Azure services and manage Windows Server in on-premises networks.