Share via

Azure Front Door / CDN still incurring charges even after deletion (post auto-migration)

GregGood-7533 5 Reputation points
2026-04-26T21:47:08.4333333+00:00

I had a couple of sites I set up a couple of years ago on Front Door / CDN Classic as it was the only clean way to get HTTPS configured on my basic SPA site (to my knowledge...still learning Azure). Theses site were auto-migrated to a Standard or Premium service automatically about 10 days ago and are now incurring costs daily. I don't really need the related projects set up with those services as Static Web Apps now handles my scenario perfectly. I tried to delete the related Front Door and CDN profiles/services but am still seeing charges getting applied daily. I've tried to use the all of the cost analysis and resource graph tools to find the source of the charges but they all show no related resources, yet I'm still getting charged. It's like there are services I can no longer see like a Web App Firewall or some ruleset that is still consuming the supposedly deleted services. The cost analysis tools tell me charges, but no GUIDs for the resource cost it displays. It's like some portions of the classis mode of the service are somehow still active in a backend system I have no access to now.

I've tried to submit support tickets but my scenario is not listed in the questions asked and there is no ticket I can submit, I guess, until I get billed on my next cycle in 10 or 15 days, in which I can try to request a refund. Is there any other way to get support for this issue or do I have to just wait until I'm billed then dispute the bill somehow?

Please help!

Community Center | Not monitored

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

Answer recommended by moderator

GregGood-7533 5 Reputation points
2026-06-05T22:21:59.8933333+00:00

It took several weeks, but my issue was finally looked at by tech support and resolved. They turned off the orphaned services I no longer had access to. They said they had a big backlog of support requests. I'm guessing it might have been related to my same issue if potentially thousands of users started incurring unexpected charges from the changes they made. It took a couple of weeks more to refund the over-charges, but they did follow through and everything is now fully resolved. It was just a little scary when I felt like my support requests went unseen for a couple of weeks or more. A simple post in my support ticket saying they we overwhelmed and might take a few weeks to get back to me would have eased my mind a bit. I did have to pay the overages at invoice time, then they got fully refunded weeks later.

Not sure how to mark this as answered here in this site, but consider this response as me marking my situation as fully resolved.

Was this answer helpful?

2 additional answers

Sort by: Most helpful
  1. kagiyama yutaka 3,765 Reputation points
    2026-04-26T23:12:44.6966667+00:00

    The issue is a migrated FD base‑meter still billing under the old path… u can stop it by Billing→new req→skip suggstns n ask them to remove that orphaned Standard/Prem meter for ur sub.

    Was this answer helpful?

    0 comments No comments
  2. AI answer

    2026-04-26T21:47:29.2266667+00:00

    Azure Front Door Standard/Premium profiles incur a base monthly fee per profile, even when there's no traffic. Variable meters like data transfer and requests stop charging when there's no usage, but the base fee continues until the profile is deleted.

    For migrated environments, the classic Front Door or CDN resource can remain present after migration, but billing for the Standard/Premium tier is tied to the new profile. Deleting only the classic resource does not stop Standard/Premium billing. The classic resource is recommended to be deleted only after verifying DNS and traffic are fully moved, but the active, billable resource after migration is the Standard/Premium profile.

    If all visible Front Door and CDN resources have been deleted and charges are still appearing, billing support must review the subscription and meters directly. Billing support is free and is the correct path to:

    1. Confirm which Front Door Standard/Premium profile(s) or meters are still active and generating the base fee.
    2. Verify whether any migrated profiles still exist in the subscription (even if the classic resources were deleted).
    3. Evaluate a billing adjustment or credit if charges are unintended.

    To proceed, create a billing support request in the Azure portal. Billing support can be opened even if the scenario doesn’t match a predefined category; after selecting Billing and the subscription, continue through to “Create a support request” and then “Return to support request” if suggested solutions are shown, and complete the case details. Billing support will then contact to investigate the ongoing charges and help stop them.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?