
SamadA.04842 (Customer) asked a question.
We recently got intune and premium ad setup. We followed the windows 10 document Okta has here https://www.okta.com/sites/default/files/Okta_Windows_10_azure_AD_join.pdf
When we try to join Windows 10 1809 manually while in windows, after entering the email in the field to join the machine to azure ad, it shows taking you to sign-in page for your organization and tries to load Okta login page and quickly window disappears and we receive an error "something went wrong"
We use SAML for office 365 logins. Are we missing some other setting in Azure for this to work?

Are these windows 10 pro machines?
Has the machine been joined before, maybe its still registered in Azure
A long shot could be to try and change the standard browser, perhaps the current one is throwing a fit and therefor quickly closing the browser
Has the user been activated in Okta and signed in on a regular browser, not for the session, but for a live account.
Ive had similar issues with login screen disappearing from Outlook, updates were needed to get it working.
But we also have joined devices in Azure and that went without a hitch.
Im guessing you followed this: https://docs.microsoft.com/en-us/azure/active-directory/devices/azuread-joined-devices-frx too?
Not sure if it helped, but just my 2 cents.
Hi Samad,
You can also check if IWA may be causing this; try disabling it for testing purposes or try the join process off-network.
Hi Alin,
I tried off networking and sure enough it worked. We were able to join the machine to azure ad. So why is the machine having trouble going through local IWA? How can we fix this?
I found that the machines need self assigned cert in order for this to work. I assigned the cert manually and ran the OOBE and found that it worked on local network. We're in the process of purchasing trusted certs instead which will resolve this problem.