Azure’s Intel Xeon 6 Dlsv7, Dsv7, and Esv7 VMs reach GA

Azure made Dlsv7, Dsv7, and Esv7 virtual machines based on Intel Xeon 6 processors generally available. The Compute announcement describes three memory-to-vCPU profiles, sizes reaching 192 vCPUs at launch, Azure Boost, the Microsoft Azure Network Adapter, NVMe remote disks, and local NVMe options on variants whose names include “d.”

A new family is a measured migration

VM generations differ in more than nominal core count. CPU behavior, NUMA layout, disk interfaces, network drivers, local storage, and regional size availability can all affect a workload. Microsoft published performance comparisons, but those vendor results do not predict a particular application’s latency or cost.

The three families give teams a way to align memory density with general compute or memory-heavy services. Optional local NVMe is useful for disposable caches and scratch data, provided the workload tolerates loss during host events.

Benchmark the whole service

Confirm the exact size exists in every required region and zone. Use a production-like image with current MANA and NVMe support, then compare request latency, throughput, CPU saturation, memory pressure, disk queues, and network behavior against the incumbent size.

Exercise restart, redeploy, and scale-out paths. Any data on local NVMe needs a rebuild procedure and clear monitoring. Review quotas and capacity before scheduling a fleet migration; general availability does not guarantee a chosen size is immediately allocatable in every zone.

Roll out by workload slice and retain a rollback size until telemetry stabilizes. Evaluate performance per unit of actual billed capacity using your own traffic, without assuming a published maximum or benchmark gain applies universally.