You prevent this error by setting a dependency in the web app. The web app fails with an error that the App Service plan resource can't be found because it doesn't exist yet. If you haven't specified that the web app depends on the App Service plan, Resource Manager creates both resources at the same time. Resource Manager optimizes deployments by creating resources in parallel, when possible.įor example, when you deploy a web app, the App Service plan must exist. If you get this error when deploying a template, you may need to add a dependency. Find the resource you're trying to use and examine the resource name, resource group, and subscription. If you can't verify the properties, sign in to the Microsoft Azure portal. Many commands provide a subscription parameter that lets you specify a different subscription than the current context.
You can change the subscription with Set-AzContext or az account set. If you're using PowerShell or Azure CLI, check that you're running commands in the subscription that contains the resource. When you receive this error while doing a management task, check the values you provided for the resource. Resource Manager needs to retrieve the properties for a resource, but can't find the resource in your subscription. Message=The Resource 'Microsoft.Storage/storageAccounts/ was not found. The ResourceNotFound error returns a result similar to: Code=ResourceNotFound Message=Cannot find ServerFarm with name exampleplan. The NotFound error returns a result similar to: Code=NotFound There are two error codes that indicate the resource can't be found.
For example, if you try to add tags to a resource that doesn't exist, you receive this error. You also see this error when doing management tasks and Azure Resource Manager can't find the required resource. Typically, you see this error when deploying resources with a Bicep file or Azure Resource Manager template (ARM template). This article describes the error you see when a resource can't be found during an operation.
0 kommentar(er)
