E96s_v5
The 'E' family of VM size series are one of Azure's memory-optimized VM instances.
The E96s_v5 is a azure vm instance type featuring multiple vCPUs and optimized memory, commonly used for vm workloads.
Last updated at Thu Apr 30 2026
Instance Info
| Compute | Value |
| vCPUs | 96 |
| Memory (GB) | 672 |
| CPU Architecture | x64 |
| Capacity Support | True |
| VM Generations | V1,V2 |
| VM Deployment Types | IaaS |
| Network | Value |
| Accelerated Networking | True |
| Storage | Value |
| Local Temp Storage (MB) | 0 |
| Cache/Temp Storage Throughput (IOPS) | 450000 |
| Cache/Temp Storage Read/Write Throughput (Bytes/s) | 4000000000 |
| Uncached Disk Throughput (IOPS) | 80000 |
| Uncached Disk Read/Write Throughput (Bytes/s) | 2600000000 |
| Premium I/O | True |
| Encryption | True |
| Memory Maintenance | True |
Family Instances
| Instance | vCPUs | Memory |
|---|---|---|
| E2s_v5 | 2 | 16 |
| E4-2s_v5 | 4 | 32 |
| E4s_v5 | 4 | 32 |
| E8-2s_v5 | 8 | 64 |
| E8-4s_v5 | 8 | 64 |
| E8s_v5 | 8 | 64 |
| E16-4s_v5 | 16 | 128 |
| E16-8s_v5 | 16 | 128 |
| E16s_v5 | 16 | 128 |
| E20s_v5 | 20 | 160 |
| E32-16s_v5 | 32 | 256 |
| E32-8s_v5 | 32 | 256 |
| E32s_v5 | 32 | 256 |
| E48s_v5 | 48 | 384 |
| E64-16s_v5 | 64 | 512 |
| E64-32s_v5 | 64 | 512 |
| E64s_v5 | 64 | 512 |
| E96-24s_v5 | 96 | 672 |
| E96-48s_v5 | 96 | 672 |
| E96s_v5 | 96 | 672 |
Related Instances
| Instance | vCPUs | Memory |
|---|---|---|
| E96-24ads_v5 | 96 | 672 |
| E96-24ads_v6 | 96 | 672 |
| E96-24as_v5 | 96 | 672 |
| E96-24as_v4 | 96 | 672 |
| E96-24ds_v5 | 96 | 672 |
21 Practical Azure Cost Optimization Techniques To Implement Today
Discover over 21 Azure cost optimization best practices you can implement now to reduce spending and maximize your cloud ROI.
Read more
Azure Vs. AWS Pricing: The Ultimate 2025 Guide
Choosing the right cloud provider can save you thousands of dollars. We breakdown AWS vs. Azure pricing so you choose what is right for you.
Read more
A Guide To Azure Database Pricing (And Reducing Costs)
Confused by Azure database pricing? We explain how it works and share tips to optimize costs across SQL, Cosmos DB, PostgreSQL, and beyond.
Read more