PostgreSQL on Azure: What Works and What Doesn't

One Service That Matters Now

Azure’s PostgreSQL story used to be confusing — there were two products with similar names. That is over. The one to build on is Azure Database for PostgreSQL — Flexible Server. The older Single Server is on a retirement path, so if you are migrating from Oracle today, Flexible Server is the answer and the rest of this is about what it does and doesn’t do well.

What Works Well

• Zone-redundant HA — a hot standby in another availability zone with automatic failover, conceptually like RDS Multi-AZ.
• Stop/start compute — pause a non-prod server and stop paying for compute, which RDS does not do as cleanly. Great for dev/test.
• Real config control — server parameters are broadly exposed, and a decent extension list including PostGIS, pg_stat_statements, and pgvector.
• Entra ID integration — native Azure AD authentication, which enterprises on the Microsoft stack value.
• Same community PostgreSQL — no fork, so your SQL and data stay portable.

What to Watch

The rough edges are mostly around read scaling and ecosystem maturity, not core reliability.

• Read replicas exist but have historically been less flexible than on AWS — check current region and cross-region support for your plan.
• No superuser / OS shell — same managed-service constraint as RDS; extensions are limited to the approved list.
• Connection limits — plan for connection pooling; Flexible Server offers a built-in PgBouncer, but you must enable and size it.
• Migration tooling — Azure’s built-in migration service targets PostgreSQL-to-PostgreSQL and MySQL well; heterogeneous Oracle-to-PostgreSQL conversion is not its strength.

The Oracle-Shop Angle

If your organisation is already deep in Microsoft — Entra ID, Azure networking, Microsoft support contracts — Flexible Server removes friction that would otherwise cost you weeks. Auth, private networking, and monitoring plug into tools your team already runs. For an Oracle shop whose surrounding infrastructure is Azure, that alignment often outweighs a feature-by-feature comparison with AWS.

The migration itself is the part Azure does not solve for you. Converting PL/SQL to PL/pgSQL, mapping Oracle data types, and proving the move was lossless are outside the platform’s scope — that is where a dedicated migration tool earns its place, whichever cloud you land on.

Verdict

Flexible Server is a solid, enterprise-ready home for PostgreSQL, and the clear choice on Azure. Pick it when your ecosystem is Microsoft; the stop/start economics and Entra ID integration are genuine advantages. Just size your read-scaling and pooling story up front, and keep heterogeneous migration as a separate workstream from the platform itself.