[AI-Suggested] Content update request from Others signal: January 2026 Recap: Azure Database for PostgreSQL

[learn-build-service-ppe]

Background

A recent product update has been released that may impact our documentation. This could include new features, changes to existing functionality, or other product enhancements.
Your Action Required: Please review the suggestions below and update the relevant documentation to ensure accuracy and completeness.

Signal Details:

• Title: January 2026 Recap: Azure Database for PostgreSQL
• Source URL: https://techcommunity.microsoft.com/t5/microsoft-blog-for-postgresql/january-2026-recap-azure-database-for-postgresql/ba-p/4492408

Source Signal Summary
Azure Database for PostgreSQL adds support for PostgreSQL 18, with GA updates across Terraform and Ansible enabling server provisioning, upgrades, and Elastic Clusters management via the latest GA REST API. Azure CLI introduces a --zonal-resiliency parameter for zone‑redundant high availability, with an option to allow same‑zone standby when cross‑zone capacity is unavailable. SDKs for .NET, Go, Java, JavaScript, and Python are updated on GA REST API version 2025‑08‑01, adding Elastic Clusters default database naming, PostgreSQL 18 support, clearer operation IDs, and corrected HTTP response codes. Azure Database for PostgreSQL Flexible Server enables expanded HA, geo‑redundant backups, in‑region and geo read replicas, Geo‑DR, and major version upgrades on Azure Premium SSD v2 in public preview, with higher, independently scalable IOPS/throughput and predictable low latency. Latest minor versions 18.1, 17.7, 16.11, 15.15, 14.20, and 13.23 are supported and applied during maintenance, delivering critical security and reliability fixes, with PostgreSQL 13.23 as the final community release for version 13. The January 2026 maintenance release introduces major engine updates, new extensions, Elastic Clusters enhancements, performance and reliability improvements, improved Query Store performance, new WAL metrics, enhanced networking flexibility, expanded migration and Microsoft Fabric mirroring support, and a phased rollout beginning January 20, 2026.

Suggestions

Note

Suggestions are generated by AI and they may not be entirely accurate or complete. Please check impacted files scope and suggestions details before making changes.

• docs-ref-conceptual/Latest-version/release-notes-azure-cli.md:
  1. In the January 13, 2026 section under RDBMS, update the entry mentioning "Show high availability feature with zonal resiliency argument" to explicitly include the parameter name: "az postgres flexible-server create/update: Add --zonal-resiliency parameter to enable zone-redundant high availability."
  2. In the same RDBMS section (January 13, 2026), add a follow-up sentence to the --zonal-resiliency entry noting the behavior: "When cross-zone capacity is unavailable, optionally allow a same-zone standby fallback (via the zonal resiliency configuration)."
  3. Ensure consistency of parameter naming across RDBMS entries in January 13, 2026 by using explicit flags (e.g., --zonal-resiliency, --standby-zone) rather than generic phrases, so readers can quickly identify the exact CLI switches introduced.

---

📚 To learn more about agentic content maintenance workflow, visit Agentic workflow for Learn content maintenance. Sign in using Learn Profile to access the content on this link.

💬 Share your feedback on the Learn Content Maintenance Agentic Workflow here.