Azure / Azure/bicep-registry-modules
[AVM Module Issue]: Storage account fails while adding private endpoint with below error
Open
@sethsteenken is already working on this.
Since Nov 13, 2025.
Class: Resource Module :package:
Needs: Immediate Attention :bangbang:
Needs: Triage :mag:
Status: Response Overdue :triangular_flag_on_post:
Type: AVM :a: :v: :m:
Type: Bug :bug:
- Dominant language
- Bicep
- Stars
- 737
- Forks
- 564
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 30
Description
Check for previous/existing GitHub issues
- I have checked for previous/existing GitHub issues
Issue Type?
Bug
Module Name
avm/res/storage/storage-account
(Optional) Module Version
0.26.2
Description
When deploying storage account with Private end points getting below error:
{
"code": "DeploymentFailed",
"target": "/subscriptions/****/resourceGroups/****/providers/Microsoft.Resources/deployments/****",
"message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.",
"details": [
{
"code": "ResourceDeploymentFailure",
"target": "/subscriptions/****/resourceGroups/****/providers/Microsoft.Network/privateEndpoints/****",
"message": "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.",
"details": [
{
"code": "StorageAccountOperationInProgress",
"message": "Call to Microsoft.Storage/storageAccounts failed. Error message: An operation is currently performing on this storage account that requires exclusive access.",
"details": []
}
]
}
]
}
(Optional) Correlation Id
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.