This is regarding the Automatic User Provisioning using SCIM feature of Azure Active Directory as described in this article (https://docs.microsoft.com/en-us/azure/active-directory/active-directory-scim-provisioning).
After assigning or un-assigning user to/from custom apps, as expected, Azure sent out a RESTful PATCH request to change to “active” attribute of the user resource, a singular-valued attribute, to True or False.
The issue is that the HTTP body payload seems to be incorrect. The “value” specified by Azure somehow was an array and somehow looked like a value for multi-valued attribute, which seems incorrect, as the user “active” attribute is a singular-valued attribute.
{"schemas":["urn:ietf:params:scim:api:messages:2.0:PatchOp"],"Operations": [ {"op":"Replace","Path":"active","Value": [ {"$ref":null,"value":"True"} ] } ] }
I believe the payload should look something like this:
{"schemas":["urn:ietf:params:scim:api:messages:2.0:PatchOp"],"Operations": [ {"op":"Replace","Path":"active","Value": "True" } ] }
Can someone in Azure Engineering team take a look at this issue?
Thanks a lot!