---
slug: "azure-sql-database-always-encrypted-intel-sgx-enclaves-retirement"
title: "Azure SQL Database: Always Encrypted with Intel SGX enclaves retirement"
summary: "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."
cloud: "azure"
service: "Azure SQL Database"
service_slug: "sql-database"
category: "feature"
type: "retirement"
announced_date: "2026-10-06"
effective_date: "2027-10-31"
effective_precision: "day"
replacement: "Virtualization-Based Security (VBS) enclaves"
affected_versions: []
source_url: "https://azure.microsoft.com/updates?id=569236"
extra_source_urls: []
vendor_ref: "569236"
last_checked_at: "2026-11-12T09:55:19.345Z"
created_at: "2026-11-13T13:36:44.208Z"
updated_at: "2026-11-13T13:36:44.208Z"
url: "https://eolwatch.dev/items/azure-sql-database-always-encrypted-intel-sgx-enclaves-retirement"
short_url: "https://eolwatch.dev/i/85"
markdown_url: "https://eolwatch.dev/items/azure-sql-database-always-encrypted-intel-sgx-enclaves-retirement.md"
json_url: "https://eolwatch.dev/items/azure-sql-database-always-encrypted-intel-sgx-enclaves-retirement.json"
source_note: null
---

# 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.

- Effective date: 31 Oct 2027
- Cloud: [Azure](https://eolwatch.dev/cloud/azure.md)
- Service: [Azure SQL Database](https://eolwatch.dev/services/azure/sql-database.md)
- Type: Retirement
- Category: [Feature](https://eolwatch.dev/categories/features.md)
- Replacement: Virtualization-Based Security (VBS) enclaves
- Announced: 6 Oct 2026
- Official source: [azure.microsoft.com](https://azure.microsoft.com/updates?id=569236)
- Last checked: 12 Nov 2026

## 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

1. Migrate from DC-series to a supported Standard-series (non-DC) compute tier.
2. Enable VBS enclaves for Always Encrypted. No attestation is required.
3. Update client drivers to versions that support VBS enclaves.
4. Update connection strings to remove SGX attestation parameters and use VBS enclave mode.
5. As an alternative, consider SQL Server on Confidential VMs.

## Replacement

Virtualization-Based Security (VBS) enclaves

## Sources

- [Official source](https://azure.microsoft.com/updates?id=569236) (azure.microsoft.com, Official)

Last checked against this source on 12 Nov 2026.

Page: https://eolwatch.dev/items/azure-sql-database-always-encrypted-intel-sgx-enclaves-retirement | JSON: https://eolwatch.dev/items/azure-sql-database-always-encrypted-intel-sgx-enclaves-retirement.json

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.