Unable to use the data source azurerm_storage_table_entity

[NickG158]

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 "+1" or "me too" comments, 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.7.5

AzureRM Provider Version

3.96.0

Affected Resource(s)/Data Source(s)

azurerm_storage_table_entity

Terraform Configuration Files

data "azurerm_storage_table_entity" "example" {
  table_name           = "exampletablename"
  storage_account_name = "examplestorageaccountname"
  partition_key        = "1"
  row_key              = "2"
}

Debug Output/Panic Output

data.azurerm_storage_table_entity.example: Reading...

Planning failed. Terraform encountered an error while generating this plan.

╷
│ Error: parsing Account ID: expected the account "" to use a domain suffix of "core.windows.net"
│
│   with data.azurerm_storage_table_entity.example,
│   on aa.tf line 1, in data "azurerm_storage_table_entity" "example":
│    1: data "azurerm_storage_table_entity" "example" {
│
╵

Expected Behaviour

Return the storage table entity

Actual Behaviour

Error above returned when using v3.96.0 of the azurerm provider. Working on 3.95.0 and below.

Steps to Reproduce

terraform init, using the v3.96.0 provider
terraform plan / terraform apply

Important Factoids

No response

References

#24798

terraform-provider-azurerm/internal/services/storage/storage_table_entity_data_source.go

Line 86 in ccdb7fa

accountId, err := accounts.ParseAccountID(accountName, storageClient.StorageDomainSuffix)

[manicminer]

@NickG158 Thanks for reporting this and apologies for this regression. We'll work on a fix as soon as possible.

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