Cloud Management Gateway Failed

This was a rare one. The short of it is, the storage account name had been taken by another customer. Similar to the cloudapp.net namespace, it’s flat. That means when you create your service you need to select a distinct name. Normally, when you select your CMG name, a good practice is to go into Classic Cloud Services and pick out a unique CMG Service Name. When creating your CMG the classic service will then auto create your storage account with the same name as your selected CMG. The rare issue we ran into is the name that was selected for the CMG service had already been taken by someone else for the storage account (but it had already checked out as a valid CMG service name showing as available as a classic cloud service. After deploying the CMG service multiple times and failing, I selected a new CMG name (added a 2 at the end) and it deployed fine. Until next time.