Co-authored with Thierry Fevrier, Amir Bredy, Danyal Bukhari, Jakub Szymaszek, Pam Lahoud
Introduction
Databases are the most valuable assets an organization has. They hold enterprise data, intellectual property, conversations, and institutional knowledge, making them the systems of record for AI. Trusted AI needs protection across the full data lifecycle, including training, inference, agents, and databases. Organizations need choices that protect data while it is being used and align with their sovereignty, operational, and application requirements.
Microsoft runs on trust, and we designed confidential computing to help protect against this end-to-end attack surface, whilst giving organizations options. A database on confidential computing has its memory encrypted and integrity protected inside a hardware-based trusted execution environment, helping protect data in use and isolate it from the host operating system, hypervisor, other tenants, and even cloud operators.
Databases on confidential computing provide a protected foundation across customer-managed cloud infrastructure, private environments, and managed services. They strengthen technical sovereignty by helping reduce infrastructure-operator access to data in use while giving organizations choices over residency, deployment model, infrastructure control, and key management.
Choose the model that fits your requirements
Start with the outcomes your organization needs: cloud or on-premises deployment, operational control or managed simplicity, SQL Server or PostgreSQL compatibility, and the regions and configurations required by the workload.
|
| |||
|
Consideration |
SQL Server in Local CVM |
PostgreSQL on CVM | |
|
State |
GA |
Preview |
GA |
|
Root of trust |
AMD SEV-SNP, Intel TDX |
AMD SEV-SNP, Intel TDX |
AMD SEV-SNP, Intel TDX |
|
Where it runs |
Azure Public and Gov |
Customer choice |
Azure Public and Gov |
|
Guest admin |
Customer |
Customer |
Microsoft |
|
Who manages it |
Customer managed |
Customer managed |
Microsoft managed |
|
Protection and keys |
Customer managed (with M-HSM) or platform managed |
Customer managed (with M-HSM) or platform managed |
Customer managed (with M-HSM) or platform managed |
|
Technology |
AMD SEV-SNP, Intel TDX |
AMD SEV-SNP, Intel TDX |
AMD SEV-SNP, Intel TDX |
|
Instance sizes |
V5, V6 (recommended) |
Hardware from HPE, Lenovo, |
V5, V6 (recommended) |
|
Regions |
60 (SEV-SNP), 5 (TDX) |
Not region dependent |
18 (SEV-SNP), 5 (TDX) |
|
Disk protection |
Confidential OS disk encryption, keys bound to the virtual TPM |
Confidential OS disk encryption, keys bound to the virtual TPM |
Confidential OS disk encryption, keys bound to the virtual TPM |
|
Guest OS |
SQL Server 2022 and 2025 confidential images (Windows Server) |
SQL Server 2025 self-install on Confidential VM (Ubuntu 24.04), WS coming soon. |
PostgreSQL versions supported by flexible server |
Option 1: SQL Server in Azure confidential VM
Choose SQL Server on an Azure confidential VM for the most direct path to a database on confidential computing. You retain familiar T-SQL tools and full control over SQL Server configuration while gaining hardware-enforced protection for data in use. Your team remains responsible for patching, backups, and high availability.
Option 2: SQL Server in Azure Local confidential VM
Choose SQL Server on an Azure Local confidential VM when workloads must remain on premises or in customer-controlled infrastructure. You control residency and operations while retaining familiar SQL Server practices and hardware-enforced protection for data in use. Your team manages the hosts, VM image, SQL Server, and backups.
Option 3: PostgreSQL flexible server on confidential VM
Choose Azure Database for PostgreSQL flexible server for a managed database on confidential computing. Given this offering is Microsoft managed, the trusted computing base is wider, however organizations get incremental defense in depth from neighboring tenants, with the benefits of running in a trusted execution environment. Confirm regional availability before planning a migration.
Availability
Availability depends on the selected product, region, VM family, image, subscription, and capacity. Before committing to an architecture, confirm the exact configuration in current Azure product documentation and the deployment experience.
- DCasv6, ECasv6, DCadsv6, ECadsv6 – Broadly Available across 50+ Regions
- DCesv6, ECesv6, DCedsv6, ECedsv6 – Accelerated I/O, Available in 5 Markets + Expanding
- Azure Local, in partnership with HPE, Lenovo and Dell, is also available for customers requiring hybrid on-prem
Demonstration for SQL Server
Learn more
- Deploy SQL Server in Azure with confidential computing
- Deploy SQL Server on Azure Local
- Deploy PostgreSQL in Azure with confidential computing
- GA: DCasv6 and ECasv6 confidential VMs based on 4th Generation AMD EPYC processors
- GA: DCesv6 and ECesv6 confidential VMs based on 5th Generation Intel Xeon processors