Can Intune EAP-TLS use a machine certificate before sign-in and a user certificate afterward?

November 17, 2026 5 answers
Asked by n.472+hexcrank

On Windows 11, machine-only Wi-Fi authentication works before and after sign-in. With Intune's machine-or-user setting, Wi-Fi fails at the sign-in screen but connects using the user certificate after sign-in.

Both machine and user certificates are deployed through SCEP. What should I check, and can one profile handle both stages?

Answers

v.638~muxnotch

Start with what is actually available before sign-in. Assign the Wi-Fi profile and machine SCEP certificate to devices, then run netsh wlan show profiles on a test laptop. Check that the Wi-Fi profile is listed as an All User Profile.

Also check the local computer certificate store with certlm.msc. The machine certificate needs to be there with its private key and a suitable certificate chain. A working user certificate after sign-in doesn't establish that the machine certificate or profile is available at the sign-in screen.

Reply to this answer
_x83+cachepulley.2

Check the RADIUS side too. A machine certificate being present doesn't necessarily mean the server can map and authorize it. Look at the failed authentication request and server logs, especially if you're using NPS with cloud-managed devices.

The server's certificate trust, identity mapping, and authorization policy all matter. Those checks may differ from the ones used for the user certificate, so compare the machine failure with the successful user authentication.

8y!gasketwinder_274:

Knowing which RADIUS server is in use would help narrow this down. A profile issue and a server-side machine identity rejection can look similar from the sign-in screen.

Reply to this answer
m.548+fusegauge

If device access is all you need, machine-only is the simpler option, and it's already working here. That won't give you user certificate authentication or user-based RADIUS policy after sign-in, though, so it depends on what the network needs to authorize.

Reply to this answer
p.714!nodecradle

You could test separate machine and user Wi-Fi profiles rather than relying on one profile to change authentication context. Treat that as an experiment, not a guaranteed fix. Check which profile Windows selects after sign-in and whether the connection switches as intended.

Another route is a custom WLAN XML profile exported with netsh and deployed through Intune. That gives you more control over settings than the built-in configuration, but it takes testing, including checking the connection itself and subsequent Intune reporting.

Reply to this answer
5x!drumfunnel_831

The RADIUS product and join state can change the available options. For hybrid-joined devices, Group Policy may offer another way to configure the Wi-Fi profile. Alternative RADIUS servers are also worth evaluating if NPS cannot handle the certificate mapping your deployment requires.

Neither change proves the current profile is wrong, so I'd inspect the client and RADIUS logs before replacing infrastructure.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions