Users added before SCIM was enabled not updating or deprovisioning via Azure AD

Ben Pemstein Ben Pemstein
· Updated

Users who existed in 15Five before SCIM was enabled are not controlled by Azure AD — they will not receive profile updates and cannot be deprovisioned through the integration until they are reimported.

Diagnose

Check: User was created in 15Five before SCIM was enabled → Confirm creation date vs. SCIM activation date → If true → If not

Check: User exists in 15Five but changes made in Azure AD do not sync to their profile.

  • How to check: Compare the user's 15Five account creation date against the date SCIM was enabled in your SCIM Integration settings.
  • If true: The user was created outside SCIM and is not yet managed by it. Proceed to Fix.
  • If not: The user was created after SCIM was enabled. This article does not cover that scenario — see Related Articles.

Fix

Reimport the affected users via CSV so SCIM can associate them with their Azure AD records. Existing check-ins, objectives, and other user-generated content are not affected.

  1. Prepare a CSV file containing at minimum the email field for each affected user.
  2. Log in to 15Five as an account admin.
  3. Click the Settings gear in the bottom-left corner.
  4. Navigate to People and select Import people.
  5. Upload the CSV file and complete the import.
  6. Confirm each reimported user appears in the Manage people list.
  7. In Azure AD, verify the users are assigned to the 15Five application.
  8. Wait up to 40 minutes for Azure AD to push the first sync.
  9. Confirm that a profile field change in Azure AD reflects in 15Five after the sync completes.

What Resolution Looks Like

After reimport and a completed Azure AD sync, profile updates made in Azure AD appear on the user's 15Five profile. Deactivating the user in Azure AD deactivates their 15Five account.

If It Still Fails

Contact 15Five Support at support@15five.com. Include:

  • The affected user's email address
  • The date SCIM was enabled on your account
  • The date the CSV reimport was completed
  • A description of the specific field or action (update or deprovision) that is not syncing

Not Covered Here

This article does not cover users who were created after SCIM was enabled but are still not syncing, or general Azure AD sync delays.

Related Articles

Configure SCIM provisioning with Azure AD Bulk import people via CSV

Was this article helpful?

Sorry to hear that. Tell us what was missing →