Share via

"DeploymentFailed" for az deployment group create --resource-group ...

lili zhang 190 Reputation points
2025-07-21T23:06:09.48+00:00

The deployment of

"az deployment group create --resource-group rg-enterprise-networking-hubs-eastus2 --template-file networking/hub-default.bicep"

was failed with the following error:

{ "status":"Failed","error":{ "code":DeploymentFailed","target":"/subscriptions/....../resourceGroups/rg-enterprise-networking-hubs-eastus2/providers/Microsoft.Resources/deplotments/hub-default","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":"ResourceDeplotmentFailure","target":"/subscriptions/....../resourceGroups/rg-enterprise-networking-hubs-eastus2/providers/Microsoft.Network/azureFirewalls/fw-eastus2-hub","message":"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.","details":[ { "code":"InternalServiceError","message":"An error occurred.","details":[]}]}]} }

Please help me out with this. Thanks.

Azure Virtual Network
Azure Virtual Network

An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.


1 answer

Sort by: Most helpful
  1. Anonymous
    2025-07-22T01:42:02.0833333+00:00

    Hello lili zhang

    We understood that y you're running into a "DeploymentFailed" error while using the az deployment group create command. This typically happens when an underlying resource fails during the provisioning as per error it is the deployment failed due to an issue with the Azure Firewall resource (fw-eastus2-hub) reaching a terminal provisioning state 'Failed'.

    We request you to please check below details to resolve the issue

    1.Since the error is related to the Azure Firewall, check its provisioning state and error details:

    az resource show --resource-group rg-enterprise-networking-hubs-eastus2 --name fw-eastus2-hub --resource-type "Microsoft.Network/azureFirewalls"

    2.The firewall must be deployed in a subnet named AzureFirewallSubnet with a minimum /26 address space.

    • Route Conflicts: Conflicting UDRs (User Defined Routes) can cause provisioning to fail.
    • Missing Dependencies: Ensure all required resources (e.g., public IPs, route tables) are correctly defined and available.

    3.Make sure that the parameters and configurations used in your Bicep template for the Azure Firewall are correct. Check for any dependencies or required fields that might be missing.

    4.We suggest you review the azure deployment error troubleshoot document:

    https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-resource-manager/troubleshooting/common-deployment-errors.md

    Since InternalServiceError can be caused by transient issues (e.g., Azure service disruptions), retry the deployment after a short wait:

    Additionally, we have suggested to deploy in a different region example: easts instead of eastus2 as likely there is a resource from previous deployment causing some issues.


    Hope the above answer helps! Please let us know do you have any further queries.

    If an answer has been helpful, please consider accepting the answer to help increase visibility of this question for other members of the Microsoft Q&A community. If not, please let us know what is still needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!

    User's image

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.