Orphaned Azure Database for PostgreSQL Flexible Server is billed daily but does not exist in ARM, Portal, CLI or Resource Graph (leftover of automatic Single Server migration)

Question

We are billed every day for an Azure Database for PostgreSQL Flexible Server that does not exist anywhere in Azure Resource Manager. We cannot see it, stop it or delete it. We need a way to delete it, or someone at Microsoft to delete it, so the charges stop.

The resource, as reported by billing

• Subscription: Pay-As-You-Go, ID ending in ...bbf3
• Resource ID from usage details: /subscriptions/<sub>/resourceGroups/timetracking_esveo/providers/Microsoft.DBforPostgreSQL/flexibleservers/timetrackingdbesveo
• Region: North Europe
• Meters billed daily: B1MS Burstable compute (24 h/day), Flex Server Storage Data Stored, and since 1 September 2026 also "Extended Support vCore" (24 h/day), which alone is now about 2.30 EUR/day

Timeline reconstructed from Cost Management

• Until 24 September 2024 the resource group timetracking_esveo contained a PostgreSQL Single Server (billed as vCore, Basic Data Stored, Backup LRS) and an App Service (S1).
• On 17 September 2024 Flexible Server meters (B1MS, Storage Data Stored) started for the same resource group. This matches the automatic Single Server to Flexible Server migration Microsoft ran ahead of the Single Server retirement. Single Server meters stopped on 24 September 2024.
• On 6 March 2025 the App Service meters stopped. This is when the resource group was deleted. The Flexible Server meters did not stop.
• Since then the Flexible Server has been billed every single day (about 15 EUR/month, roughly 270 EUR so far) even though the resource group and the server are gone from ARM. Since 1 September 2026 the Extended Support meter has been added on top.

What we have verified

• az group show -n timetracking_esveo returns ResourceGroupNotFound.
• GET on the full resource ID above (api-version 2024-08-01) returns ResourceGroupNotFound. The same for the Single Server resource type.
• az postgres flexible-server list on the subscription returns only our other server (esveo-shared-pg, West Europe).
• az resource list --name timetrackingdbesveo returns nothing.
• Azure Resource Graph across all subscriptions in the tenant (resources | where name =~ 'timetrackingdbesveo' or type has 'dbforpostgresql') returns only esveo-shared-pg.
• The Microsoft.DBforPostgreSQL resource provider is registered on the subscription.
• The server is not present in any other subscription in the tenant.
• Signed in as a user with Owner on the subscription and Global Administrator in the tenant, and as the subscription's Account Administrator: same result. Portal "All resources" with hidden types shown does not list it either.
• Cost analysis grouped by resource shows two PostgreSQL resources (esveo-shared-pg and timetrackingdbesveo); the Resources view shows only esveo-shared-pg.

Support history

We opened billing support request 2608170050001071. The Azure Billing team confirmed they cannot act on resource-level issues and suggested either cancelling the whole subscription (not an option, other production resources run in it) or buying a support plan to open a technical request. We do not think we should have to buy a support plan to stop paying for a resource that Microsoft's own automatic migration left behind and that has no ARM representation we could act on.

Questions

1. Is there any customer-side way to delete a Flexible Server that exists in billing but whose resource group and ARM record are gone? Would recreating an empty resource group with the same name in the same region make it visible again?
2. Is this a known issue with the automatic Single Server to Flexible Server migration, where deleting the resource group afterwards removes the ARM record but leaves the backend server running and billing?
3. Can a Microsoft moderator route this to the Azure Database for PostgreSQL team or open a technical support case on our behalf, given that billing support has confirmed it is out of their scope?

Thank you.