Azure launches VM series powered by Cobalt 100 ARM processors
Microsoft Azure has launched VM series powered by its custom Cobalt 100 ARM processors, targeting general-purpose and compute-optimized workloads. Preview benchmarks show up to 40% better price-performance compared to equivalent x86 instances for web servers, containerized applications, and open-source databases.
Cobalt 100 specs
Cobalt 100 is based on the ARM Neoverse N2 architecture, offering 128 cores per processor with 12-channel DDR5 memory and PCIe 5.0 support. Azure's initial offerings include the general-purpose Dpsv6 and compute-optimized Fpsv6 series, covering web services, microservices, API gateways, and batch processing.
ARM ecosystem maturity
With rapid ARM ecosystem growth, mainstream Linux distributions, Node.js, Python, Java, Go, and .NET all provide excellent ARM64 support. For new projects or containerized applications, ARM instances require minimal adaptation effort.
16IDC Takeaway
All three major cloud providers now offer custom ARM instances — AWS Graviton, Azure Cobalt, and Google Axion. For site owners and SaaS teams, ARM should be a default evaluation option in the next instance selection round.
Background: Microsoft's Custom Silicon Strategy Takes Shape
Cobalt 100 is Microsoft's custom ARM server processor, based on the ARM Neoverse N2 architecture. Its launch marks Microsoft's official entry into the "cloud provider custom ARM processor" club — directly competing with AWS Graviton and Google Axion.
Microsoft's chip strategy has been building for years — from Xbox custom silicon, to Surface SQ processors, to Azure's Maia 100 AI accelerator. Cobalt 100 targets general-purpose computing, aiming to reduce Azure's operational costs while offering customers higher value compute options.
Notably, Cobalt 100 uses a 128-core design — the highest core count among the three cloud ARM processors. This provides a clear advantage for multi-threaded and parallel general-purpose workloads.
Practical Impact for Site Builders
Cobalt 100 vs x86 Comparison
| Dimension | Dpsv6 (Cobalt 100) | D-series (Intel Xeon) | Difference |
|---|---|---|---|
| Price/Performance | ★★★★★ | ★★★☆☆ | Up to 40% better |
| Software Compatibility | ★★★★☆ | ★★★★★ | Most OSS supports ARM |
| Memory Config | 12-channel DDR5 | 8-channel DDR5 | Better bandwidth |
| Best Workloads | Web services, containers, OSS DBs | Enterprise, legacy systems | Different strengths |
Best Candidates for Migration
- Web servers and API gateways: Nginx, Apache, Caddy — excellent ARM support
- Containerized apps: Docker/Kubernetes ARM64 support is mature; just swap base images
- Open-source databases: MySQL, PostgreSQL, Redis perform well on ARM
- CI/CD pipelines: Build and test tasks run well on ARM at lower cost
Not Yet Suitable
- Windows Server workloads (ARM Windows support still maturing)
- Closed-source commercial software without ARM versions
- Tasks with deep x86 instruction dependencies
Actionable Recommendations
- Start with new projects: Avoid migration costs by choosing Cobalt 100 for new launches
- Containerize first: If not yet containerized, do that before migrating to ARM to abstract architecture differences
- Use Azure migration assessment: Azure Migrate offers ARM compatibility scanning tools
- Compare TCO: Run real-world cost comparisons between Cobalt 100 and Intel/AMD instances
- Check regional availability: Cobalt 100 may launch in select regions first
Deeper Perspective
The three-way ARM competition — AWS Graviton, Azure Cobalt, Google Axion — is reshaping cloud cost structures. For users, this is extremely favorable: more choices mean stronger bargaining power and faster innovation.
However, ARM migration is no silver bullet. While price-performance improvements are attractive, migration costs, compatibility testing, and team learning curves must factor into TCO calculations. Take a "gradual migration" approach — start with non-critical workloads and expand ARM usage over time.
Source: Microsoft Azure Blog