ResourceNotFound: The Resource 'Microsoft.X/...' under resource group 'y' was not found
The specific resource doesn’t exist in that resource group/subscription — wrong name, group or subscription, or it was deleted.
Seen on:
Azure
Meaning
Commands with --name/--resource-group or IDs from another environment fail. In templates, references to existing resources (existing keyword) must point at the right scope.
Common causes
- Wrong name or resource group
- Wrong subscription
- Resource deleted or not yet created
- Template references existing resource in another scope
⚡ Quick fix
- List resources in the group to confirm the name
- Set the correct subscription
- Use the full resource ID
Detailed fix by platform
Azure CLI
az resource list -g rg-app --query "[].{name:name,type:type}" -o table
How to diagnose
- Scope — Subscription and group
- Name — Exact resource name/type
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- Android resource linking failed AAPT: error: resource x (aka y) not found — Android resource linking failed
- android:attr/lStar not found AAPT: error: resource android:attr/lStar not found
- AnotherOperationInProgress Conflict: AnotherOperationInProgress — Another operation is in progress on the resource
Most viewed in Azure
- AADSTS50076 Azure AD (Entra ID): AADSTS50076 / AADSTS50079 — multi-factor authentication required
- AuthorizationPermissionMismatch Azure Storage: AuthorizationPermissionMismatch (403) — This request is not authorized to perform this operation using this permission
- AADSTS700016 Azure AD (Entra ID): AADSTS700016 Application not found in the directory
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026