Share via

Resource group has a cost for a resource that does not exist

Rasmus Frederiksen 20 Reputation points
2026-02-26T08:22:03.0333333+00:00

Currently attempting to reign in company services, I see a MySQL Flexible server in cost analysis, which does not seem to have been deleted in the last 90 days at least, racking up costs

But the resource group doesn't contain it, attempting to open it leads to "Resource not found"

Considering the service is costing around 100USD, and the bills we have indicate we've been paying it for the last half year at least, I'd like to know what this service has on it, but I can't access it

Furthermore

  • No systems we have reference it
  • az resource list -g <group>does not mention it
  • attempting to create a new mysql flexible server on this resource group with the name of the one which supposedly does not exist, I receive the error "name must be available"

Is there anything I can do here, that I simply don't know about?

Azure Database for MySQL
0 comments
Answer accepted by question author
  1. TP 152.1K Reputation points Volunteer Moderator
    2026-02-26T08:28:39.32+00:00

    Hi,

    From your description it sounds like the resource was deleted in the past and it either didn't fully delete or it did and the billing for it got stuck. Either way you need Azure engineer to manually fix it on the backend.

    I recommend you create a new billing support request so that you can speak to billing engineer and have them investigate. Billing support is free.

    Please carefully follow my instructions below to create new billing support request without getting stuck in endless loop.

    If you have issues creating ticket please let me know in a comment.

    1. Navigate to this link to start the process:

    https://portal.azure.com/#create/Microsoft.Support

    2. Enter billing in the box and click Go

    User's image

    3. Select Billing and click Next

    User's image

    4. Select your subscription from the dropdown and click Next

    5. At this point there will be a delay of several seconds, and then various options will be displayed. Click Create a support request button at the top. DO NOT CLICK any of the other options.

    User's image

    6. Fill out screen, Summary, Problem type, Problem subtype, then click Next button at bottom. You may need to select different Problem/subtype than shown below

    User's image

    7. There will be another several second delay, and then some solutions will be displayed (this is similar to above). DO NOT CLICK any of the solutions, instead click on Return to support request button in upper left corner, similar to below

    azure support request Return to support request

    8. Now you are back at support case. Click Next button at bottom to continue to Additional details tab. Fill out information as required, one of the items you may need is your Subscription ID.

    User's image

    You can open separate browser tab and navigate to your subscription in portal, the ID is there, click the copy button to the right of it, then paste it into the box on Additional details tab. Click Next to advance to Review + create tab, then click Create.

    You should receive an automated email within a few minutes and then be contacted by support within 1 business day.

    Please click Accept Answer and upvote if the above was helpful.

    Thanks.

    -TP

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2026-02-26T08:22:19.13+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The behavior matches a classic “resource not found but still billed” situation where Cost Management shows historical/ongoing charges, but the underlying resource object is gone or not addressable via ARM/CLI.

    Based on the available information, only supported actions are:

    1. Verify that the resource truly does not exist
      • Confirm subscription and context when checking:
        • In Azure CLI, explicitly set the subscription: 
                 az account set -s <subscriptionId>
          Then list resources in the group: 
                 az resource list --resource-group <group>
          This is the supported way to verify what is actually deployed in that resource group.
      • If the resource does not appear in az resource list and the portal blade for the resource shows Resource not found, it is no longer present in Resource Manager.
    2. Understand why Cost Analysis still shows cost
      • Cost Analysis and billing are based on metered usage records and reservations/commitments, not on the current ARM inventory. Historical charges remain visible even after a resource is deleted.
      • A “ghost” resource in Cost Analysis usually means one of the following:
        • The resource existed and was deleted, but you are looking at a time range that includes when it was active.
        • The cost is being attributed to that resource name from a metering/billing perspective even though the ARM object is gone.
      • When a resource is deleted, there can be a short period where the portal still shows it but it is not actually available; refreshing normally clears it. If it persists, the official guidance is to contact support.
    3. Use Cost Management views to confirm scope and grouping
      • In Cost Analysis, use the Resources view and group by resource to confirm that the charges are indeed attributed to that specific MySQL Flexible Server and subscription.
      • Grouping and child-resource behavior (for example with SQL) is for visualization only; it does not change the underlying billing records, but it can help confirm that the cost is not coming from another related resource.
    4. Next step when a billed resource cannot be accessed
      • Because the resource cannot be found via ARM (portal/CLI) but continues to appear in billing, the only supported escalation path is a billing/support case.
      • Billing support is free. Use the Azure portal to open a Billing support request for the affected subscription and provide:
        • Subscription ID
        • Resource name as it appears in Cost Analysis
        • Screenshots of Cost Analysis showing ongoing charges
        • Evidence that az resource list --resource-group <group> does not show the resource and that the portal blade returns Resource not found
      • Support can:
        • Confirm whether the resource is truly deleted at the platform level
        • Investigate why metering is still occurring or why historical charges are mapped as they are
        • Advise on possible credits/waivers if the charges are unintended (handled case-by-case by billing).

    There is no supported way from the customer side to “force delete” or “reclaim” a name that the platform still considers in use, nor to directly inspect a resource that ARM reports as NotFound. Once the basic checks above are done, engaging Azure support is required.

    References:

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.