Hi all,
First time poster here, so go easy on me! :)
We are a customer who is in the process of getting our dev/hosting company to release our live Azure environments to us. We're moving to a new dev company (for various reasons).
Apparently our dev has already moved all our resources into their own Azure Subscription, which is great. There's nothing very exotic, just webapps, SQL, storage etc. Therefore it should be as simple as transferring ownership of that subscription to our own Azure account (we have an empty one set up waiting).
However, when the dev went to transfer ownership to us (back in August), they noticed that in one of the Azure Portal screens, our subscription mentions a product name that's internal to one of their other customers. This spooked them and so they've refused to proceed with the subscription transfer and have been asking Microsoft Azure Support to investigate. In 40 days, Microsoft have yet to come up with a fix or workaround in this time though and so we're completely stuck.
Apologies, I appreciate the details above are incredibly vague. I have asked the devs several times for specifics and screenshots so that I can investigate myself, but they aren't being very transparent at all.
Anyway, my question is...
Has anyone heard of an issue like this in the Azure Admin Portal, i.e. information from one subscription showing under another? I've spent some time trying to find technical discussions of anything even vaguely similar to this online, but I can find nothing, which is really odd.
And if you guys/gals ran into such an issue, how would you proceed?
The devs initially floated the idea of creating a fresh Azure subscription and moving our resources into that to see if it fixes it. That sounds very sensible to me (given it's the subscription not the resources that are showing the error), but despite having suggested that themselves (several times) they don't seem to want to try that until Azure support tell them that they can.
Do you have any suggestions (especially polite ones!) on how best to proceed?
Any workarounds we might not have thought of, or any tips for escalating things with Azure Support would be really appreciated.
Thanks very much,
Andy