How to Fix Request_ResourceNotFound
Error message
Request_ResourceNotFound: Resource '<id>' does not exist or one of its queried reference-property objects are not present.
If you're seeing "Request_ResourceNotFound", you're not alone. Here's what it means, why it happens, and the steps to resolve it.
What this error means
Graph cannot find the object you asked for. Either the ID is wrong, the object was deleted, or you're querying the wrong tenant.
Why this happens
Common causes: typo in the ID, the object was soft-deleted, replication delay after a recent create, or you authenticated to a different tenant than expected.
Step-by-step fix
Confirm which tenant your session is connected to.
command(Get-MgContext).TenantIdLook up the object by a stable property to get its current ID.
commandGet-MgUser -Filter "userPrincipalName eq 'jdoe@contoso.com'"If the object was just created, wait 30–60 seconds for replication and retry.
Check the deleted items container in case it was recently removed.
commandGet-MgDirectoryDeletedItemAsUser -DirectoryObjectId <id>
Affected products
Microsoft Graph PowerShell
Still broken? Try these
- Try the same query in Graph Explorer with the same account.
- Verify the ID is from the same tenant as the session.
- If the object is in a different directory (B2B guest), query it by UPN instead of ID.
Related errors
Frequently asked questions
What does "Request_ResourceNotFound" mean?
Graph cannot find the object you asked for. Either the ID is wrong, the object was deleted, or you're querying the wrong tenant.
What causes "Request_ResourceNotFound"?
Common causes: typo in the ID, the object was soft-deleted, replication delay after a recent create, or you authenticated to a different tenant than expected.
How do I fix "Request_ResourceNotFound"?
1. Confirm which tenant your session is connected to. 2. Look up the object by a stable property to get its current ID. 3. If the object was just created, wait 30–60 seconds for replication and retry. 4. Check the deleted items container in case it was recently removed. Always test changes in a non-production environment first.
Browse more errors in Microsoft Graph PowerShell: Fix Microsoft Graph PowerShell errors. Insufficient privileges, invalid object ID, missing cmdlets, token problems, and more. Or paste your own error into the error decoder tool to find a match. You can also go back to the homepage to browse common errors by topic.