I have two subscriptions for difference Jenkins masters, when I used the same "Resource Group" in the UI, the automatically generated "Storage Account Name" created the same name on both Jenkins masters leading to an ARM template deployment failure.

I think the fix would be to use a hash of the Subscription ID and the Resource Group name to generate the storage acocunt name since that must be globally unique