ResourceGroupNotFound: Resource group 'x' could not be found
The resource group doesn’t exist in the subscription the command or deployment is using.
Seen on:
Azure
Meaning
The active subscription in Azure CLI/PowerShell is often not the one you expect. Typos, groups deleted or not yet created in a pipeline are other causes.
Common causes
- Wrong active subscription
- Typo in the resource group name
- Group not created yet / deleted
- Service principal without access to that subscription
⚡ Quick fix
- az account show / az account set --subscription
- az group list to find the name
- Create the group before deploying
Detailed fix by platform
Azure CLI
- bash
az account show --query name az account set --subscription "Production" az group create -n rg-app -l westeurope
How to diagnose
- Subscription — Active one
- Name — Exact group name
- Access — Can the identity see it?
🔧 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
- AnotherOperationInProgress Conflict: AnotherOperationInProgress — Another operation is in progress on the resource
- InvalidTemplateDeployment ARM/Bicep: DeploymentFailed / InvalidTemplateDeployment / InvalidTemplate
- LocationNotAvailableForResourceType LocationNotAvailableForResourceType / InvalidResourceLocation
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