Why are Genesys Cloud user records unexpectedly changed after an update to Azure Active Directory?

Note: This article applies to Genesys Cloud SCIM (Identity Management).

Occasionally when Microsoft updates Azure Active Directory, Microsoft also updates the Genesys Cloud for Azure Active Directory user provisioning app. As a result, unexpected changes may be made to Genesys Cloud user records. In some cases, these changes may affect the ability of your users to work in Genesys Cloud.

Identify the scope of changes

Start by reviewing Microsoft’s audit logs for Azure Active Directory:

For general information about the types of logs available, see Audit logs in Azure Active Directory.
To see what data was sent to Genesys Cloud as part of a provisioning operation, view the provisioning logs in Azure Active Directory.

Next, review audit log information in Genesys Cloud:

Use the Genesys Cloud audit log viewer to review certain changes made by the Azure AD provisioning app.
For more information about all of the data that is captured in the Genesys Cloud audit log, see Action Catalog.

Fix incorrect attribute mappings

If Microsoft has incorrectly updated attributes to Genesys Cloud user records, go to the Genesys Cloud for Azure Active directory user provisioning app and update the mappings there. Depending on the changes that were made, you may need to manually intervene after you reset the attribute mappings to your desired state.

Additionally, you may want to contact Microsoft Support and open a service request.