azurerm_servicebus_namespace created in UAE North enables zone redundancy by default even with Standard SKU

[PavelPikat]

Is there an existing issue for this?

• I have searched the existing issues

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.

Terraform Version

1.8.5

AzureRM Provider Version

3.112.0

Affected Resource(s)/Data Source(s)

azurerm_servicebus_namespace

Terraform Configuration Files

resource "azurerm_servicebus_namespace" "me" {
  name                = "me1-test-sbn"
  location            = "UAE North"
  resource_group_name = "me1-test-sbn-rg"
  sku                 = "Standard"
  capacity            = 0
  zone_redundant      = false
}

resource "azurerm_servicebus_namespace" "eu" {
  name                = "eu1-test-sbn"
  location            = "West Europe"
  resource_group_name = "eu1-test-sbn-rg"
  sku                 = "Standard"
  capacity            = 0
  zone_redundant      = false
}

Debug Output/Panic Output

-

Expected Behaviour

Service Bus Namespaces with Standard SKU should have zone_reduntant set to false according to documentation.
If the user specifies zone_reduntant = false when creating the Namespace, then Zone Redundancy should not be enabled, regardless of the target Azure Region - Europe or UAE

Actual Behaviour

When the user creates Standard SKU Service Bus Namespace in West Europe, it is created with Zone Redundancy disabled.
When the user creates Standard SKU Service Bus Namespace in UAE North, it is created with Zone Redundancy enabled, even though the user specified zone_redundant = false in Terraform configuration

Steps to Reproduce

Apply sample Terraform configuration attached to this issue that creates two namespaces: in EU and UAE. EU will have zone redundancy disabled and running terraform apply will not detect any changes.
UAE namespace will have zone redunancy enabled, and Terraform will mark resource for replacement after running terraform apply second time because actual state does not match the desired state (zone_redundant = false)

Important Factoids

No response

References

No response

[xiaxyi]

Thanks @PavelPikat for raising this issue, the zoneRedundant feature has been changed. I will update the provider document accordingly.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.