On Tuesday of this week we started to receive alerts that many of our Azure DevOps deployments for Managed Cloud were failing with the following error
I may go back at some point and update this post with more information, but I want to get it published as quickly as possible in case you’re running into this issue as well. The issue ended up being related to the casing of the Subscription ID that was used when we originally create our Service Connections
As I’m sure many of you have done, when we first created these Service Connections in ADO, the details were copied directly from the Sitecore Service Request that was used to generate that account. If you’re unfamiliar with that process then you can read about it here (but you also probably won’t be reading this post if you’re not)
Either way, the Subscription ID that is returned from those Service Requests is in all uppercase. This doesn’t appear to be an issue as the connections can be “Verified” in ADO and the everything appears to be fine
Notice how Subscription ID is in uppercase
To fix this, we ended up needing to create a new Service Connection, but with the Subscription ID in lowercase (This matches if you were to copy the Subscription ID directly from Azure itself)
With this new Service Connection our releases are back to working like they were
Notice how Subscription ID is now lowercase
I am currently waiting on an update from Microsoft on why this started happening, but if you run into this problem hopefully this fixes it for you as well.
A huge shoutout to Bob Dieguez over at United Airlines for being the first one to bring this issue to our attention and finding the fix! I’ll be sure to update this with more information as I get it.
Update:
Sitecore support has updated me that this issue has been officially recognized by Microsoft and they are rolling out a fix! You can read more about that here:
Sitecore Saga 