Missing resources, wrong scope, lifecycle drift, and state mismatches.
Last reviewed: March 4, 2026|56 mapped errors|Page 3 of 4
Resource-state errors appear when identifiers, region or account scope, lifecycle state, or consistency timing do not match request assumptions.
Provider-specific error pages mapped to this category (56 total). Showing 31-45.
Azure LeaseIdMissing means a blob or container currently has an active lease, but the request did not include the required lease ID.
ARM returns `ResourceGroupNotFound` when the target resource group does not exist in the active subscription context.
Azure ResourceModified means a write targeted resource state that changed after the caller read it, so the stale mutation was rejected.
Azure ResourceNotFound means ARM or a resource provider could not resolve the requested resource ID in the exact subscription, resource group, provider, type, and location context.
ARM returns `StorageAccountNotFound` when the referenced storage account name, resource group, or subscription context does not resolve.
Azure returns `Unauthorized` (401) when request authentication is missing, invalid, expired, or mismatched for the target endpoint.
Azure returns `VMExtensionNotFound` when a VM operation references an extension resource name that does not exist on the target VM.
Azure returns `VMNetworkInterfaceNotFound` when a VM operation references a network interface that cannot be resolved in the current scope.
Azure returns `VMSSInstanceNotFound` when a requested scale set VM instance ID cannot be resolved in the target scale set context.
GCP BILLING_DISABLED means the consumer project has no active billing account attached or its linked billing account is not in an active state for service usage.
GCP NOT_FOUND means the target entity cannot be resolved in the requested project, location, parent collection, or service-specific resource namespace.
GCP OUT_OF_RANGE means the request is structurally valid, but a requested value, offset, cursor, or range falls outside the currently valid bounds.
HTTP 201 Created means the request succeeded and a new resource was created as a result. The server should return the new resource URI in the Location response header.
HTTP 204 No Content is a success status code indicating that the server has fulfilled the request but there is no data to return in the response body. It is the standard response for successful DELETE operations and PUT updates where no representation is needed.
HTTP 205 Reset Content is a success status code that instructs the client to reset the document view that initiated the request. It is the semantic standard for clearing form inputs or resetting a UI state after a successful submission without providing a response body.
Compare Guide
Use 403 for explicit access denial, or 404 to conceal resource existence when security policy requires reducing endpoint and object enumeration risk.
Compare Guide
Learn when to return 404 (missing or temporary absence) versus 410 (intentional permanent removal), including redirect and cache implications.
Playbook
Use this playbook to separate temporary missing-resource lookups from permanent removals, then fix scope, lifecycle, and identifier drift safely.
Temporary 404s often resolve after propagation or deployment completion, while permanent removals are typically explicit lifecycle events (for example 410 semantics).
Many control planes are eventually consistent. Read-after-write visibility can lag and briefly return not-found responses.
Confirm exact scope and identifier tuple: resource name, region, account/subscription/project, and parent container.