Microsoft Entra ID SCIM Validator test failing DELETE /Users/Id

Yes. Based on the documented behavior, returning 404 Not Found for GET /Users/{id} after a delete is valid, and the validator message appears inconsistent with the request it actually issued.

Supported behavior is:

1. DELETE /Users/{id} returns 204 No Content on success.
2. A subsequent GET /Users/{id} for a non-existent user returns 404 Not Found.
3. A filtered query for a missing user, such as GET /Users?filter=..., returns 200 OK with totalResults: 0 and an empty Resources array.

That means these are two different expected patterns:

• Lookup by ID after deletion: 404 Not Found
• Filter query after deletion or for a missing user: 200 OK with zero results, or in some validator scenarios a returned user with active=false

Since the failed test report shows the validator sent GET /Users/{id} but the failure text says GET filter on deleted User should not return any Users or should return a User with active set to false, the failure text does not match the request pattern. That points to a SCIM Validator issue rather than a requirement for different endpoint behavior.

There is also prior Microsoft Q&A context showing known SCIM Validator bugs in other tests, with guidance to ignore clearly incorrect validator failures in those cases.

• Tutorial: Develop and plan provisioning for a SCIM endpoint in Microsoft Entra ID
• Tutorial: Validate a SCIM endpoint
• Microsoft Entra ID SCIM Validator test failing PATCH update userName - Microsoft Q&A