Users do not appear in the Imported Users column after created on AD side

Hi @DoziE.16959 (Customer)​ , Thank you for reaching out to the Okta Community! 

The most common causes are missing required attributes, an incorrect OU configuration, or issues visible only in the Okta System Log that require investigation.

Although you have verified that the OU is checked and the user has First Name, Last Name, sAMAccountName, and Email populated, there are several additional factors that can prevent import:

1. Missing or incomplete required attributes: Okta requires specific fields to be populated in Active Directory. Even if the fields you checked are complete, the user may be missing the User Principal Name (userPrincipalName) or another required attribute that Okta's import process expects. If any required field is blank, Okta silently skips that user during import without displaying them in the Imported Users list.
2. OU configuration not saved:The OU must be checked AND saved in the Directory Integration settings. If the checkbox was selected but the settings were not saved, the OU will not actually be scanned during import.
3. Import results not showing skipped users: Okta logs why users are skipped, but this information is not always visible in the default import results view. You may need to check the System Log to see the actual reason.

Solution:

Follow these steps to diagnose and resolve the issue:

1. Verify all required Active Directory attributes: In Active Directory, confirm that each new user has the following fields populated: First Name (givenName), Last Name (sn), sAMAccountName, User Principal Name (userPrincipalName), and Email (mail). If any of these are blank, populate them and save the user object.
2. Confirm the OU configuration is saved: In the Okta Admin Console, navigate to Directory > Directory Integrations > Active Directory > Settings. Scroll to the User OUs section, verify that the OU containing the new users is checked, and click Save to ensure the configuration is persisted.
3. Run a full import: After confirming the OU and attributes, go to Directory > Directory Integrations > Active Directory > Import and click Import to trigger a full import.
4. Check the System Log for import errors: If the users still do not appear, go to Reports > System Log and search for the user's name or username. Look for events related to system.agent.ad.import_user or mapping failures. These logs will show exactly why the user was skipped (for example, "missing email attribute" or "invalid profile mapping").
5. Review the Import Results for skipped users: After running the import, check the Import tab for any indication of skipped users. If the import summary shows "X Users Skipped," there may be a download option or expandable section that reveals which users were skipped and why.
6. Verify the user is enabled in Active Directory: Although you have confirmed this, double-check that the user account is not disabled or locked in Active Directory, as disabled accounts will not import.

In rarer cases, I've also seen this be caused by replication issues/delay. In short: If the user records were created on the Domain Controller but the Okta AD agent was installed on a different server, due to replication delay, the info was not propagated and Okta did not pick the users up for import. 

If you continue experiencing issues with the import, please open a case to do a deep-dive with one of my colleagues from the Okta Support team. 

If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

Hope my answer helps! 

--

Help others in the community by liking or hitting Select as Best if this response helped you.

Collect them all. Learn a new skill and earn a new Okta Learning badge.

Just released: More Okta Community badges just added