Error AtlasError Documentation and Resolution
Back to search

ARM

Azure ARM deployment failed with NotFound

Code=NotFound

Azure Resource Manager couldn't find a resource required by the deployment, often because of a missing dependency, wrong name, or wrong scope.

NotFounddeployment

Observed message

Code=NotFound

Why it happens

  • A dependent resource name is wrong or the resource does not exist.
  • The deployment references a resource before it has been created.
  • The deployment targets a different subscription or resource group than expected.

How to fix it

  1. Verify the resource name, type, and scope used in the deployment.
  2. Add the required dependency if the missing resource is created in the same template.
  3. Confirm the subscription and resource group context before rerunning.

Official reference

Microsoft Learn: Common Azure deployment errors

Related errors

InvalidTemplateDeploymentAzure ARM deployment failed because the template deployment is invalidAuthorizationFailedAzure ARM deployment failed with AuthorizationFailedBadRequestAzure ARM deployment failed with BadRequestConflictAzure ARM deployment failed with Conflict

Explore more

deploymentBrowse more deployment errors
Azure NotFound during ARM deployment: causes and fixes | Error Atlas