Okta Unassigns Users From Microsoft Office 365 Application After Import
Last Updated:
Overview
Okta unassigns users from the Microsoft Office 365 integration or generates an import roadblock event after an import. This occurs when user accounts are inactive or unlicensed in Microsoft, and the resolution involves verifying active status and licenses or using a comma-separated values (CSV) export. Import Safeguard settings stop an import before Okta makes changes if a specific percentage of application unassignments or user deactivations occurs.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Microsoft Office 365
- Imports
Cause
The issue occurs due to the following reasons:
- The user accounts are no longer active in Microsoft.
- Microsoft removed the user account licenses. Okta does not import Microsoft Office 365 unlicensed users.
Solution
How are Microsoft Office 365 unassignments resolved?
Review the user account status in Microsoft and perform a manual import for unlicensed users to ensure successful Okta assignments.
- Verify that the user accounts are active and possess the necessary licenses in Microsoft Office 365. Okta requires active licenses to import users successfully.
- Export unlicensed users who lack an Okta account from Microsoft as a comma-separated values (CSV) file and import them into Okta.
NOTE: Group membership in Okta experiences changes if Microsoft Office 365 manages the memberships. Adjustments to the CSV import may be necessary.
