Error map
MissingSubscriptionRegistration MissingSubscriptionRegistration: The subscription is not registered to use namespace 'Microsoft.X'
Azure · layer 6, Platform & cloud
Centre: this error. First ring: errors it is linked with (8). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (8)
ARM/Bicep: DeploymentFailed / InvalidTemplateDeployment / InvalidTemplate
An Azure Resource Manager (ARM/Bicep/Terraform) deployment failed; the inner error under “details” has the real cause.
Azure: AuthorizationFailed — The client does not have authorization to perform action
The signed-in identity (user, service principal or managed identity) lacks an Azure RBAC role for that action on that scope.
ScopeLocked: The scope cannot perform write/delete operation because following scope(s) are locked
A resource lock (CanNotDelete or ReadOnly) on the resource, group or subscription blocks the change.
SubscriptionNotFound: The subscription 'x' could not be found
The subscription ID doesn’t exist in the current tenant or the identity has no access to it.
ResourceGroupNotFound: Resource group 'x' could not be found
The resource group doesn’t exist in the subscription the command or deployment is using.
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.
LocationNotAvailableForResourceType / InvalidResourceLocation
The resource type isn’t offered in that region, or the resource already exists in a different region than the template says.
Conflict: AnotherOperationInProgress — Another operation is in progress on the resource
Azure is still processing a previous change on the same resource, so new operations are rejected until it finishes.
Two steps away (19)
Azure: SkuNotAvailable / QuotaExceeded when creating a VM or resource
The VM size isn’t offered in that region/zone for your subscription, or you’ve hit the vCPU quota.
Stack is in ROLLBACK_COMPLETE state and can not be updated
The stack’s first creation failed and rolled back; a stack in ROLLBACK_COMPLETE can only be deleted, not updated.
CloudFormation stack in UPDATE_ROLLBACK_FAILED
An update failed, and then the rollback also failed, leaving the stack stuck until you continue the rollback.
AWS S3: AccessDenied (403) when calling GetObject / PutObject
An IAM policy, bucket policy, ACL/ownership setting, Block Public Access or KMS key policy denied the S3 request.
HTTP 403 Forbidden
The server understood the request but refuses to authorize it — you (or the server process) are not allowed to access this resour…
Azure Storage: AuthorizationPermissionMismatch (403) — This request is not authorized to perform this operation using this permission
You’re accessing blob/queue data with Microsoft Entra ID, but the identity has only management roles (Owner/Contributor) — not a…
RequestDisallowedByPolicy: Resource 'x' was disallowed by policy
An Azure Policy assignment denied the request — allowed locations, SKUs, required tags, public network access, etc.
Azure AD (Entra ID): AADSTS700016 Application not found in the directory
The client ID in your sign-in request doesn’t exist in the tenant you’re authenticating against.
Azure AD (Entra ID): AADSTS50076 / AADSTS50079 — multi-factor authentication required
A Conditional Access policy requires MFA, but the sign-in flow (often a script, legacy client or ROPC password grant) can’t compl…
AADSTS50126: Error validating credentials due to invalid username or password
Microsoft Entra ID (Azure AD) rejected the sign-in because the username or password is wrong — or the flow can’t use passwords fo…
Kubernetes: Pod stuck in Pending — FailedScheduling: 0/3 nodes are available
The scheduler can’t find a node that satisfies the pod’s resource requests, selectors, taints or volume constraints.
Kubernetes: Pod Evicted — The node was low on resource: memory / ephemeral-storage
The kubelet removed the pod because its node ran short of memory or disk.
Error creating: pods is forbidden: exceeded quota: compute-resources, requested: limits.memory=1Gi, used: ..., limited: ...
The namespace’s ResourceQuota doesn’t have room for the new pod’s requests/limits (or object count).
S3 PermanentRedirect: The bucket you are attempting to access must be addressed using the specified endpoint
The request went to the wrong S3 region/endpoint for that bucket.
InvalidKeyPair.NotFound: The key pair 'x' does not exist
The key pair name you passed doesn’t exist in that region (key pairs are regional).
InvalidAMIID.NotFound: The image id '[ami-xxxx]' does not exist
The AMI ID isn’t available in this region/account — AMI IDs are regional and private AMIs must be shared.
HTTP 409 Conflict
The request conflicts with the current state of the resource — e.g. a duplicate or an edit based on an outdated version.
java.util.ConcurrentModificationException
A collection was modified while being iterated (even in a single thread).
HTTP 412 Precondition Failed
A conditional request header (If-Match, If-Unmodified-Since) didn’t match the current state of the resource.
Map another error
Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException