SCIM issue | Community
Skip to main content
Explorer
June 27, 2026
Question

SCIM issue

  • June 27, 2026
  • 0 replies
  • 3 views

Small business so we don’t add users often, but has something change in zoom in the recent past? Azure provisioning for users is no longer working. New users to be provisioned and existing users are all showing the same error in the Azure log, which is clearly a false positive. These new users have never used their domain email with zoom before and why would it error out on existing users with this as well?

 

This entry is being skipped, because it conflicts with an existing entry hosted in a different tenant of the target application. Almost nothing can be done, except possibly by the person corresponding to the entry. That person may have created a personal account in the target application, using her or his organizational email address, for example. So, unless the person can be contacted, and is willing to delete their pre-existing account, the conflict will persist. For many applications, the skipping of the entry will have no adverse consequences; all that matters is that the person corresponding to the entry in the source directory also has a record somewhere in the target application, and that is indeed the case.

SkipReason

Conflict
 

The only changes I’ve made so far to trouble shoot are to the SAML Basic Information Mapping where entries were either not set up or not an option when this was first set up. These files have been populated but no change.

Email Address

userPrincipalName

 

First Name

givenName

 

Last Name

surname