<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00007eSD1qCAGOkta Classic EngineSingle Sign-OnAnswered2025-07-29T09:00:29.000Z2022-05-17T16:57:35.000Z2022-05-18T17:18:45.000Z

jolio (jolio) asked a question.

Office 365 Integration & WS-Federation

Hello. When configuring the Office 365 integration, during the SSO setup, WS-Federation is configured using the automated or manual PowerShell options. Now, the primary login domain name should be used for this. After this domain is federated, what does that mean to current users? I am currently in the initial phases of setting up Okta and our O365 integration. My users are currently synced to Azure AD via Azure AD Connect. After federating our domain, will the users immediately have to login via Okta? Meaning there is no next step to onboard the users.


  • flaviu.vrinceanu1.5628408972654734E12 (Customer Success Service Delivery)

    Hi @jolio (jolio)​,

     

    Thank you for posting on the Okta community page!

     

    Once the domain is federated, the users will be re-directed to Okta for authentication after they insert their credentials on the Office 365 side (Okta does not control the applications sessions) therefore I would recommend to make sure that all the users that need access to O365 are already in Okta and that they are assigned successfully to the app before federating the domain.

     

    You can also configure provisioning and bring the users into Okta by performing an import from Office 365. I have provided bellow a documentation about Office 365 provisioning:

     

    I hope the above information is useful!

    Expand Post
This question is closed.
Loading
Office 365 Integration & WS-Federation