Deletion of user attribute is not patched by SCIM.

Fabrice Dutron 21 Reputation points


In Azure, If I change the phone number from let's say "05" to "05 06", there is a patch which is send to my SCIM server :
Preceding GET :
"phoneNumbers": [
{ "value": "05", "display": "05", "type": "work", "primary": true },
{ "value": "06", "display": "06", "type": "mobile", "primary": false }
"schemas" : [ "urn:ietf:params:scim:api:messages:2.0:PatchOp" ],
"Operations" : [{
"op" : "replace",
"path" : "phoneNumbers[type eq \"work\"].value",
"value" : "05 06"

Now if I edit the phone number in Azure from "05 06" to "" then :
Preceding Get :
"phoneNumbers": [
{ "value": "05 06", "display": "05 06", "type": "work", "primary": true },
{ "value": "06", "display": "06", "type": "mobile", "primary": false }

  • no patch operation on the phone numbers

Moreover, in "Provision On Demand detail" Azure screen :

  • "Import User" screen : I do no see the phone number. So it seems that Azure has correctly removed the phone number.
  • "Match user between source and target system" screen : I can see the line "phoneNumbers[type eq "work"].value | 05 06". So it seems that Azure can read the remote value.

So, should I not have a replace patch operation or maybe a remove operation on the work phone number ?

I Have the same behaviour with the city by exemple. Am I missing something here ?

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
20,551 questions
0 comments No comments
{count} votes

Accepted answer
  1. Danny Zollner 9,861 Reputation points Microsoft Employee

    This is expected. See:

    It's something we hope to enable at a future time but I can't provide an ETA.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful