azurerm_storage_container - storage_account_name deprecated but cannot migrate to storage_account_id

[dkirrane]

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

AzureRM Provider Version

4.9.0

Affected Resource(s)/Data Source(s)

azurerm_storage_container

Terraform Configuration Files

resource "azurerm_storage_container" "example" {
  name                  = "vhds"
  storage_account_name  = azurerm_storage_account.this.name
  storage_account_id    = azurerm_storage_account.this.id
  container_access_type = "private"
}

Debug Output/Panic Output

The Terraform Plan shows Forces replacement of the container when I add storage_account_id and remove the deprecated storage_account_name

If it add both storage_account_id and storage_account_name I get only one of storage_account_id,storage_account_name can be specified

Expected Behaviour

I should be able to migrate from storage_account_id and storage_account_name
There should be a migration path called out in https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/guides/4.0-overview

Actual Behaviour

Cannot remove deprecated storage_account_name.

Steps to Reproduce

1. Create an azurerm_storage_container with storage_account_name
2. Try change it to using storage_account_id. Terraform Plan shows Forces replacement

Important Factoids

No response

References

• azurerm_storage_container - support for the storage_account_id property (#27733)

[mybayern1974]

Duplicate with #27942

[rcskosir]

Thanks for taking the time to submit this issue. It looks like this is a duplicate of #27942. We like to try to keep discussions consolidated, so we’re going to close this new issue in favor of #27942.

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