Hi Geir Sagberg,
Thankyou for Reaching Microsoft Q&A!
Azure retired PostgreSQL Single Server in March 2025. If the resource wasn’t migrated, it can become “orphaned” still running and billed but invisible in Portal/CLI due to tenant or RBAC changes.
What to do:
Find the resource:
In Portal: Switch Directory to the tenant linked to your billing profile.
CLI:
az account list --output table
az account set --subscription <subscription-id>
Use Resource Graph:
az graph query -q "resources | where name contains 'gaver11'"
Restore access:
Add yourself back as Owner/Contributor at subscription level if RBAC was removed.
Migrate to Flexible Server:
-Create a new Flexible Server
az postgres flexible-server create --resource-group <rg> --name <flex-name> --location <region>
-Start migration
az postgres flexible-server migration create --resource-group <rg> --migration-name <id> --properties @migration.json
If migration isn’t possible:
-Dump data
pg_dump -h gaver11.postgres.database.azure.com -U <user> -d <db> -f db.dump
pg_dumpall --roles-only > roles.sql
-Restore to Flexible Server
pg_restore -h <flex-name>.postgres.database.azure.com -U <user> -d <db> db.dump
psql -h <flex-name>.postgres.database.azure.com -U <user> -f roles.sql
Stop billing:
Delete the old Single Server after migration or dispute charges via Cost Management.
The empty Resource Graph results mean the old Single Server is fully retired post-March 2025: no control-plane resource left for portal/CLI deletion, just a lingering backend that'll auto-cleanup in -30 days with billing stopping.
You've done everything possible on your end. Charges should drop off soon in Cost Management monitor there. Your Flexible Server is good to go!
If this helps please do click Accept Answer and Upvote for was this answer helpful.