NPS server changing login ID to ******@domain.com format and rejecting authentication of Azure AD authenticated user

Question

Hello,

I have a set up where our users connect to the Wi-FI using Azure AD authentication via on premise NPS Radius servers. However, they get rejected. When I look at the event log, it shows DOMAIN******@DOMAIN.COM as the user ID it cannot find. So somewhere within the server it is adding the @DOMAIN.COM.

Where would I find what is doing this? It started happening randomly and now it is spreading to most of my users (dozens of them).

Thank you

Answer 1

Hi. Thank you for your question and reaching out. I’d be more than happy to help you with your query

It sounds like you are having an issue with the NPS Server rejecting authentication of an Azure AD authenticated user when their login ID is changed to the ******@domain.com format. This issue is usually caused by a mismatch between the authentication method used by the NPS server and the authentication method used by Azure AD. To resolve this issue, you will need to configure the NPS server to use the same authentication method as Azure AD. Depending on your specific configuration, this may require making changes to the NPS server or to the Azure AD configuration.

If the reply was helpful, please don’t forget to upvote or accept as answer, thank you.