CuraDevOps

tag: Vm-Retirement · 3 items

Plan archived Azure DCsv3/DCdsv3 VMs retire October 31, 2029
2026-10-02 · Azure Updates · source ↗ #azure#vm-retirement#migration
  • Platform/SRE — Plan: If you run DCsv3 or DCdsv3-series VMs in production, plan migration to a supported confidential compute series before October 31, 2029; the deadline is distant but inventory and migration scoping should enter the backlog now.
  • CI/CD — Skip
  • Leader — Skip
  • Signals: deprecation/EOL deadline mentioned: October 31, 2029
Act archived Azure NVv4-series VMs retired as of September 30, 2026
2026-10-01 · Azure Updates · source ↗ #azure#vm-retirement#gpu
  • Platform/SRE — Act: The NVv4-series VM SKUs were decommissioned on 2026-09-30 — any workloads or node pools still using these SKUs are now unsupported; migrate to a current GPU-capable series (e.g. NVadsA10 v5) immediately.
  • CI/CD — Skip
  • Leader — Skip
  • Signals: deprecation/EOL deadline mentioned: September 30, 2026
Act archived Azure NVv3-series GPU VMs retired September 30, 2026
2026-10-01 · Azure Updates · source ↗ #azure#vm-retirement#gpu
  • Platform/SRE — Act: The NVv3-series retirement deadline was September 30, 2026 — audit all Azure subscriptions immediately for remaining NVv3 instances and migrate to NVv4 or NVadsA10 v5 series before Azure force-deallocates any remaining VMs.
  • CI/CD — Skip
  • Leader — Skip
  • Signals: deprecation/EOL deadline mentioned: September 30, 2026