You can now migrate your Azure Database for PostgreSQL server from a virtual network‑integrated deployment to a network configuration that supports Private Endpoint connectivity. If you originally deployed your server inside a virtual network but now want more flexibility in how you manage networking, Private Endpoints give you a simpler and more scalable model. With this migration, you can continue to access your server privately over the Azure backbone network, reduce dependency on delegated subnets, and better align your database networking with evolving architecture or organizational standards.
You can directly initiate the migration through Azure CLI, API, or SDK. While the operation involves a period of downtime, it enables you to adopt Private Endpoint connectivity without needing to recreate your server or move data manually. After the migration, you can configure Private Endpoints or firewall rules based on your desired access model and update your infrastructure-as-code templates accordingly.
Disclaimer:
This migration currently supports PostgreSQL servers that are not configured
with high availability or read replicas. Additional post‑migration configuration,
including updating Terraform templates and setting up Private Endpoints
or firewall rules, is required.
Learn
more.