No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Hi, we are trying to update a `azure-native:dbforpostgresql:Server` database (just changing the tags and `administratorLoginPassword` ) but we are getting a `Code="AvailabilityZoneNotAvailable" Message="Specified availability zone is not supported in this region. Please choose a different availability zone."`  error that doesn't seem to make sense to me - we are not changing anything that could affect AZ's.

This happens to me if I am recreating resources over and over. I think there is a rate limiting response that is not recognized, somewhere. Usually if I wait a few minutes the problem will go away. I know that's not a great answer but I dont know what the root of this actually is.

```    ~ azure-native:dbforpostgresql:Server: (update) 🔒
        [id=redacted]
        [urn=redacted]
        [provider=urn:pulumi:redacted]
      + administratorLoginPassword: [secret]
      ~ tags                      : {
          + automation  : "redacted.iac"
          - location    : "westeurope"
          - module      : "redacted"
          + stack       : "redacted"
          - subscription: "redacted"
          + type        : "Pulumi.AzureNative.DBforPostgreSQL.Server"
        }```
This is the diff

yes, Based on your original questions I am assuming this is an existing resource. if that is the case it is likely just a capacity constraint.

but the resource already exists, why would capacity matter here?

because Azure "needs" to recreate the resource which means it has to have capacity so that you dont have downtime. If you want to avoid this you need to use HA. Check this out. <https://learn.microsoft.com/en-us/answers/questions/1659815/availability-zone-became-unavailable-how-can-i-swi>

I guess we'll have to raise a ticket with MS, thanks for the link!