A User we created is not getting an Okta profile, even after completing a directory sync

Loading

Skip to Navigation Skip to Main Content

Search

Search

Select Language

0D5KZ00000krdU90AIOkta Classic EngineDirectoriesAnswered2025-05-30T17:38:30.000Z2025-05-01T17:37:45.000Z2025-05-30T17:38:29.000Z

FinnP.13041 (Customer) asked a question.

May 1, 2025 at 5:37 PM

A User we created is not getting an Okta profile, even after completing a directory sync

Not sure what other details to add. The user is created, they can login from a domain joined computer, they have licensing assigned in M365, but they cannot access any M365 software, which is a necessity for their job. Trying to get their Okta profile setup but they are not showing up even after completing a manual directory sync.

Any ideas why? Any tips? Help would be appreciated.

Directories

Top Rated Answers

Paul S. (Okta, Inc.)
a year ago
Hello @FinnP.13041 (Customer) Thank you for posting on our Community page!

Usually there are only 2 reasons why a user is not being imported from AD to Okta:
User is missing one or more required attributes. For this you can check the System log after the import and see if there is any failed to create user because of missing attribute. By default Okta profile requires Username, email, First Name and Last Name attributes to create a user, if any of these are missing then the user will not be imported.
User is in a AD OU that is no synced with Okta. In this case Okta does not have the ability to read the OU the user is.

Thank you for reaching out to our Community and have a great day!
--
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.
Expand Post
Selected as Best

All Answers

Paul S. (Okta, Inc.)
a year ago
Hello @FinnP.13041 (Customer) Thank you for posting on our Community page!

Usually there are only 2 reasons why a user is not being imported from AD to Okta:
User is missing one or more required attributes. For this you can check the System log after the import and see if there is any failed to create user because of missing attribute. By default Okta profile requires Username, email, First Name and Last Name attributes to create a user, if any of these are missing then the user will not be imported.
User is in a AD OU that is no synced with Okta. In this case Okta does not have the ability to read the OU the user is.

Thank you for reaching out to our Community and have a great day!
--
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.
Expand Post
Selected as Best

This question is closed.

Recommended content

Forum

HR mastered custom profile OKTA attribute is getting dropped after Deactivation

Forum

I have a user created in Active Directory that hasn't appeared after importing

Forum

get full profile after oidc api login

Forum

Newly created Salesforce Profile not available in Okta dropdown menu on user profile

Loading

A User we created is not getting an Okta profile, even after completing a directory sync