A 204 response to a PATCH is perfectly fine in production as far as interoperability is concerned with Entra user provisioning. This was previously flagged as an issue with the SCIM validator, but I believe that it has already been changed to not flag a 204 as problematic.
Azure AD SCIM provisioning - Expected response for resource modification request with PATCH
Hi Team,
We are developing a SCIM provisioning server application as per standards mentioned in SCIM documentation - https://datatracker.ietf.org/doc/html/rfc7644#section-3.5.2 and Azure documentation -https://learn.microsoft.com/en-us/azure/active-directory/app-provisioning/use-scim-to-provision-users-and-groups.
For the expected response for patch methos, SCIM documentation states it support both 200(with attributes) and 204 response code.
On successful completion, the server either MUST return a 200 OK
response code and the entire resource within the response body,
subject to the "attributes" query parameter (see Section 3.9), or MAY
return HTTP status code 204 (No Content) and the appropriate response
headers for a successful PATCH request.
Whereas the azure document has a sample with 200 response code only.
Please let us know if 204 response code is supported for the user updates while integrating out SCIM application with Azure AD auto user provisioning application.
Microsoft Security | Microsoft Entra | Microsoft Entra ID
-
Danny Zollner 10,801 Reputation points Microsoft Employee Moderator
2023-10-18T18:39:48.42+00:00