Applying azurerm_servicebus_queue fails on Basic tier

[ronny-standtke]

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.9.5

AzureRM Provider Version

4.0.1

Affected Resource(s)/Data Source(s)

azurerm_servicebus_queue

Terraform Configuration Files

resource "azurerm_servicebus_queue" "servicebus_my_queue" {
  name         = "my-queue"
  namespace_id = azurerm_servicebus_namespace.servicebus_namespace.id

  default_message_ttl = "P1D"
}

Debug Output/Panic Output

╷
│ Error: unexpected status 400 (400 Bad Request) with error: MessagingGatewayBadRequest: SubCode=40000. The property 'AutoDeleteOnIdle' cannot be set when creating a Queue because the namespace 'servicebus-ns' is using 'Basic' tier. To know more visit https://aka.ms/sbResourceMgrExceptions
│ Parameter name: AutoDeleteOnIdle. TrackingId:d078a499-9f94-413a-b4dc-f1ac4dc36dfa_G14, Timestamp:2024-09-03T11:53:31
│ 
│   with module.service_bus.azurerm_servicebus_queue.servicebus_my_queue,
│   on service-bus/service-bus.tf line 31, in resource "azurerm_servicebus_queue" "servicebus_my_queue":
│   31: resource "azurerm_servicebus_queue" "servicebus_my_queue" {
│ 
╵

Expected Behaviour

auto_delete_on_idle should be (known after apply)

Actual Behaviour

auto_delete_on_idle is set to default (P10675199DT2H48M5.4775807S")

Steps to Reproduce

No response

Important Factoids

Running Azure in Germany

References

No response

[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.