This is expected. See: https://learn.microsoft.com/en-us/azure/active-directory/app-provisioning/known-issues#null-attribute-cant-be-provisioned
It's something we hope to enable at a future time but I can't provide an ETA.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello,
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 }
]
PATCH:
{
"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 }
]
The PATCH :
Moreover, in "Provision On Demand detail" Azure screen :
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 ?
This is expected. See: https://learn.microsoft.com/en-us/azure/active-directory/app-provisioning/known-issues#null-attribute-cant-be-provisioned
It's something we hope to enable at a future time but I can't provide an ETA.