Issue Summary

This is reproducible on Data Center: no (Applicable only to Atlassian Cloud)

Steps to Reproduce

1. Have a SCIM provisioning configured for Azure/Entra AD
2. Configure the attribute mapping to map the Job Title attribute to Atlassian
3. Set a value for the Job title and provision the user
4. The user gets provisioned and the job title with the respective value is set on Atlassian side
5. Change the job title attribute to an empty value and try to provision the user again
6. Azure does not provision the account reporting "Skip Redundant Export" on the account
7. Changing the job title to any other value than empty works as expected.

Expected Results

The Entra/Azure should be able to update the user and his job title on Atlassian side with the null value. 

Other IDPs such as Okta are able to handle that Update. That only seems to fail for Azure/Entra and thus this is likely an error on Azure side/Entra. But we need to have visibility of that from our side.

Actual Results

The below exception is thrown in the Azure side and no information is sent to Atlassian (no API call is made as well, so there are no logs or requests on our side):

Workaround

Currently, there is no known workaround for this behavior except adding a character on the field to have the title updated (using a space character does not work either as the field seems to expect a "regular" character (such as a letter).

Additional notes:

Other IDPs such as Okta are able to handle that Update. That only seems to fail for Azure/Entra and thus this is likely an error on Azure side/Entra. But we need to have visibility of that from our side.