SQL Server on Azure Local GA for Edge and Sovereign

Introduction

Microsoft has made SQL Server on Azure Local generally available, giving organizations a new option to modernize database workloads without requiring them to move data to the public cloud. This is especially important for regulated, sovereign, edge, and remote environments where connectivity, latency, or data residency rules limit where workloads can run.

What’s new

General availability for connected and disconnected deployments

Organizations can now run SQL Server on Azure Local in two models:

• Connected deployments: Run SQL Server locally while using Azure Arc to manage SQL Server resources through Azure.
• Disconnected deployments: Support operations in environments with restricted, intermittent, or no external connectivity through Azure Local Disconnected Operations (ALDO).

This flexibility lets IT teams choose the right operating model for each site instead of standardizing on a single connectivity approach.

Built for sovereign, regulated, and edge scenarios

Microsoft is positioning SQL Server on Azure Local for customers that need tighter control over infrastructure and data placement, including:

• Public sector and defense
• Financial services
• Healthcare
• Manufacturing and energy
• Remote or connectivity-constrained sites

The platform supports SQL Server workloads on virtual machines running Windows Server or Linux in customer-owned datacenters and edge locations.

AI closer to the data

Microsoft also highlighted Foundry Local on Azure Local, currently in preview. This allows organizations to run AI models alongside SQL Server on local infrastructure, helping teams explore AI inferencing without moving sensitive data off-premises.

Why this matters for IT admins

For database and infrastructure administrators, this release expands hybrid deployment options for SQL Server while maintaining operational control. Teams can modernize infrastructure with Azure-consistent tooling, keep workloads running locally when internet access is unreliable, and support compliance requirements around sovereignty and residency.

Licensing flexibility is also a key benefit:

• Connected deployments can use eligible existing SQL Server licenses or pay-as-you-go licensing through Azure Arc.
• Fully disconnected deployments can use eligible licenses through Azure Hybrid Benefit.

Next steps

IT teams evaluating this release should:

1. Identify SQL Server workloads with sovereignty, latency, or offline operation requirements.
2. Review whether connected or disconnected Azure Local deployments are the best fit per site.
3. Validate existing SQL Server licensing eligibility for Azure Arc or Azure Hybrid Benefit.
4. Review Microsoft Learn guidance for deployment, monitoring, performance tuning, and high availability.
5. Track Foundry Local if local AI inferencing is part of your roadmap.

SQL Server on Azure Local gives enterprises a practical hybrid path for mission-critical databases that need to stay close to the business, the application, and the data.