A glowing checkmark certifies server and memory hardware in a futuristic data center, with database and analytics icons.
Azure's remote-storage-optimized memory VMs, Ebsv6 and Ebdsv6, are now generally available. That is a meaningful step for anyone running storage-hungry databases on Azure. One caveat: the biggest sizes aren't here yet, and Microsoft's own figures don't fully agree with each other.

A glowing checkmark certifies server and memory hardware in a futuristic data center, with database and analytics icons. What Microsoft launched​

Microsoft's Azure Updates entry carries the "Launched" label, which the page defines as fully released and production-ready for all Azure customers. The details come from Microsoft's Azure Compute blog GA announcement of November 13, 2026. I couldn't open that post directly, so the figures below are the ones Microsoft published in that announcement and its preview post.

Both series are memory-optimized and built for high remote-disk throughput. They run on 5th-generation Intel Xeon Platinum 8573C (Emerald Rapids) processors with Azure Boost. Microsoft positions the Ebsv6 as purpose-built for memory-intensive workloads such as relational database servers, large-scale data warehousing, and advanced analytics.

The two series differ in one respect:

  • Ebsv6 has no local temporary disk.
  • Ebdsv6 includes local NVMe temporary disks.

Either way, you can attach remote persistent disks such as Premium Disk v1, Premium Disk v2, or Ultra Disks. Local temp storage is ephemeral, so don't treat it as durable storage.

The numbers, with caveats​

Microsoft's published comparisons are against the previous Ebsv5 generation. They are "up to" figures, not guarantees:

  • Up to 15% higher remote-storage performance per vCPU, at up to 6,600 IOPS per vCPU.
  • Up to 10% higher remote-storage throughput per vCPU.
  • Up to 15–30% better CPU performance.
  • Up to 800,000 IOPS with Premium SSD v2 and Ultra Disk.
  • Up to 200 Gbps of network bandwidth.
  • Enhanced security through Intel Total Memory Encryption (TME), which Microsoft says is on by default.

TME protects data in system memory. It does not replace disk encryption, network controls, or application-level security.

Two throughput figures that disagree​

The GA blog gives a maximum of 12,500 MB/s of remote throughput. The preview post, and Microsoft Learn's series pages, list a range of 330 to 14,000 MB/s. I can't tell from the evidence which figure is authoritative. Check the current Learn size tables for the exact size you plan to deploy. Disk type and configuration also cap what you actually get.

Biggest sizes come later​

The series is listed at 2–192 vCPUs and 16–1,832 GiB of memory. Microsoft's GA announcement says the 128- and 192-vCPU sizes are expected in Q1 calendar 2027. Today's scalable configurations top out at 96 vCPUs and 768 GB. If your sizing plan assumes the top end, build in a fallback.

Where it's available​

The preview was limited to US East. The GA announcement lists a much wider footprint of more than 50 regions, including:

  • North America: East US, East US 2, Central US, West US, West US 2, West US 3, Canada Central.
  • Europe: West Europe, North Europe, UK South, Germany West Central, Sweden Central, Switzerland North.
  • Asia-Pacific: Japan East, Southeast Asia, Australia East, Korea Central.
  • Middle East and Africa: UAE North, South Africa North.

That list is a snapshot, and availability can also vary by size. Confirm your region and size combination in the portal before you commit to an architecture.

Who should care​

If you're on Ebsv5 and your database is bottlenecked on remote-disk IOPS or throughput, this is the obvious upgrade to evaluate. If your workload is CPU- or memory-bound, the standard E-family v6 series may fit better. Microsoft's size overview describes the Eb family as the E-family with high remote storage performance.

A sensible evaluation path:

  1. Measure where your current Ebsv5 workload is bound: IOPS, throughput, memory, or CPU.
  2. Choose the disk type. The headline IOPS figures assume Premium SSD v2 or Ultra Disk.
  3. Check that the exact VM size is available in your region.
  4. Benchmark with your own workload and compare cost with Azure's pricing page.

Microsoft's percentages are vendor comparisons, not independent benchmarks. Treat them as a reason to test, not a promise.

Bottom line​

This is a solid, practical GA for Azure database and analytics shops. The 15% per-vCPU gain is incremental, not revolutionary. The wide regional rollout and the NVMe interface are the more useful news. Watch for the Q1 2027 arrival of the 128- and 192-vCPU sizes, and verify the throughput ceiling for your size before you design around it.

 

References

  1. (Launched) Generally Available: Azure Ebsv6 and Ebdsv6 Azure Updates 2026-11-17T20:00:32Z
  2. Announcing the Preview of the new Azure Ebsv6 VMs based on the 5th Gen Intel® Xeon® processor | Microsoft Community Hub techcommunity.microsoft.com
  3. Virtual machine sizes overview - Azure Virtual Machines learn.microsoft.com