Current CosmosDB implementation is incompatible with Azure CosmosDB name limits

[jeremyrickard]

There have been provisioning failures with CosmosDB that fail in ARM with a BadRequest and an error message that the name must be between 1 and 50 characters. We currently use a UUID. More info below per @zhongyi-zhang (thanks for the info!!)

The actual limit of the length of CosmosDB account name is [50 – length of region name – 1 (length of ‘-‘)].
For example,
In EastUS, the max length of the name is [50 – 6 – 1] = 43
In AustraliaSoutheast, the max length of the name is [50 – 18 – 1] = 31
I reported this to CosmosDB team several months ago, and they confirmed.
UUID as the account name in OSBA takes 36 of them, so provisioning could fail in some regions such as AustraliaSoutheast.
In @chzbrgr71 's case, the region is "southcentralus"(length=14). The actual length of the account name is 14 + 36 + 1 = 51 > 50.