For all Azure Powershell commands that perform the API function of "Put Blob", such as Set-AzureDeployment, Set-AzureStorageBlobContent, and New-AzureDeployment, add a command parameter for the "timeout" URI parameter passed via the API. Currently, any such Powershell command results in a static "timeout" value of 90 (seconds) being passed via the API.
Impact: Being able to define a "timeout" would be valuable for clients using PowerShell that have larger packages, slower connections, or the need to troubleshoot storage exceptions during storage or deployment operations.
This is a good feedback. We will take a look.
Brady K commented
Example of a storage exception that was more difficult to troubleshoot given the static timeout:
New-AzureDeployment : The remote server returned an error: (500) Internal Server Error.
+ CategoryInfo : CloseError: (:) [New-AzureDeployment], StorageException
+ FullyQualifiedErrorId :
In order to for Microsoft Support to determine that such errors were the result of a storage account timeout, a traffic capture had to be initiated, which shows the static timeout period set by Powershell and a timeout error message not reflected in the user-facing exception above.