Office 365 Provisioning Fails in Okta Due to Invalid Domain Name in "userPrincipalName" Property
Last Updated:
Single Sign-On
Okta Classic Engine
Okta Identity Engine
Overview
A Microsoft Office 365 provisioning flow fails in Okta because the username that Okta sends does not match the Office 365 username format. Resolve this issue by ensuring the application username format domain matches the federated domain in Office 365. The Okta dashboard displays the following error:
The domain portion of the userPrincipalName property is invalid. You must use one of the verified domain names in your organization.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Microsoft Office 365
- Provisioning
- Single Sign-On (SSO)
Cause
Office 365 returns an error when the username Okta sends does not match the Office 365 username format.
Solution
How is the invalid domain portion error resolved?
Resolve the invalid domain portion error by verifying and matching the application username format domain with the federated domain in Office 365.
- Verify the application username format domain in Okta.
- Ensure the application username format domain matches the Microsoft Office 365 federation domain.
