Azure VPN first login shows blank white screen during MFA setup

Question

Azure VPN first login shows blank white screen during MFA setup

Zuuber 35

Has anyone encountered an issue where newly created Azure VPN Client users, on first login, see a blank white screen when the MFA setup screen should appear?

We haven’t seen this before, and no changes have been made to Conditional Access policies or elsewhere. The issue started a few days ago. Our CA policy is basic and just forces MFA via the 'Grant' section set to 'Require multifactor authentication', and sign in frequency set to 11 hrs. No changes have been made to this.

This occurs within the Azure VPN Client during the sign-in/MFA setup flow for new users only.

As a workaround, users can complete MFA setup via a web browser (e.g. logging into Office.com). Once MFA is configured, they can then successfully connect using the Azure VPN Client.

Has anyone seen this recently or identified a root cause?

Vallepu Venkateswarlu 9,325 Reputation points Microsoft External Staff Moderator

2026-04-24T21:59:47.0066667+00:00
Hi @ Zuuber

Welcome to Microsoft Q&A Platform.

This blank/white screen during the in-client MFA registration usually means the embedded browser control (WebView2) in the Azure VPN Client isn’t rendering Microsoft Entra’s MFA setup page. Here’s what you can try:

Make sure the Microsoft Edge WebView2 runtime is installed and up-to-date on the user’s machine.

Update the Azure VPN Client to the latest version (4.x and above).

Force the client to launch your system browser for sign-in instead of WebView2 by editing your VPN profile XML. Under <clientauth><aad>…</aad></clientauth> add:

<useexternalbrowser>true</useexternalbrowser>

Then re-import the profile and retry.

As a quick workaround you’re already using—have users complete MFA registration in a browser (e.g. office.com) first, then sign in via the VPN client.

Please "upvote" if the information helped you. This will help us and others in the community as well.
Zuuber 35 Reputation points

2026-04-24T22:21:07.4833333+00:00
thank you for responding.

The issue occurs on any and all machines.

WebView 2 is version 147.0.3912.72
Azure VPN Client is 4.0.5.0
I added the below to the VPN config file but still the same issue occurs.

<clientauth> <aad> <audience>41b23e61-6c1e-4545-b367-cd054e0ed4b4</audience> <cachesigninuser>true</cachesigninuser> <enablegrouptoken>false</enablegrouptoken> <issuer>https://sts.windows.net/REMOVED/</issuer> <tenant>https://login.microsoftonline.com/REMOVED</tenant> <useexternalbrowser>true</useexternalbrowser> </aad> <cert i:nil="true" /> <type>aad</type> <usernamepass i:nil="true" /> </clientauth>

Yes users are able to firstly register MFA via a web browser then connect the VPN but this is inconvenient for users, and it was previously possible to register MFA during first VPN login. It should work.
Vallepu Venkateswarlu 9,325 Reputation points Microsoft External Staff Moderator

2026-04-24T22:45:58.8266667+00:00

Hi @ Zuuber

Could you please check the issue from another machine or a different browser? If the issue persists, kindly uninstall the application, download the latest version, and reinstall it.
Zuuber 35 Reputation points

2026-04-24T22:49:47.1433333+00:00

As already mentioned the issue occurs on any machine from any network.

Azure VPN client has been uninstalled and reinstalled.

What do you mean try a different browser?
The issue occurs when using the Azure VPN client app.
Vallepu Venkateswarlu 9,325 Reputation points Microsoft External Staff Moderator

2026-04-25T00:58:31.1233333+00:00

What do you mean try a different browser?
Please change the default browser to a different one. For example, if the default browser is Edge, switch it to Chrome and check if the issue persists.

As a quick workaround, you’re already using----have users complete MFA registration in a browser (e.g. office.com) first, then sign in via the VPN client.
Zuuber 35 Reputation points

2026-04-25T06:41:20.9533333+00:00

Yes tried that, the issue occurs whether the default browser is Chrome or Edge.

Yes that is our current work around, but its inconvenient for users, its also worked fine for years, it should work as it has done years.
Zuuber 35 Reputation points

2026-04-25T19:52:08.1366667+00:00

As if by magic the issue is no longer present, this was 100% something within the Azure backend that was at fault that has now been sorted, maybe they restarted one of their servers, the good old reboot!

2 answers

Your answer

Vallepu Venkateswarlu 9,325 Reputation points Microsoft External Staff Moderator

2026-04-24T21:59:47.0066667+00:00

Hi @ Zuuber

Welcome to Microsoft Q&A Platform.

This blank/white screen during the in-client MFA registration usually means the embedded browser control (WebView2) in the Azure VPN Client isn’t rendering Microsoft Entra’s MFA setup page. Here’s what you can try:

