<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
0D54z000075XSEBCA4Okta Classic EngineDirectoriesAnswered2021-08-08T20:55:45.000Z2021-08-05T15:22:57.000Z2021-08-08T20:55:45.000Z

RobertJ.12440 (Community Colleges of Spokane) asked a question.

Affect of O365 Federation on existing Azure SSO Enterprise Applications

We are preparing to enable O365 SSO through Okta. We operate in a hybrid environment and use AD Connect to sync our users with Azure. At the moment we do not plan on using Okta to do any O365 provisioning. We just want to use it for SSO & MFA. I understand that once we enable federation with Okta, when a user signs into O365, they will no longer be redirected to our on prem authentication server, but will be redirected to Okta for authentication.

The issue is that we have a large number of Azure Enterprise Applications that are used to provide SSO functionality for other vendors such as Adobe, LinkedIn, KnowBe4, Zoom...etc.

With our current configuration, when a user signs into one of these, Adobe.com for example, they hit Azure AD and ultimately get redirected to our on prem authentication server. If we enable O365 Federation with Okta, will they hit Azure AD and then be redirected to Okta for authentication instead of our on prem server?

 

Thank you,

Jason Jakober

Technology Services

Community Colleges of Spokane


  • Hi Jason,

     

    This is Alex from Okta Support.

     

    Once you federate an Office domain with Okta, all login requests made from users that are part of that domain will be redirected to Okta as well. You cannot select who goes through the federated login and who will go to your On-Prem authenticator.

     

    Best regards,

    Expand Post
This question is closed.
Loading
Affect of O365 Federation on existing Azure SSO Enterprise Applications