A remote site’s database needs to keep working even when its cloud connection fails.
Microsoft announced on September 28 that SQL Server on Azure Local is generally available for connected and disconnected operations. The release gives organizations with restricted or unreliable connectivity another deployment option for databases that need to remain on their own infrastructure.
For IT teams, the decision involves more than where to store data. Running disconnected also means planning for local management, infrastructure capacity, licensing, and recovery.
How connected and disconnected deployments differ
Azure Local runs on customer-managed infrastructure in datacenters and edge locations. Microsoft says SQL Server workloads can run in Windows Server or Linux virtual machines on that infrastructure.
Connected deployments can use Azure Arc to manage SQL Server resources through Azure. Azure Local Disconnected Operations, or ALDO, supports environments where external connectivity is restricted, intermittent, or unavailable.
Microsoft’s disconnected operations documentation explains that the platform uses a local control plane to deploy and manage workloads without a connection to the Azure public cloud. Administrators get a familiar Azure portal and command-line experience within that environment.
That adds a deployment choice for organizations weighing hybrid cloud architecture: decide which sites can use cloud management and which require management to stay local.
Disconnected operations require additional planning
Microsoft’s documentation identifies remote industrial locations and organizations with sovereignty or regulatory requirements as potential users. Keeping management local can address an operational requirement that storing databases locally alone does not resolve.
However, disconnected operations require additional capacity to host the local control plane and a dedicated management cluster. Microsoft specifies Premier Solutions for Azure Local as the supported hardware category.
Access also has eligibility conditions. Organizations need an eligible Microsoft agreement, an active Standard-or-higher Microsoft support plan or a partner with an active support plan, a valid business need to operate disconnected, and staff or a partner capable of deploying and operating the environment. Microsoft directs prospective customers to work with their account team to obtain access.
For buyers, the implication is to assess the entire operating environment. Hardware, administrative access, support arrangements, and data sovereignty controls all belong in that assessment.
SQL Server licensing remains separate
Microsoft says SQL Server is licensed separately from Azure Local. Connected deployments can use eligible existing SQL Server licenses, including qualifying subscriptions or licenses with Software Assurance, or pay-as-you-go licensing through Azure Arc.
Fully disconnected deployments can use eligible existing SQL Server licenses through Azure Hybrid Benefit. Teams should confirm eligibility before building a budget around license reuse.
Deployment planning should also include a review of Microsoft’s product support deadlines, particularly when moving an older database estate. Infrastructure changes and database lifecycle decisions need to be assessed together.
Local AI remains in preview
Microsoft also points to Foundry Local on Azure Local as an option for running AI models near SQL Server data. That offering remains in preview, separate from SQL Server on Azure Local’s general availability.
Foundry Local documentation describes AI inference on an Arc-enabled Kubernetes cluster, with data processing kept on premises. Preview deployment access is currently available by request, and capabilities may change before general availability.
IT teams considering that option should evaluate the preview’s hardware and operating requirements separately from the production database deployment.
What IT teams should check before deploying
Start by identifying which applications must remain usable without external connectivity, including their dependencies on authentication and other services. Then confirm the disconnected platform’s eligibility, hardware requirements, and SQL Server licensing terms.
Recovery needs its own design. Microsoft’s workload resiliency guidance says SQL Server on Azure Local requires a strategy combining host protection with database-native high availability and disaster recovery. It recommends regular backups and restoration tests.
For a disconnected site, the practical test is whether administrators can operate and recover the database using the resources available inside that environment. General availability provides a deployment option; a tested operating plan determines whether it meets the site’s needs.
Read more: Microsoft’s emergency Windows update fixes Remote Desktop failures and shared-folder problems in certain Hyper-V-based Linux environments.