"Hey guys... can we like avoid repeating the clusterfuck that is our elventeen billion.. AWS accounts when we start moving over to Azure by having like sensible, enforceable, already in place multi-tenant plan before everyone starts moving things over? Look we can even set up things with Azure Policy to avoid cost over runs and dumb things from happening.."

"NOPE SORRY ALREADY HAVE LIKE 10 DEV ACCOUNTS PAID FOR WITH CORP CREDIT CARDS OR PERSONAL CARDS THEN EXPENSED AND SOME RANDOM ASS DEV IS THE ROOT POLICY MANAGER BECAUSE WE ALL PIGGY BACKED OUR PROD STUFF ON HIS ACCOUNT! FUCK YEAH! PLUS LIKE THAT WOULD TAKE SOME C-LEVEL PERSON DOING MORE THAN SAYING 'HEY GUYS WE AZURE SHOP NOW FIGURE OUT HOW TO GET THERE LIKE WHENEVER YOU WANT!!"

Oh and nobody is bothering to put anything into CloudHealth even though it is requirement... and IT hasn't even set up CloudHealth integration yet... because they own it... well.. it is busted as fuck!

Oh.. oh and you are the first ops team to ask for access and we have like no account creation policy in place or anything how people are supposed to request access.. so it has been bounced around a week and my team still has no accounts...
But hey... we have to have one of the services we support spun up and running in Azure by the end of June to meet our enterprise contract reqs with M$ :D :D :D

I'm sure this will go great and totally not turn into a huge cost overrun clusterfuck.