Azure Files creation - unexpected status 400

[acelebanski]

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

Affected Resource(s)/Data Source(s)

azurerm_storage_share_file

Terraform Configuration Files

https://github.com/PaloAltoNetworks/terraform-azurerm-swfw-modules/blob/main/examples/dedicated_vmseries/main.tf

Debug Output/Panic Output

│ Error: checking for existing File "init-cfg.txt" (Directory Path "config" / Share Name "fw-in-2" / Account "Account \"smplngfwbtstrp1998\" (IsEdgeZone false / ZoneName \"\" / Subdomain Type \"file\" / DomainSuffix \"core.windows.net\")"): executing request: unexpected status 400 (400 The specifed resource name contains invalid characters.) received with no body
│ 
│   with module.bootstrap["bootstrap"].azurerm_storage_share_file.this["fw-in-2-files-init-cfg-sample-txt"],
│   on ../../modules/bootstrap/main.tf line 179, in resource "azurerm_storage_share_file" "this":
│  179: resource "azurerm_storage_share_file" "this" {

Expected Behaviour

On provider version 3.97.1, I am not able to create files in Azure File Storage which I was able to do earlier. I even tested this by setting the provider version to 3.95 and it worked like a charm.

Actual Behaviour

No response

Steps to Reproduce

No response

Important Factoids

No response

References

No response

[acelebanski]

Hey @manicminer, I just found #25353 issue although closed. It looks like it might solve my problem. This bugfix isn't released yet, is it? Any idea when the fix will be released?

[rcskosir]

@acelebanski Thanks for taking the time to open this issue. #25404 has been released with 3.98. Since the fix is released, I am going to mark this issue as closed.

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