I'm no longer able to replicate this...
Something must have change as right now the only I'm unable to see the changes log in the details pane, where as they were showing up at least a week ago.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
The app provisioner is able to set nested object properties for the employeeOrgData (even using dynamic expressions) and passwordProfile (provided only password sub-property is set) that exist in the AAD user schema. Even though this is undocumented I assumed it would be possible to map such nested object properties using a convention similar to JSONPath expressions for each sub-property. For instance this meant adding the target attributes "employeeOrgData.businessUnit" and "employeeOrgData.costCenter" with the "String" data type.
However it does not properly detect changes for nested properties such as employeeOrgData. I find that the business unit and/or cost center names are always described as being changed in the log output.
I'm no longer able to replicate this...
Something must have change as right now the only I'm unable to see the changes log in the details pane, where as they were showing up at least a week ago.
@Fernando Almeida
Statement "... For instance this meant adding the target attributes ..."
I assume you meant source attribute from AAD? Curious, did you use https://portal.azure.com/?Microsoft_AAD_Connect_Provisioning_forceSchemaEditorEnabled=true then edit the AzureAD schema?
I'm having a similar problem with employeeOrgData's subAttributes.
Here's my question post >
SCIM Provisioning of employeeOrgData subAttributes [ costCenter | division ]
https://learn.microsoft.com/en-us/answers/questions/1150096/scim-provisioning-of-employeeorgdata-subattributes.html
/paul