Microsoft’s PostgreSQL Roadmap and Strategy: Reactionary

• Microsoft’s PostgreSQL lineup is in flux again, leaving some customers to face costly retirements and migrations.
• Microsoft is once again realigning its PostgreSQL services with a focus on two scale-out options built for different purposes.
• Customers should only consider the established offerings, but design for portability so that the next change costs less.

Microsoft’s approach to PostgreSQL, an open-source alternative to SQL Server, has been opportunistic rather than planned. Since 2018, Microsoft has released six PostgreSQL offerings, retired two, rebranded a third, and scheduled a fourth for retirement. Most of those changes originated from an acquisition, a marketing priority, or a competitor rather than following a stated roadmap. While PostgreSQL itself as a product is a safe bet, the Azure-based service wrappers around it change often, and each change costs customers a migration, revalidation, code changes, and retraining.

Customers who are on Azure or considering one of the PostgreSQL services should narrow their use to the two stable offerings, avoid service-specific management features where possible, and parameterize deployment scripts and pipelines so they can move easily. Microsoft’s history suggests future changes are likely, and portable designs can reduce the effort and risk of another migration.