af5cs (af5cs) asked a question.
I need some guidance on how to achieve the below from Okta's side?? as in step by step manual since some settings seem to be outdated.
Document: https://www.okta.com/resources/whitepaper/using-okta-for-hybrid-microsoft-aad-join/
Okta Sign-in Policy
Okta sign-in policies play a critical role here and they apply at two levels: the organization and application level. Office 365 application level policies are unique. This is because authentication from Microsoft comes in various formats (i.e., basic or modern authentication) and from different endpoints such as WS-Trust and ActiveSync. Here are some of the endpoints unique to Okta’s Microsoft integration.
Type
Endpoint
(https://company.okta.com/app/office365/)
Use
Authentication Type
PassiveLogOnUri
../sso/wsfed/passive
Login
Modern
ActiveLogOnUri
.../sso/wsfed/active
Login
Basic
LogOffUri
.../sso/wsfed/signout
Sign-out Use Cases
Basic
Username
.../sso/wsfed/username13
Windows 10 Machine Logins
Basic
Windows Transport
.../sso/wsfed/windowstransport
Kerberos-based Logins
Basic
Hi @af5cs (af5cs) , thank you for contacting Okta Community.
The article you mentioned explains how the technology works rather than how to implement it. You can review the following articles:
Typical workflow for integrating Hybrid Azure AD Join - this is a table of contents with several articles
Configure Office 365 sign-on rules to allow on-prem and cloud access
Regards.
--
Help others in the community by liking or hitting Select as Best if this response helped you.