AzureRetirement
Azure SQL Database: Always Encrypted with Intel SGX enclaves retirement
Retirement date for Always Encrypted with Intel SGX enclaves in Azure SQL Database: 31 Oct 2027. After retirement, workloads using Intel SGX enclaves no longer have enclave functionality.
Retires , 31 Oct 2027
What breaks
After retirement, workloads using Intel SGX enclaves no longer have enclave functionality. Databases running on DC-series compute tiers should be migrated to supported compute tiers to continue using enclave-enabled features. Microsoft ties the retirement to the phase-out of support for SGX-enabled DC-series hardware.
What to do
- Migrate from DC-series to a supported Standard-series (non-DC) compute tier.
- Enable VBS enclaves for Always Encrypted. No attestation is required.
- Update client drivers to versions that support VBS enclaves.
- Update connection strings to remove SGX attestation parameters and use VBS enclave mode.
- As an alternative, consider SQL Server on Confidential VMs.
Replacement
Virtualization-Based Security (VBS) enclaves
Sources
- Official sourceazure.microsoft.comOfficial
Last checked against this source on .
Related
- , 1 Oct 2026Azure SQL Database: FSV2-series hardware retirementSource
- , 31 Mar 2027Azure SQL Database: Elastic query Shard_Map_Manager mode end of supportSource
- , 30 Sep 2027Azure SQL Database: SQL Data Sync retirementSource
- , 18 Aug 2026Microsoft Defender for Cloud: retirement in Azure operated by 21VianetSource
- , 14 Sep 2026Azure Functions: runtime version 1.x end of supportSource
- , 14 Sep 2026Azure Monitor: AKS-Engine monitoring retirementSource
Found an error? Report it
The text on this page is drafted with AI assistance from the vendor's text, checked against the official source and approved by a person before it is published. How items are written
Last checked · Added · Changelog for this item