When a randomly-generated shared storage key begins with a '/', Windows interprets this as the start of a string option, not as a value.
How is this addressed
The simple fix is to check the key to see if it begins with a '/'. If so, use the second key. That reduces the collision rate by a significant amount, but doesn't completely solve the problem. To solve it, the storage account keys need to be checked when the storage account is created, at workspace-creation time.
Fixes #69
What is being addressed
When a randomly-generated shared storage key begins with a '/', Windows interprets this as the start of a string option, not as a value.
How is this addressed
The simple fix is to check the key to see if it begins with a '/'. If so, use the second key. That reduces the collision rate by a significant amount, but doesn't completely solve the problem. To solve it, the storage account keys need to be checked when the storage account is created, at workspace-creation time.