Forum Discussion

RIGAN25's avatar
RIGAN25
Copper Contributor
Mar 31, 2020

Hybrid Azure AD Join + Okta Federation

Implemented Hybrid Azure AD Joined with Okta Federation and MFA initiated from Okta. Trying to implement Device Based Conditional Access Policy to access Office 365, however, getting Correlation ID ...
Azure Active Directory (AAD)
Kav77's avatar
Kav77
Copper Contributor
Aug 25, 2020
Hi RIGAN25, can you elaborate on this? I have the exact same problem, federated with Okta and wanting to use conditional access policies using hybrid joined devices.

They are failing the CA policy because AzureAdPrt = NO.
RIGAN25's avatar
RIGAN25
Copper Contributor
Aug 25, 2020

Kav77 Providing you details about this:
Please follow controlled HYAADJ rollout using Group Policy Object.
The only change you need to perform related to GPO object is the Tenant.

Use Tenant domain : domain.onmicrosoft.com and not the custom domain name verified to the tenant.

Also, the reason where you see AzureAD PRT = NO, is related to device where Windows device login work on Legacy Auth, so please create a Rule in Okta to allow legacy auth to the PRT token.

Be sure that device is able to communicate to DC and Internet while performing the device registration process.

  • ItchyChimp's avatar
    ItchyChimp
    Copper Contributor
    Oct 15, 2020

    Kav77 Custom User Agent is Early Access, which Okta admins should be able to enable themselves from the Admin UI "Settings>Features". If not available, Okta support can turn it on for you.

     

    https://help.okta.com/en/prod/Content/Topics/Apps/Office365/custom-client-filter.htm

     

  • Kav77's avatar
    Kav77
    Copper Contributor
    Sep 07, 2020

    RIGAN25I wasnt sure what you meant by this initially: "Also, the reason where you see AzureAD PRT = NO, is related to device where Windows device login work on Legacy Auth, so please create a Rule in Okta to allow legacy auth to the PRT token."

     

    Did some digging and found these two resources:

    https://www.okta.com/resources/whitepaper/securing-office-365-with-okta/

    https://www.youtube.com/watch?v=gvQ8BuxRlkg&ab_channel=Okta

     

    Though I didnt have the option to add a custom agent string, I did add another sign on policy in Okta to allow legacy auth and now my PRT token is generated and device conditional access policies work 🙂

     

    Hopefully this helps someone else that may come across this.

  • Kav77's avatar
    Kav77
    Copper Contributor
    Aug 25, 2020
    hmm I only have the GPO 'Windows Components> Device registration> register domain joined computers as devices' enabled and that seems to have Hybrid joined the devices successfully. It has no option for specifying the tenant domain?

    Anyway I just noticed the AzureAdPrt is user based. I was running CMD under admin and it was saying NO, but when run under user context it actually says 'YES'. Think I will log this with support.