Tried searching a bit here, but couldn't really find it. We're hitting a bug (or well, documented limit) in azure - it is not possible to have more than 10 deployment locations (i.e. where the

deployment

itself is run from, not where the resources are). I do not see any option of setting

deploymentLocation

anywhere - I would think this could be a provider level command. In Bicep or throgh powershell/az-cli you can run stuff like this:

az deployment sub create --location <region> ---template file....

where the

<region>

is the region of the `deployment`NOT the actually deployed resources. I would very much like to know if a similar parameter is possible in pulumi. Source of limitation: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#management-group-limits