Open
Description
Description
It looks like there is no rate limit handling in place for Bicep/ARM deployments.
We are experiencing a lot of failed deployments due to change over from global rate limits to bucket rate limits.
The deployment should be improved so it handles the rate limits correctly and continues the deployment without stopping.
I am not sure if this is the correct place to report this, if its incorrect please guide me to the correct channel thanks :)
Issue script & Debug output
New-AzResourceGroupDeployment
Environment data
N/A
Module versions
N/A
Error output
No response