Microsoft Connected Cache for ISP - ASN 273486 stuck in use after old Azure subscription was deleted

Analista de Rede 0 Reputation points
2026-10-23T14:50:17.69+00:00

Hello Microsoft Connected Cache Team,

I am trying to register ASN 273486 in a new Microsoft Connected Cache for ISP resource, but I receive the following error:

"Your ASN is already in use. Please enter a new ASN or delete all existing MCC resources associated with this ASN to unlock it."

The ASN was previously associated with an MCC resource in an Azure Free Trial subscription that was automatically deleted after expiration.

Old subscription ID: Available privately if required.

New active subscription: Jvn Mcc

New subscription ID: Available privately if required.

New MCC resource: mcc-jvn-prod

ASN: 273486

The old subscription and MCC resource can no longer be accessed or deleted from my side.

The current on-premises MCC server is still running, but I need to migrate management to the new Pay-As-You-Go subscription.

Could the Microsoft Connected Cache Product Group please clear the stale ASN registration / unlock ASN 273486 in the MCC backend so I can complete Operator Verification?

I can provide the old and new subscription IDs, proof of ASN ownership, and PeeringDB information privately if required.

Azure Content Delivery Network

1 answer

Sort by: Oldest
  1. Alex Burlachenko 26,135 Reputation points MVP Volunteer Moderator
    2026-10-28T08:31:22.31+00:00

    Hi Analista de Rede & thx for join me at Q&A platform,

    This looks like a stale ASN association in the Microsoft Connected Cache backend rather than an issue with your new subscription.

    Microsoft's MCC troubleshooting documentation confirms that deleting existing MCC resources normally releases the ASN for reuse.

    However, your original subscription has already been deleted, so you can't perform that cleanup yourself.

    There's also a similar confirmed case where Microsoft staff acknowledged a stale MCC registration and submitted an unlock request to the Product Group.

    I'd recommend opening a support case from your active subscription and requesting MCC backend ASN association cleanup for ASN 273486. Include both subscription IDs, the old and new resource details, and proof of ASN ownership through the private support channel.

    Importantly, your existing cache server is still running. Ask Microsoft to confirm the impact on that deployment before removing the old association. Don't uninstall or reprovision the node yet.

    As a volunteer moderator, I can't unlock the ASN or initiate backend changes directly.

    Best regards,

    Alex Burlachenko

    💬 P.S. Did this help? Mark it as the solution: it keeps me motivated!

    ➕ Follow me on Q&A for more answers

    📝 And feel free to visit my blog → https://ctrlaltdel.blog/

    Was this answer helpful?


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.