Forum Discussion
WiFi WPA2 Enterprise seamless sign-on
WPA2 Enterprise setup in intune requires the on-premise domain-joined NDES server and certificate issued by internal CA. WPA2 Enterprise seamless authentication will not work if the device is not joined to the on-premise AD. By seamless, we mean that users are not prompted for authentication. How do we enable seamless WPA2 Enterprise authentication for Azure AD joined Windows 10 computers (computers which are only joined to Azure AD, not hybrid)?
Forgot to update this.
Short answer: If the computer is only joined to Azure AD, WPA2 Enterprise seamless authentication is not possible.
As of now (March 2019) it is not possible to have seamless (users are not prompted for authentication) WPA2 Enterprise authentication when the computers (Windows 10) are not joined to an on-premise AD (only joined to Azure AD). This is because winlogon credentials contains a cloud user which will not be allowed to authenticate automatically on RADIUS (radius is using the on-premise AD).
17 Replies
Forgot to update this.
Short answer: If the computer is only joined to Azure AD, WPA2 Enterprise seamless authentication is not possible.
As of now (March 2019) it is not possible to have seamless (users are not prompted for authentication) WPA2 Enterprise authentication when the computers (Windows 10) are not joined to an on-premise AD (only joined to Azure AD). This is because winlogon credentials contains a cloud user which will not be allowed to authenticate automatically on RADIUS (radius is using the on-premise AD).
rajeshkhanikarBut what about doing device level authentication? I presume the device will be able to enrol via NDES for a certificate and then authenticate via 802.1x at a machine level.
I have made this work. CA + NDES with Intune SCEP enrolment policy to issue user certificates. Intune WiFi profile for EAP-TLS authentication and finally a FreeRadius Linux RADIUS server to do the authenitcation. This is seamless. You cant use NPS as the RADIUS server, as that always attempt to authenticate to AD (requiring domain join or a nasty manual certificate mapping setup). FreeRadius can be configured to just validate the client certificate only.
Thanks for sharing with everyone. Where you able to discuss the scenarie if user is hybrid and device is cloud only? rajeshkhanikar
- I have not tried this personally, but I would think you would have to follow this article to ensure Azure AD joined devices are cared for.
https://docs.microsoft.com/en-us/windows/security/identity-protection/hello-for-business/hello-hybrid-aadj-sso-cert#configure-network-device-enrollment-services-to-work-with-microsoft-intuneThanks for your response. We have seen this article. But it doesn't discuss expected behaviour for Azure AD joined computers (not hybrid). Our goal is to enable seamless WPA2 Enterprise authentication for only Azure AD joined computers (not hybrid).
Ah I see. In that case, NDES should hand out the client certificate to your Azure AD joined computer. And then you will need to make sure the Azure AD joined computer has the root certificate as well. Have you confirmed that NDES is handing out the client certificate and that the root certificate is being deployed to your computers?
