
PaulS.94875 (ACE Fitness) asked a question.
I am about to pull the trigger on the OKTA Office365 WS integration, but I have a few questions to make sure I am doing this correctly.
- Adding the WS federation with the NON domain admin.. so not the domain, but the onmicrosoft.com admin user.
- I want to make sure by adding the Okta WS federation that it will not brick the Azure AD connection or logins for non test Okta users. As I understand it, if the user is in the Okta users, it will redirect the user to the Okta login, if they aren't they will still be able to login normally via the Office365 portal. Can the community confirm this is the way the user login will work.

Hi Paul,
In the case of a federated domain, when a user logs into Office 365, their authentication request is forwarded to Okta, which acts as the domain controller.
This allows for a single place to control all authentication requests.
If you disable an account or change a password, these changes take effect immediately and you don’t have to wait until synchronization is complete. Okta allows Single Sign-On and a slightly better user experience since the user has to sign in fewer times.
Once an Office 365 Domain is Federated, any and all authentication to it will be
handed by Okta, which means that any users not assigned the Office 365 application in Okta, will no longer be able to access that domain.
The o365 is based on upn suffix not okta
register a test domain. Test.tv
create a couple users in ad with this suffix n federate that to o365
easy peasy 🙂
also join Facebook okta help tips and tricks for a growing community of help