[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 PostgreSQL 18 support via Terraform (GA) and updates the Ansible module (GA) to align with the GA REST API, enabling Elastic Clusters provisioning and PostgreSQL 18 deployments. Azure CLI introduces a --zonal-resiliency parameter (GA) to enable zone‑redundant high availability by default, with an option to allow same‑zone standby. Azure SDKs for .NET, Go, Java, JavaScript, and Python (GA) adopt REST API version 2025‑08‑01, add default database name configuration for Elastic Clusters, support PostgreSQL 18, clarify operation IDs, and correct HTTP response codes. Azure Database for PostgreSQL Flexible Server adds Premium SSD v2 capabilities in public preview, including HA (same‑zone and zone‑redundant), geo‑redundant backups, in‑region and geo read replicas, Geo‑DR, and major version upgrades, with higher scalable IOPS/throughput and low latency. Latest minor versions 18.1, 17.7, 16.11, 15.15, 14.20, 13.23 are supported and applied during maintenance with two security fixes and 50+ bug fixes; PostgreSQL 13.23 is final community release (EOL) with Azure Extended Support available. January 2026 maintenance delivers engine updates, new extensions, Elastic Clusters enhancements, performance and reliability improvements, expanded migration and Microsoft Fabric Mirroring support, analytics/security/observability features, improved Query Store performance, new WAL metrics, and enhanced networking, with automatic onboarding from 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, refine the bullet 'Show high availability feature with zonal resiliency argument' to explicitly name the parameter and behavior. Suggested text: 'az postgres flexible-server create/update: Add --zonal-resiliency (GA) to enable zone‑redundant high availability by default; supports configuring same‑zone standby alongside --standby-zone.'
  2. In the January 13, 2026 RDBMS entry, adjust the related bullet 'update: Fix bug for using argument --standby-zone when enabling high availability' to note its relationship to --zonal-resiliency (i.e., that --standby-zone can be used to specify same‑zone standby when zonal resiliency settings are applied).
  3. Add a brief parenthetical to the January 13, 2026 RDBMS overview line to clarify default behavior for readers: '(Default: zone‑redundant HA when --zonal-resiliency is specified; same‑zone standby supported via --standby-zone.)'

---

📚 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.