SaaS
Microsoft
Microsoft will retire the Azure DCsv3 and DCdsv3-series confidential-computing virtual machines (Linux, Windows, and Dedicated Host) on 31 October 2029; after that date they can no longer be used or purchased, and workloads must move to the v6 confidential VM series or Confidential Container Instances.
departs 31 Oct 2029
Quick answers
- Is it true that Azure will retire the DCsv3 and DCdsv3-series confidential-computing VMs on 31 October 2029 — migrate to DCasv6/DCesv6 or Confidential Container Instances?
- Yes. Microsoft has officially announced it, effective 31 Oct 2029. The DCsv3 and DCdsv3-series are Azure's Intel SGX-based confidential-computing VMs — used for workloads that need hardware-isolated, encrypted-in-use enclaves (sensitive data processing, key management, multi-party computation, regulated workloads).
- When does it take effect?
- 31 Oct 2029. Verified against the vendor's own announcement.
- What should I use instead?
- Microsoft's recommended targets depend on the workload model.
What this means for you
The DCsv3 and DCdsv3-series are Azure's Intel SGX-based confidential-computing VMs — used for workloads that need hardware-isolated, encrypted-in-use enclaves (sensitive data processing, key management, multi-party computation, regulated workloads). Microsoft will retire the series on **31 October 2029**, after which these VMs can no longer be used or purchased, across Linux, Windows, and Azure Dedicated Host deployments. The date is three years out, so there is no immediate action — but confidential-computing workloads tend to carry attestation, key-release, and compliance dependencies tied to a specific CPU technology (SGX enclaves here), which makes migrating them more involved than a routine VM resize. For large or regulated fleets this is multi-year capacity and re-validation planning, not a late-2029 scramble.
Where to go
Microsoft's recommended targets depend on the workload model. For VM-based confidential computing, move to the **v6 confidential VM series** — DCasv6 / DCadsv6 / DCesv6 / DCedsv6, or the memory-optimized ECasv6 / ECadsv6 / ECesv6 / ECedsv6 — which use newer confidential-computing technologies (AMD SEV-SNP and Intel TDX) rather than the SGX enclave model of the DCsv3 generation. For containerized workloads, Microsoft points to **Azure Confidential Container Instances (C-ACI)** or confidential **virtual nodes on Azure Kubernetes Service**. Because the underlying confidential-computing technology differs between generations, plan to re-validate attestation flows, secure key release, and any SGX-enclave-specific code against the SEV-SNP/TDX model before cutting over — this is the part that needs lead time, not the VM redeployment itself.
- Azure DCasv6 / DCadsv6 / DCesv6 / DCedsv6 confidential VMs (AMD SEV-SNP / Intel TDX) — current-generation confidential computing VMs
- Azure ECasv6 / ECadsv6 / ECesv6 / ECedsv6 — memory-optimized confidential VMs
- Azure Confidential Container Instances (C-ACI) or confidential virtual nodes on AKS — for containerized confidential workloads
Microsoft will retire the Azure DCsv3 and DCdsv3-series confidential-computing virtual machines on 31 October 2029. Per the official Azure retirement notice, after that date these VMs “will no longer be available for use or purchase,” across Linux, Windows, and Azure Dedicated Host.
What is being retired
The DCsv3/DCdsv3 series are Azure’s Intel SGX-based confidential-computing VMs — built for workloads that need hardware-isolated, encrypted-in-use enclaves: sensitive-data processing, key management, multi-party computation, and regulated workloads that must keep data protected even from the host. This is a standard VM-lifecycle retirement with a long runway, not an imminent cutoff.
Where Microsoft points you
- VM-based confidential computing: the v6 confidential VM series — DCasv6 / DCadsv6 / DCesv6 / DCedsv6, or memory-optimized ECasv6 / ECadsv6 / ECesv6 / ECedsv6. These use AMD SEV-SNP and Intel TDX rather than the SGX enclave model of the DCsv3 generation.
- Containerized confidential workloads: Azure Confidential Container Instances (C-ACI) or confidential virtual nodes on AKS.
Why to start before 2029
The date is three years out, so nothing breaks soon. But confidential computing is the one VM category where “just resize it” rarely holds: these workloads carry attestation, secure-key-release, and compliance dependencies tied to the specific CPU technology — SGX enclaves on DCsv3, versus SEV-SNP/TDX on the v6 series. Re-validating those flows and any enclave-specific code is the part that needs lead time. For large or regulated fleets, treat this as multi-year planning that happens to have a 2029 deadline.
Entry changelog
- — last reviewed.
- — Entry created from Microsoft's official Azure Updates retirement notice (id 569592, published 1 October 2026). The Azure Updates page is JavaScript-rendered and does not fetch server-side, so the retirement date (31 October 2029), the affected series (DCsv3 and DCdsv3 across Linux/Windows/Dedicated Host), and the recommended migration targets (DCasv6/DCadsv6/DCesv6/DCedsv6, ECasv6/ECadsv6/ECesv6/ECedsv6, Confidential Container Instances, confidential virtual nodes) were verified against Microsoft's server-rendered release-communications API (id 569592). Dates recorded exactly as stated; no inference. No detect: fingerprint — the notice names the series, not concrete Standard_DC*_v3 size strings, so (per the cc_v5 / Dv3 precedent in SOURCING §6) fingerprinting a family would misfire; added only when a notice names the concrete sizes.
Put this countdown in your README
Building on Microsoft? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page. 
[](https://lastcall.dev/entries/azure-dcsv3-dcdsv3-vm-series-retirement)Spot an error or a changed date? Tell us and it’s corrected the same night.