Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
APPLIES TO: 
Azure Database for PostgreSQL - Single Server
Azure Database for PostgreSQL single server has now been retired. As a result, the migration articles related to this service will be removed soon. It's essential to migrate to Azure Database for PostgreSQL flexible server to ensure continued service and support. Review and complete any necessary migrations to the flexible server before these resources are no longer available.
Automigration is a service-initiated migration that occurs during a planned maintenance window for a single server deployment. After the migration, a flexible server is created with the same name as the original single server deployment, with all data copied over. Additionally, existing connection strings automatically point to the newly migrated Flexible Server. Learn More
Workloads on a single server deployment after March 28, 2025, poses security risks. The platform no longer receives security updates, bug fixes, or live support. To safeguard your workloads, single server deployments are force-migrated to flexible server instances using automigration.
Eligibility for force migration of single server deployments with Private End Points
- single server deployments with Deny Public Network Access set to No → Eligible for force migration.
- single server deployments with Deny Public Network Access set to Yes → Not Eligible for force migration.
Handling Private End Points
Certain advanced features, such as Private Endpoints, can't be force-migrated automatically. This means:
- Private Endpoints aren't enabled on the automigrated Flexible Server.
- You must manually configure Private Endpoints on the migrated Flexible Server to maintain business continuity. Follow these steps to configure a Private Endpoint on your Flexible Server with the same settings as your single server deployment.
Steps to configure Private End Points for an Automigrated Flexible Server
Confirm that the flexible server deployment has the same name as the single server deployment in the same subscription and resource group. This confirmation indicates that the automigration was successful. (Refer to the attached screenshots from Azure portal for reference).
Delete the private endpoint associated with the single server deployment using Azure CLI or by following steps in Azure portal.
Important
Ensure that the private endpoint associated with single server deployment is deleted before proceeding with the next steps.
Create a Private Endpoint on the automigrated Flexible Server using the same name and Private DNS zone as the single server deployment. Use Azure CLI or Azure portal.
Note
You might see your Flexible Server in an Updating state when attempting to create a Private Endpoint. This issue occurs if the DNS record of your single server deployment hasn't been released yet. One such cause is the Private Endpoint on the single server deployment isn't deleted. If Private Endpoint on single server deployment is still active, delete it. In some cases, even after deletion, the DNS record might take up to 5 hours to be fully released. Wait for the Private Endpoint to be created successfully before retrying.
Ensure that the deployment completes successfully and that the private endpoint is attached to the Flexible server.
After configuration, you should be able to connect to automigrated flexible server using the same connection strings as single server deployment via the private endpoint.
