Improving the indexed partitioning criteria for handling storage accounts with same naming conventions
As described in detail here: https://azure.microsoft.com/en-us/documentation/articles/storage-performance-checklist/#subheading47 , Azure handles indexed partitioning with an index with aphabetical criteria, so storage accounts starting with A-H will go into one partition, H’-R will go into a different partition and last R’-Z will go into another different partition too.
We discovered that this could affect High Availability of VMs if you take care of putting them into Availability Set and use different storage accounts for their virtual disks, but same naming convention for accounts. In this case, if a fail happens on a given partition for example during an internal maintenance task or storage load balancing-operation, all accounts sharing the same partition are affected and so your VMs that you expected to have HA, will reboot together.
So, it would be possible to make Azure automatically spread into separate partitions the storage accounts of VMs in HA configuration, without us to find weird ways of renaming storage accounts in order of giving them names with different characters in the beginning (we prefer to use logical naming conventions)?