Issue: Azure Virtual hub deletion, question on bill charge

Rajendra Mattihalli 0 Reputation points
2026-08-08T06:34:00.01+00:00

Hi Team,

I have around 5 azure virtual hub which is unable to delete from Azure console or neither from Azure cli.

Every time attempt to delete there is error. Some route-table association still exists.

stuck Failed hub with phantom route-table associations

Attempted below actions

  1. followed the suggestions in diagnostics.
    1. Azure cli commands - to delete the virtual hub
  2. Also tried resetting the hub , deleting it from console still no go.

Asking to connect Azure support team, to remove this connection from backend.

How do we go with this, if i don't have azure support plan. If the deletion of virtual hub is mainly cause of the bug from portal azure. But not technically from our infrastructure.

Because of the diagnostics, run over ideally there should not be single association. Only associations i could see is default and none routeTable which cannot be deleted. Still there is an issue with virtual hub deletion.

Would azure charge for the Virtual hub of all the virtual hub failed for deletion, despite it getting failed for deletion from azure end?

Azure Virtual WAN
Azure Virtual WAN

An Azure virtual networking service that provides optimized and automated branch-to-branch connectivity.

0 comments

1 answer

Sort by: Oldest
Most helpful Newest Oldest
  1. Allan Solomon Mejia 8,085 Reputation points
    2026-08-09T21:28:10.0733333+00:00

    Hello @Rajendra Mattihalli

    Based on your description, this sounds like the Virtual WAN hub has orphaned/stale routing associations in the Azure control plane, especially since you've already removed the visible connections but the hub still reports route-table associations.

    One important point: the defaultRouteTable and noneRouteTable are managed Virtual Hub route tables, so you shouldn't try to delete those directly. Microsoft documents the association/propagation behavior of Virtual Hub route tables here.

    Before escalating, I would try Virtual Hub Reset:

    Virtual WAN → Virtual hubs → affected hub → Reset

    Microsoft specifically states that Hub Reset can bring failed resources such as route tables, the hub router, or the virtual hub itself back to the correct provisioning state.

    After the reset completes, verify that all VNet/VPN/ExpressRoute connections have actually been removed and retry the hub deletion.

    For VNet connections specifically, Microsoft recommends deleting them from the Virtual WAN portal experience, not from the VNet side, because deleting from the VNet side can leave the Virtual WAN connection behind.

    If Reset completes but deletion still fails with an association that isn't visible in the portal or CLI, I would stop repeatedly modifying the hub. That can indicate orphaned backend/control-plane state that requires Microsoft Support to investigate.

    Regarding your billing question

    Yes, I would assume the Virtual Hub can continue generating charges while the resource still exists, even if your intention is to delete it. A failed deletion isn't the same as successful resource deletion.

    Since you believe Azure itself is preventing deletion, preserve:

    • First attempted deletion date/time
    • Resource IDs of the affected hubs
    • Deletion error messages
    • Activity Log entries
    • Correlation/Request IDs
    • Screenshots of the failed deletion

    Then open an Azure support request.

    You mentioned that you don't have a support plan. Technical support normally requires one, but Azure billing and subscription support is available without purchasing a paid technical support plan.

    If you're being charged for Virtual Hubs that Azure wouldn't allow you to delete because of an apparent backend issue, open the request under Billing → Assistance with a bill / unexpected charges and explain that the charges occurred after your documented attempts to delete the resources.

    The Billing team can review whether a billing adjustment is appropriate; Microsoft Q&A can't authorize credits or refunds.

    So I'd proceed in this order:

    Hub Reset → retry deletion → if phantom associations remain, collect Activity Log/correlation IDs → create a support request.

    And keep evidence of the first failed deletion attempt, since that timestamp may be important if you later request a billing review.

    Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.

    Was this answer helpful?

    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.