Blog Post

SQL Server Blog
4 MIN READ

Strengthen SQL Server security on Azure Local with confidential VMs (In Preview)

Attinder_Pal_Singh's avatar
Nov 17, 2026

SQL Server holds some of the most sensitive data an organization runs, including the business data that local AI applications and agents query. Azure Local provides a Microsoft-managed, distributed infrastructure platform for running SQL Server in virtual machines at customer locations, so data can stay on premises. Data at rest and in transit is commonly protected, but while SQL Server processes queries, the data it works with sits in memory. Confidential virtual machines (CVMs) on Azure Local help protect it there.

Protecting SQL Server requires more than securing the database engine. With a standard VM, the host operating system, the hypervisor, and anyone with administrative access to the host all sit inside the trust boundary of the workload. At edge and remote sites with less physical control, that is a lot of trust to place in the infrastructure.

CVMs on Azure Local, now generally available on AMD processors and in preview on Intel processors, bring hardware-based memory encryption and attestation to customer-owned edge infrastructure. They provide hardware-based isolation between the VM, the hypervisor, and host management code. SQL Server 2025 runs on Ubuntu 24.04 inside the CVM.

For SQL Server workloads, the value is straightforward: help keep data confidential while it is in use, even from the infrastructure it runs on.

Where confidential VMs fit 

Consider CVMs when SQL Server data should stay private from the people and systems that operate on the underlying infrastructure, such as regulated and sovereign data, edge and remote sites, hosted or partner-run clusters, and local AI applications that query sensitive business data.

Protect SQL Server data while it is in use

CVMs on Azure Local use AMD SEV-SNP or Intel TDX to encrypt guest memory in hardware, so SQL Server's buffer pool and in-memory data stay encrypted and isolated from the host and its administrators. CVMs don't protect against sophisticated physical side-channel attacks, so pair them with physical safeguards at the site.

Data on disk, in backups, and in transit still needs SQL Server's own protections. The following table shows how they fit together.

What you're protecting 

Threat 

Protection 

SQL Server memory, including the buffer pool 

Host administrators or a compromised host 

CVM memory encryption (AMD SEV-SNP or Intel TDX) 

Operating system disk and boot chain 

Host-side tampering 

Integrity-protected image 

Data, log, and tempdb files 

A copy of the data disk taken from the host 

TDE with keys in Azure Key Vault 

Backups 

Copies stored outside the VM 

Backup encryption 

Network traffic 

Interception between clients and SQL Server 

Encrypted connections (TLS) 

Sensitive columns 

Privileged database users 

Always Encrypted 

Start from an integrity-protected image

CVMs follow a clean-room, image-driven model. You build a hardened Ubuntu 24.04 image with SQL Server 2025 installed and enable integrity protection, which helps protect the guest operating system disk and boot chain from host-side tampering. The root file system is read-only, so SQL Server databases, logs, and tempdb live on a separate writable data disk.

To maintain the security boundary, guest management isn't supported, so plan guest changes, including SQL Server updates, as new image builds rather than in-place changes.

Plan availability around confidential VMs

CVMs don't support live migration or failover between nodes in an Azure Local cluster, so plan maintenance around the CVMs on each node, build availability into the database design, and keep regular SQL Server backups outside the VM.

Verify the environment with attestation

Attestation helps you confirm that SQL Server is running in a genuine confidential environment before you trust it with sensitive data. The CVM produces a hardware-rooted attestation report that Microsoft Azure Attestation validates, so plan cloud connectivity from the site.

Get started with SQL Server on confidential VMs

  1. Prepare a CVM-ready cluster. Deploy Azure Local 2607 or later on validated AMD or Intel hardware with confidential VMs enabled by following the Azure Resource Manager template guidance. Hardware partners for both include Dell, HPE, and Lenovo. Find specific validated systems in the Azure Local solutions catalog.
  2. Build the SQL Server image. Use the integrity-protected CVM image builder in the AzureStack-Tools repository to create an Ubuntu 24.04 image, add SQL Server 2025, and point SQL Server at a separate data disk.
  3. Create the confidential VM. Create the CVM from your image with the data disk attached by following the CVM creation and connection guidance.
  4. Verify and connect. Verify the CVM with attestation and connect your applications. For detailed guidance, see Deploy SQL Server on Azure Local.

Review the confidential VM overview for current limitations.

Frequently asked questions 

How is this different from Always Encrypted? 

Always Encrypted protects selected columns from anyone without the column keys, including database administrators. A CVM protects all of SQL Server's memory from the host and infrastructure operators. They address different threats, so use both when you need protection from both groups.  

Can I convert an existing VM into a confidential VM? 

No. CVMs are created from a purpose-built, integrity-protected image. Create a new CVM and move your databases into it with backup and restore. 

Does it support SQL Server on Windows? 

Not yet. This release supports Ubuntu 24.04 guests only. 

A stronger foundation for sensitive database workloads

When SQL Server runs in a confidential VM on Azure Local, its memory is encrypted and isolated from the host, the hypervisor, and infrastructure operators, and attestation provides evidence of that protection before applications connect. That brings confidential computing to SQL Server workloads that need to stay on premises.

Published Nov 17, 2026
Version 1.0
No CommentsBe the first to comment