Make sure the Microsoft Edge WebView2 runtime is installed and up-to-date on the user’s machine.

Update the Azure VPN Client to the latest version (4.x and above).

Force the client to launch your system browser for sign-in instead of WebView2 by editing your VPN profile XML. Under <clientauth><aad>…</aad></clientauth> add:

<useexternalbrowser>true</useexternalbrowser>

Then re-import the profile and retry.

As a quick workaround you’re already using—have users complete MFA registration in a browser (e.g. office.com) first, then sign in via the VPN client.

Please "upvote" if the information helped you. This will help us and others in the community as well.
Zuuber 35 Reputation points

2026-04-24T22:21:07.4833333+00:00

thank you for responding.

The issue occurs on any and all machines.

WebView 2 is version 147.0.3912.72
Azure VPN Client is 4.0.5.0
I added the below to the VPN config file but still the same issue occurs.

<clientauth> <aad> <audience>41b23e61-6c1e-4545-b367-cd054e0ed4b4</audience> <cachesigninuser>true</cachesigninuser> <enablegrouptoken>false</enablegrouptoken> <issuer>https://sts.windows.net/REMOVED/</issuer> <tenant>https://login.microsoftonline.com/REMOVED</tenant> <useexternalbrowser>true</useexternalbrowser> </aad> <cert i:nil="true" /> <type>aad</type> <usernamepass i:nil="true" /> </clientauth>

Yes users are able to firstly register MFA via a web browser then connect the VPN but this is inconvenient for users, and it was previously possible to register MFA during first VPN login. It should work.
Vallepu Venkateswarlu 9,325 Reputation points Microsoft External Staff Moderator

2026-04-24T22:45:58.8266667+00:00

Hi @ Zuuber

Could you please check the issue from another machine or a different browser? If the issue persists, kindly uninstall the application, download the latest version, and reinstall it.
Zuuber 35 Reputation points

2026-04-24T22:49:47.1433333+00:00

As already mentioned the issue occurs on any machine from any network.

Azure VPN client has been uninstalled and reinstalled.

What do you mean try a different browser?
The issue occurs when using the Azure VPN client app.
Vallepu Venkateswarlu 9,325 Reputation points Microsoft External Staff Moderator

2026-04-25T00:58:31.1233333+00:00

What do you mean try a different browser?
Please change the default browser to a different one. For example, if the default browser is Edge, switch it to Chrome and check if the issue persists.

As a quick workaround, you’re already using----have users complete MFA registration in a browser (e.g. office.com) first, then sign in via the VPN client.
Zuuber 35 Reputation points

2026-04-25T06:41:20.9533333+00:00

Yes tried that, the issue occurs whether the default browser is Chrome or Edge.

Yes that is our current work around, but its inconvenient for users, its also worked fine for years, it should work as it has done years.
Zuuber 35 Reputation points

2026-04-25T19:52:08.1366667+00:00

As if by magic the issue is no longer present, this was 100% something within the Azure backend that was at fault that has now been sorted, maybe they restarted one of their servers, the good old reboot!

Answer 1

Hi Zuuber

Thank you for the update.

Based on your confirmation, the issue with the blank screen during the MFA setup flow in the Azure VPN Client has now resolved without any changes on your end. This strongly suggests the behavior was caused by a transient issue within the Microsoft Entra (Azure AD) or Azure VPN authentication backend, which has since been remediated.

As noted:

The issue only affected new users during initial MFA registration
Existing users or users with pre-configured MFA were not impacted
The problem resolved automatically without configuration changes

This aligns with a temporary service-side issue affecting the embedded authentication experience within the Azure VPN Client.

Workaround (validated during the issue): Users were able to complete MFA registration via a browser (e.g., Office.com), after which VPN authentication succeeded as expected.

Pleaseand “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Answer 2

Zuuber hi & thx for join me here at Q&A portal,

first-time MFA setup inside VPN client is broken, register MFA in browser first :)))) this is usually Azure VPN Client embedded sign-in window choking on the first-time MFA registration flow. not really VPN Gateway. existing users work because they already have MFA methods, new users hit the registration UI and the client renders blank. workaround u found is the right one: have users register MFA in browser first via Office.com or aka.ms/mfasetup, then connect VPN.

root cause is likely WebView/WAM/Auth broker issue or a recent Entra sign-in UI change that Azure VPN Client doesnt render correctly. update Azure VPN Client, update Edge WebView2 Runtime, clear WAM/token cache if needed, but for production I would just pre-register MFA before VPN onboarding. if it started suddenly for multiple users, open support with timestamps, client version, Windows build, and sign-in correlation IDs.

rgds,

Alex

&

 if my answer helps pls accept it.

Share via

Azure VPN first login shows blank white screen during MFA setup

2 answers

Your answer