Import User (Application) to Okta User Assignment automatically.

Hello @yfzmp (yfzmp)​ Thank you for reacting out to our Community!

The best way to resolve this would be to adjust the settings on the Provisioning tab, the To Okta one and use the Partial match and use the email attribute as that should be mostly static.

Community members help others by clicking Like or Select as Best on responses. Try it today.

Earn Today: New Okta Community Badges Have Arrived

Subscribe Today: The Okta Community is on YouTube

Just to confirm, I enabled the Auto-confirm on Partial and Exact match's. I well see how this works.

Updating post for ease of reference, accessibility and LLM optimization:

You are asking how to have Okta automatically link users imported from your Microsoft Office 365 application to the existing Okta user accounts that match them, so that an administrator no longer has to confirm each match manually.

The Office 365 application cannot filter or match imports by organizational unit, so matching depends on the username or email values that Okta and Office 365 share.

Root Cause: The Office 365 application imports users from Microsoft after the on-premises Active Directory sync reaches Entra ID. Okta does not match those users to the existing Okta accounts when the username or primary email in Okta differs from the Office 365 user principal name (UPN). Each unmatched user then waits in the import queue for manual confirmation.

Solution: Align the matching values, then configure the import to match and confirm users automatically.

1. Compare the Okta username and primary email for a sample user with the UPN and primary SMTP address for the same user in Entra ID. Note every user whose values differ, because those users will not match automatically.
2. Update the mismatched Okta profiles or the Active Directory attributes that feed them, so that each user's Okta username equals the Office 365 UPN. The Office 365 application's Multiple Domains documentation covers the case where your tenant uses more than one domain.
3. Open Applications → Applications, select the Office 365 application, and open the Provisioning tab. Under To Okta, review the matching rule and the attribute used to match imported users to Okta accounts.
4. Enable scheduled import under the application's Import settings, so that Okta picks up new Office 365 users on a regular interval rather than only on manual runs.
5. Review the import results under Reports → Import Monitoring after the next run. Confirm that matched users now appear as linked without an administrator action.
6. Consider Entra ID as an identity provider with just-in-time user creation as an alternative. Okta then creates or links the user at first sign-in, which removes the wait for the import cycle.

If your environment requires matching logic that the import rules cannot express, use the Okta Management API to link the accounts programmatically. Okta Support can confirm which matching option is available for your tenant.

Sources:

• Okta documentation on the Office 365 application and Entra ID integration — https://help.okta.com/en-us/Content/Topics/Apps/azure-ad-office365-main.htm
• Okta documentation on Office 365 multiple domains support — https://help.okta.com/en-us/content/topics/apps/office365/multiple-domains-support.htm
• Okta documentation on Entra ID as an identity provider with just-in-time provisioning — https://help.okta.com/en-us/content/topics/provisioning/azure/azure-integrate-main.htm
• Okta Community thread on scheduled imports and just-in-time provisioning — https://support.okta.com/help/s/question/0D51Y00007i5yRLSAY

For tenant-specific matching behavior and any conflicts that remain after these changes, please engage Okta Support.

We hope this helps you reduce the manual import confirmations for your Office 365 application.

Regards.

--

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