An Azure service that provides global content delivery and acceleration.
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/