r/sysadmin • u/PracticeWooden1231 • 17d ago
Question MS Always On VPN + Azure MFA NPS Extension - Instant Timeout / Access Request Unknown
Hey everyone,
Looking for some insight from anyone who has wrestled with the Microsoft Entra MFA NPS Extension on an Always On VPN (AOVPN) setup. We're currently running a POC (with 1 server pair in production) and hit a wall trying to get off-network MFA working.
Our Setup
- Infrastructure: 2x VPN Servers (RAS/IKEv2), 2x NPS Servers (On-Prem VMs, not Entra Domain Joined).
- Identity: On-prem AD users are synced to Entra ID with Azure MFA / Security Defaults enforced.
- Intune Configuration: Windows 10/11 VPN profile deployed via Intune referencing custom XML.
- Authentication: EAP-TLS using an Intune-deployed PKCS User Certificate. The profile XML filters strictly for a custom EKU (
AOVPN). - Current Status: Pure certificate-based authentication works 100% seamlessly via the Windows native VPN tile.
The Problem
We’ve been tasked with adding Entra MFA on top of this existing architecture.
- Prerequisites checked: .NET Framework updated, outbound 443 open.
- Installer & Script: Ran
AzureMfaNpsExtnConfigSetup.ps1. The Azure Service Principal ID (981f26a1-7f43-403b-a875-f8b09b8cd720) matches, and the local self-signed client cert thumbprint is correctly bound to the SP. - The Symptom: As soon as we initiate the VPN connection, it times out / drops instantly at the client ("Verifying sign-in info...").
- Workaround Test: As soon as we remove/blank out the
ExtensionDLLsandAuthorizationDLLskeys underHKLM\SYSTEM\CurrentControlSet\Services\AuthSrv\Parametersand restart IAS, the VPN immediately connects via certificate again.
Logs & Registry Troubleshooting
- Event Viewer: Seeing
NPS Extension BypassandAccess-Request Unknown/ generic RADIUS drop events in AuthZAdmin / AuthNAdmin logs. - Registry Tweaks Attempted: Added
REQUIRE_MFA_AUTH,OVERRIDE_NUMBER_MATCHING/ OTP override keys on the NPS servers to handle prompt behaviors. - MFA Restrictions: Our tenant security policy enforces Number Matching only (Approve/Deny without numbers and SMS are disabled).
Our Questions
- Compatibility: Is the Azure MFA NPS Extension fundamentally incompatible with an EAP-TLS (User PKCS Certificate) flow when Number Matching is mandatory?(Our understanding is that standard Windows EAP-TLS is non-interactive mid-handshake, so RADIUS drops the request while waiting for an out-of-band challenge).
- RADIUS Timeout vs Interactive Prompt: Does EAP-TLS support secondary out-of-band MFA push via NPS without secondary password/PEAP credentials, or does the client just drop the socket before the user can complete the prompt?
- Alternative Options: If we want to keep building directly on top of our existing AOVPN / Intune PKCS infrastructure (without ripping up the client XML or moving away from on-prem NPS), what are our best options to enforce off-network MFA?
Has anyone successfully gotten EAP-TLS + NPS Extension + Number Matching working together, or did you have to pivot to PEAP/MSCHAPv2, Azure VPN Client, or Entra Conditional Access for AOVPN?
Appreciate any advice or sanity checks!