@Will McKay
Thank you for your post! We received a similar issue to yours not too long ago, which I'll share here.
Issue:
From my understanding, you set up Azure MFA with the NPS extension, and users with the Authenticator app can authenticate to your VPN, while users who use SMS don't have any place to input the SMS OTP.
- PAP supports all the authentication methods of Azure AD Multi-Factor Authentication in the cloud: phone call, one-way text message, mobile app notification, OATH hardware tokens, and mobile app verification code.
- CHAPV2 and EAP support phone call and mobile app notification.
Based off these authentication methods, when you deploy the NPS extension, if your RADIUS client supports PAP, but the client UX doesn't have input fields for a verification code, then phone call and mobile app notification are the two supported options.
Also, regardless of the authentication protocol that's used (PAP, CHAP, or EAP), if your MFA method is text-based (SMS, mobile app verification code, or OATH hardware token) and requires the user to enter a code or text in the VPN client UI input field, the authentication might succeed.
If you configured SMS as an authentication method, can you make sure your VPN has the ability to support the SMS code option, if it does and you'd like us to take a closer look into your environment, please let me know.
If you have any other questions, please let me know.
Thank you for your time and patience throughout this issue.
----------
Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.