This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 79%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGS%3C/text%3E%3C/svg%3E)
I made a mistake. I allowed Azure Database for PostgreSQL Single server to go on beyond the end date. It still shows in my resources, but is now Disabled, and attempts to connect or migrate are not working. The automigration from Azure was supposed to happen, but I see no evidence that was actually planned or attempted. I can no longer access the database. What are my options?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 49%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVK%3C/text%3E%3C/svg%3E)
Greetings!
Since Azure Database for PostgreSQL - Single Server was officially retired on March 28, 2025 instances that missed migration deadlines have been disabled.
Could you please share the details requested via private message as it will help us to troubleshoot the issue.
Thank you,
Hi Garland, Scott,
We would like to thank you for your feedback provided on survey. We found your recent engagement on this question was rated low. However, we are able to share some additional information. Would you please re-evaluate your feedback.
Azure Database for PostgreSQL - Single Server was officially retired on March 28, 2025 instances that missed migration deadlines have been disabled. Periodic notifications were sent since the announcement on March 28, 2023, at intervals of 2 years, 18 months, 15 months, 1 year, 6 months, 3 months, 1 month, and 1 week.
Notifications were sent via email to the subscription owner as well as with service health alert in the portal. Also there was a notification on the portal page of Single Server as a popup acknowledgement for migration enablement.
I would like to inform you that, We have enabled the PostgreSQL single server for the next 30 days to migrate it to the Flexible Server, this is not extendable.
Use our migration service in Azure Database for PostgreSQL to simplify the migration experience. It provides both offline and online migration options. https://learn.microsoft.com/en-us/azure/postgresql/migrate/migration-service/tutorial-migration-service-single-to-flexible
Auto-migration option (offline mode only) can keep server name and DNS the same, so the application won’t need any connection string changes. Note: Public Access needs to be enabled for the Single Server, and CMK server can’t be created using auto-migration.
I hope this information helps. Please do let us know if you have any further queries.
We haven’t heard from you on the last response and wanted to follow up to check if your issue has been resolved.
Please do let us know if you have any further queries.
thank you -that did work! I am reaching out on private message to re-enable one more for us to practice the migration that must be done
Hi Garland, Scott,
I am glad to know that your issue has been resolved. And thanks for sharing the confirmation.
We have received the details via private message. We will investigate the issue and keep you informed as soon as we have an update.
We appreciate your patience
@Garland, Scott Thank you for reaching out.
We would like to inform you that server was enabled from the back end. Please check and let us know if you have additional queries.
Don't forget to mark as accept answer if reply was helpful.
Regards,
Oury
Hi Garland, Scott,
I would like to inform you that, We have enabled the additional requested PostgreSQL single server for the next 30 days to migrate it to the Flexible Server, this is not extendable.
Use our migration service in Azure Database for PostgreSQL to simplify the migration experience. It provides both offline and online migration options. https://learn.microsoft.com/en-us/azure/postgresql/migrate/migration-service/tutorial-migration-service-single-to-flexible
Auto-migration option (offline mode only) can keep server name and DNS the same, so the application won’t need any connection string changes. Note: Public Access needs to be enabled for the Single Server, and CMK server can’t be created using auto-migration.
If my response addressed your query, kindly click 'Accept Answer' and select 'Yes' under 'Was this answer helpful?' This will help others in the community who may have similar questions.
Hi Garland, Scott,
We wanted to follow up as we have not received a response to our last message. Could you please confirm if your issue has been resolved?
If my last response addressed your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.