VPN SAML Browser Authentication fails after latest Edge / Chrome updates

[Ruan_Kotze]

I have not seen any posts on this, so just a heads up.

If users update to the latest Edge / Chrome / Chromium build they will receive a pop-up asking them to Allow access from your VPN url to the local network. Failing to do so will cause SAML authentication to fail.

Microsoft References:

Microsoft Edge release notes for Stable Channel | Microsoft Learn
Control a website’s access to the local network in Microsoft Edge - Microsoft Support
Microsoft Edge Browser Policy Documentation LocalNetworkAccessAllowedForUrls | Microsoft Learn

Edit:
As per links above you can add the sites to the allow list via either GPO or Intune Settings Catalog for Edge.

-Ruan

[bsc]

You can deploy that via GPO

https://learn.microsoft.com/en-us/deployedge/microsoft-edge-browser-policies/localnetworkaccessallow...

We're still working on the fix, I can update details, later.

Workaround: Egde settings => website permissions => all permissions => local network access => add website

something like that, in german, its Datenschutz, Suche und Dienste/Websiteberechtigungen/Alle Berechtigungen/Lokaler Netzwerkzugriff )

#########edit - This is, what we did:

1. Quickfix on all computers that are not reachable by GPO: Go to Edge: 

edge://settings/privacy/sitePermissions/allPermissions/localNetworkAccess

and add your SAML-URL to allowed websites

(there may be way to do that smarter by reg or powershell, we just sent out a onepager with a screenshot)

2. (update MS-Edge ADMX templates from https://www.microsoft.com/de-de/edge/business/download and)

configure your MS-Edge-GPO with your SAML URL:

Administrative Templates/Microsoft Edge/Network settings/LocalNetworkAccessAllowedForUrls

to catch all computers, that are not working remotely.

[Ruan_Kotze]

Correct - the GPO and Intune settings to resolve are in the links I posted.  We are pushing the setting using the Intune Settings Catalog for Edge.