New PostgreSQL High availability experience - does migration timeline affect servers that are already zone-redundant HA?

Question

I have read. However, I am not quite clear on the migration details. We have two Azure PostgreSQL servers that are already in zone redundant high availability mode. I understand that the labeling in the portal and the prompts are changing a bit, but does anything need to change on the servers themselves? Wasn't clear whether our operations team actually needed to plan for a migration in our case or we were already fine as is. I understand that some servers might be configured with same zone high availability and need to migrate but that seems not to be the case for us.

Any clarification you could give on impact (if any) to existing zone redundant HA deployments would be greatly appreciated. Thanks in advance!

Answer 1

Existing Azure Database for PostgreSQL flexible servers that are already configured with zone-redundant high availability (HA) do not require a migration or configuration change because of the new “Business Critical (High Availability)” / “Zonal resiliency” experience.

From the current HA model:

• Zone-redundant HA already places the standby in a different availability zone for maximum zone resiliency.
• The new portal experience mainly introduces clearer options and wording (for example, the Zonal resiliency toggle and the fallback checkbox for same-zone HA) and enforces zone-redundant HA as the default when enabling HA.
• Migration or automatic movement is only relevant when:
  • HA is being newly enabled on an existing non-HA server, or
  • HA is configured as same-zone (zonal) and the service later moves workloads to zone‑redundant HA when zonal capacity becomes available (or when administrators choose to migrate using PITR/read replicas, depending on the documented behavior).

For servers that are already zone‑redundant HA, the architecture and behavior (primary in one zone, standby in another, synchronous replication, automatic failover within 60–120 seconds on zone failure, and the 99.99% SLA) remain as documented. No additional migration planning is indicated in the provided guidance for such deployments.

Operations teams should only review the new portal labels to confirm that:

• High availability is shown as enabled, and
• The configuration reflects Zone‑redundant / Zonal resiliency: Enabled for those servers.

If those conditions are already met, no further action is required based on the new HA experience.

---

References:

• Configure high availability for Azure Database for PostgreSQL
• High availability in Azure Database for PostgreSQL
• Reliability in Azure Database for PostgreSQL

Answer 2

Hi Brian Beery,

it looks like both of your servers are already configured with true zone-redundant HA (primary and standby in different AZs). The new portal experience is mostly a UI/label change and a few updated prompts—there’s no underlying migration required for servers that are already in zone-redundant mode.

Here’s the key point: • Only servers that were deployed with the “same-zone” fallback option (because true multi-zone capacity wasn’t available at creation time) need to be automatically migrated to full zone-redundant HA once capacity frees up. • If you already have a standby replica in a different zone (your case), nothing needs to change, and there’s no impact or planned migration window for you.

You can verify your setup by hopping into the High Availability blade in the portal (it should show “Zone-redundant” with two different AZ values), or run the Availability Zones diagnostic to confirm AZ support. Otherwise, you’re all set—just ignore the new “migration timeline” notices, as they only apply to same-zone fallbacks.

Hope that clears it up!

Reference documentation

• Zone-redundant HA overview: https://docs.microsoft.com/azure/postgresql/flexible-server/concepts-high-availability#zone-redundant-high-availability-architecture
• FAQ on HA for Flexible Server: https://docs.microsoft.com/azure/postgresql/flexible-server/concepts-high-availability#frequently-asked-questions
• Enable/disable HA in the portal: https://docs.microsoft.com/azure/postgresql/flexible-server/how-to-manage-high-availability-portal
• High availability concepts (zone-redundant vs. zonal): https://learn.microsoft.com/azure/postgresql/high-availability/concepts-high-availability#availability-zone-support-types