Several Microsoft sources describe the change. They don't cover everything a database owner would want to know before moving a workload, so this piece also lists what is still unconfirmed.
What Microsoft announced
Microsoft's Ignite 2026 Book of News says Cobalt 200, now generally available for Azure Database for PostgreSQL, adds Microsoft-designed Arm64-based compute alongside Intel and AMD x64-based options. So Postgres customers now have an Arm option next to the x86 choices.
The Azure Database for PostgreSQL team's Ignite post says the service now supports the Azure Cobalt 200 VM SKU, using Microsoft's custom Arm-based processor built around the Arm Neoverse V3 Compute Subsystems. It describes this as a new price-performance option for Postgres.
The same post says initial testing has shown outstanding performance compared to similar x86-64 SKUs, particularly for in-memory analytical workloads. That is a qualitative claim. It comes with no numbers, no workload description and no named baseline SKUs.
How this fits into the wider Cobalt 200 launch
The PostgreSQL news sits inside a larger announcement. Microsoft's Azure blog says Cobalt 200 VMs are now generally available. The blog says they deliver up to 50% better CPU performance compared to our Cobalt 100 VMs. The blog's authors say the VMs are available in 14 regions, expanding to 23 by the end of 2026. Microsoft's Book of News gives a slightly different figure, saying planned for 24 Azure regions by year-end. Treat the year-end region count as approximate.
The blog also says at Microsoft Build 2026, we announced the availability of Azure Database for PostgreSQL on Cobalt 200. The Ignite item therefore appears to be the general-availability milestone for something first announced earlier. The exact earlier availability stage isn't spelled out in the material I reviewed.
Microsoft's database-related claims for Cobalt 200 are all VM-level:
- Benchmarks: Microsoft's benchmarking showed up to 1.5x for web serving and 1.6x for Java workloads. For database workloads the figure was 1.9x, all against Cobalt 100. These are VM benchmarks, not measurements of managed PostgreSQL.
- Storage and networking: Azure Boost is included in every Cobalt 200 VM. Microsoft quotes up to 15% higher network bandwidth, 20% higher remote storage IOPS and 10% higher remote storage throughput than Cobalt 100.
- Silicon: The chip has 132 Arm Neoverse V3 cores. Each vCPU maps to a full physical core. There are 12 DDR5 memory channels, and memory encryption is on by default.
- Operating modes: Cobalt 200 VMs support a deterministic 3.2 GHz mode and an opportunistic mode that boosts up to 3.6 GHz. Microsoft says the boost mode gives up to 12% more performance with some frequency variability. The blog describes a
ProcessorModesetting for VMs. Nothing I found says PostgreSQL customers can set it.
The 1.9x database figure is not a PostgreSQL result, and it compares against the previous Arm generation. It says nothing about Arm versus Intel or AMD.
What is still unconfirmed
The sources I could review don't answer the questions a DBA would ask first:
- Tiers and sizes: Microsoft doesn't say which tiers (Burstable, General Purpose or Memory Optimized), vCore counts or memory sizes the Cobalt 200 option offers.
- Regions: The 14-region list covers Cobalt 200 VMs. It is not confirmed as the PostgreSQL availability list.
- Versions: No supported PostgreSQL major versions are stated for the Cobalt 200 option.
- Pricing: No price is given beyond the "price-performance option" framing.
- Migration: There is no documented procedure for moving an existing server to Cobalt 200, and no statement on downtime.
- Documentation lag: The Microsoft Learn compute-options page was last updated July 9, 2026. In the version I reviewed it lists Burstable, General Purpose and Memory Optimized tiers built on Intel- and AMD-style series such as Ddsv6 and Edsv6, with no Cobalt 200 series. That looks like documentation lag, not a contradiction of the announcement. Still, it means you can't yet check SKU names against the docs.
Don't assume existing servers will move to Cobalt 200 automatically. Nothing published says so.
Practical guidance for PostgreSQL operators
- Check the portal first. In the server-creation experience, check whether an Arm-based Cobalt 200 option appears for your region and tier. The Learn page notes that the portal shows an estimate of monthly costs while you configure a server, so you can compare prices there. Use the portal pricing estimate, not the VM blog, for cost.
- Test before you move. Arm64 is a different architecture from the x86 servers many teams run today. The database engine is managed, but check extensions, client-side tooling and anything else tied to your server setup. This is general industry advice, not something the sources say.
- Benchmark your own workload. Microsoft's own wording points to in-memory analytical workloads as the strongest case. Transactional, write-heavy or I/O-bound workloads may behave differently, and your storage tier still caps IOPS.
- Keep storage in view. The Learn compute page stresses that the storage tier sets minimum and maximum IOPS. A faster CPU won't help a workload that is limited by disk.
- Watch the release notes. The service release notes were last updated in August 2026 and list minor-version support, with no Cobalt entry yet. I would expect SKU and region details to appear there or in the compute docs.
Why it matters
Microsoft has been moving its own services onto Cobalt. The Cobalt 200 blog says Azure Database for PostgreSQL, Azure SQL, Azure DevOps, Microsoft 365 and Xbox run on Cobalt VMs. Offering the same silicon to PostgreSQL customers continues that pattern. Vendor cost and efficiency claims deserve the usual skepticism until independent benchmarks appear. Even so, a managed Postgres option on Arm is worth a test run, especially if you already run Arm workloads elsewhere in Azure.
For now, this is a confirmed production-ready option with limited public detail. The Cobalt 200 VM story is well documented. The PostgreSQL-specific details of tiers, regions, pricing and migration are not.
References
- (Launched) Generally Available: Cobalt 200 compute for Azure Database for PostgreSQL Azure Updates · 2026-11-17T23:50:40Z
- Azure Cobalt 200 VMs: Faster compute for modern agentic workloads azure.microsoft.com
- Compute Options - Azure Database for PostgreSQL | Microsoft Learn learn.microsoft.com