SQL Server on Azure Local runs SQL Server inside Windows Server or Linux virtual machines (VMs) on infrastructure at your site. Hyper-V, storage, and clustering provide the local platform; Azure Arc can add cloud-based management for supported resources when the environment is connected. The database workload and its data remain local—the management connection does not move SQL Server execution to Azure.
What is SQL Server on Azure Local?
It is SQL Server deployed on customer-owned Azure Local infrastructure, rather than a database service running in an Azure datacenter. Microsoft describes it as SQL Server workloads running on Windows Server or Linux VMs in your own infrastructure. The approach can suit organizations that need to keep data on site, process it near users or equipment, or modernize SQL Server without moving the database workload to the public cloud. Microsoft’s overview lists these deployment reasons and explains the two operating modes.
Azure Local supplies the infrastructure and virtualization platform. You deploy and operate the guest VM and SQL Server workload, and plan its availability, backup, and recovery. This differs from using a managed database service: Azure services may help manage supported resources, but they do not take over database execution or remove the need to design workload protection.
How does SQL Server on Azure Local work?
The architecture has a physical platform, a virtualization layer, SQL Server guest workloads, and—if connected—an Azure management path. Each layer has a distinct role:
#1 Best Overall
| Layer | What it does | Where it operates |
|---|---|---|
| Physical infrastructure | Validated servers provide compute, storage capacity, networking, and clustering foundations. | At the customer site or edge location. |
| Azure Local platform | Hyper-V hosts VMs; Storage Spaces Direct and failover clustering support the platform design. Azure Local components, including the Azure Arc resource bridge in connected deployments, support Azure-based lifecycle operations. | On the Azure Local infrastructure. |
| SQL Server workload | SQL Server is installed in a Windows Server or Linux VM. The VM runs the database workload locally. | On the customer’s Azure Local system. |
| Azure management | For supported connected resources, Azure Arc can provide Azure inventory, governance, monitoring, security, and licensing experiences. | Management services are hosted in Azure; database execution and storage remain local. |
Microsoft’s Azure Local baseline architecture describes a multi-machine design covering 2 to 16 machines. That range describes the scope of that reference design, not a universal sizing rule or a performance result. The same baseline gives a two-machine storage-switched example requiring at least 11 IP addresses; that is an example-specific configuration, not a general requirement for every deployment.
Hardware, network, and capacity choices must match Azure Local’s current supported deployment design and the intended SQL workload. Microsoft’s deployment guidance directs customers to select an integrated, premium, or validated system from the Azure Local catalog and work with an OEM or systems integrator on sizing. Do not assume that an arbitrary server model is supported. The cited installation sequence is specific to Azure Local version 23H2; verify current requirements and validation before procurement or deployment. Microsoft’s version 23H2 deployment guidance covers hardware selection and VM installation.
Rank #2
Can SQL Server run on Azure Local without internet?
It can operate in disconnected operations, intended for settings such as restricted-connectivity, regulated, remote, or air-gapped environments. But disconnected operation changes which Azure management features are available. Microsoft marks connected mode generally available in its current overview; disconnected operations avoid an ongoing dependency on the public-cloud control plane.
| Mode | Connectivity and management | Important trade-off |
|---|---|---|
| Connected | Azure Local maintains Azure connectivity, and SQL Server instances can be connected to Azure Arc for supported centralized management experiences. | Azure-based management depends on the connected path and the prerequisites of each service. |
| Disconnected operations | The environment operates without an ongoing public-cloud control-plane dependency. | The SQL Server extension for Azure Arc is not supported for SQL Server on Azure Local in this mode, so its SQL inventory, best-practices assessment, and Azure SQL Server management experiences are unavailable. Plan local tools and operating procedures instead. |
For the supported Arc-connected SQL Server architecture, the Azure Connected Machine agent and SQL Server extension communicate with Azure services over outbound HTTPS on TCP 443 using TLS. Some capabilities, including Defender for Cloud and best-practices assessment, also require Azure Monitoring Agent connected to a Log Analytics workspace. These are requirements for the connected management path, not a reason to infer that disconnected operations need Azure connectivity. See Microsoft’s Azure Arc-enabled SQL Server overview for the connected architecture and agent details.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteRank #3
How does Azure Arc fit into SQL Server on Azure Local?
Azure Arc is the management connection for supported connected resources, not a remote database engine or a replacement for SQL Server operations. It can surface supported SQL Server instances in Azure management experiences for inventory, governance, monitoring, security, and licensing. The underlying VM, database processing, and data storage continue to reside on Azure Local.
Arc’s role is conditional on connectivity and feature support. In particular, the SQL Server extension is unavailable for SQL Server on Azure Local in disconnected operations. Azure Arc also does not provide SQL Server high availability or disaster recovery by itself; those depend on platform and SQL-native design.
Rank #4
How should availability, backup, and recovery be designed?
Start with the workload’s recovery point objective (RPO)—how much data loss is acceptable—and recovery time objective (RTO)—how long service can be unavailable. Then combine host-level resilience with SQL Server mechanisms appropriate to local node failures, site failures, and the required failover behavior. Microsoft’s Azure Local workload resiliency guidance discusses these options.
| Mechanism | What it protects or provides | Design consideration |
|---|---|---|
| Windows Server failover clustering | Coordinates cluster behavior for SQL Server VMs and platform availability. | Microsoft’s deployment guidance describes Azure Cloud witness for quorum control and recommends anti-affinity rules to place relevant VMs on different physical nodes. |
| Always On Availability Groups | Protect user databases through primary and secondary replicas. | Synchronous commit can suit nearby, low-latency replicas; asynchronous commit can suit more distant replicas where latency is higher. |
| Always On failover cluster instances | Protect a SQL Server instance using shared cluster storage, including shared Storage Spaces Direct storage in the described deployment guidance. | Plan around the shared-storage and cluster design; this differs from database-level replica protection. |
| Backups | Provide recovery points from which data can be restored. | A backup is not rapid failover. Choose retention and recovery-copy locations to meet recovery objectives, including an off-instance copy where required. |
| Replication | Can support data distribution or disaster recovery. | Replication does not automatically fail over entire databases. |
Use a deliberate combination rather than treating any one mechanism as complete protection. A local cluster can address a node failure but may not satisfy site-level recovery needs; determine whether a recovery copy must sit outside the Azure Local instance, and specify whether failover should be automatic or manual. The version 23H2 deployment guidance also describes SQL Server VM high availability and backup considerations.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What should you evaluate before choosing this architecture?
- Connectivity and sovereignty: Decide whether Azure Arc-connected management is appropriate or whether disconnected operations are necessary, and account for the SQL extension’s feature limitations in disconnected mode.
- Data location and latency: Keeping compute and data local can support residency needs and processing close to users or equipment. It does not establish a universal performance advantage; results depend on the workload and design.
- Recovery objectives: Define RPO, RTO, node- and site-failure scenarios, failover behavior, and backup locations before choosing clustering, replicas, and recovery copies.
- Operational ownership: Plan who will maintain hardware, Azure Local, guest operating systems, SQL Server, and workload-specific protection. Azure Arc management does not make this a managed database service.
- Validated capacity: Confirm current catalog validation, workload sizing, network design, and enough capacity to handle maintenance and failure scenarios with an OEM or systems integrator.
There is no generalizable cost or performance figure for this architecture in the cited guidance. A deployment’s results depend on its hardware, licensing, workload, and recovery design; evaluate those specifics rather than assuming a universal saving or benchmark.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
