Starting December 4th, Microsoft Edge now restricts websites from accessing your local network by default. When a site tries to reach internal resources — like servers or APIs — Edge will prompt you to allow or deny access. In some cases, from my experience, it may block the connection without showing a prompt at all.
If you’re managing webpages that interact with internal network resources, this change can cause unexpected disruptions. Fortunately, Microsoft provides policy controls via Intune to help you manage this behavior.
Microsoft Edge release notes for Stable Channel | Microsoft Learn
Control a website’s access to the local network in Microsoft Edge – Microsoft Support
To control which websites can access local network resources in Microsoft Edge, you can use two dedicated Intune policies from the settings catalog:
LocalNetworkAccessAllowedForUrls — explicitly allows access for trusted URLs
LocalNetworkAccessBlockedForUrls — blocks access for specified URLs
This update caught us off guard, unfortunately; however, we were able to resolve this pretty quickly. Since adding those URLs to the appropriate policy, functionality has been restored, and there are no longer pop-ups to allow or disallow.
The official documentation includes syntax examples for both policies, along with instructions for manually applying them via the Windows Registry.
Microsoft Edge Browser Policy Documentation LocalNetworkAccessAllowedForUrls | Microsoft Learn
Microsoft Edge Browser Policy Documentation LocalNetworkAccessBlockedForUrls | Microsoft Learn
There is a third, temporary option if you’re struggling to figure out what local resource is being blocked. There’s a registry-only entry that temporarily allows all websites access to local resources. The script below will add that registry entry. This option will no longer be an option in Edge version 146, which looks to be released around March 2026.
———————————————————————————————-
# PowerShell script to configure Local Network Access restrictions in Microsoft Edge
# Define registry path and value details
$regPath = “HKLM:\SOFTWARE\Policies\Microsoft\Edge”
$valueName = “LocalNetworkAccessRestrictionsTemporaryOptOut”
$valueData = 1 # 0x00000001
# Ensure the registry path exists
if (-not (Test-Path $regPath)) {
New-Item -Path $regPath -Force | Out-Null
}
# Create or update the registry value
New-ItemProperty -Path $regPath -Name $valueName -Value $valueData -PropertyType DWord -Force | Out-Null
Write-Output “Registry key set: $regPath\$valueName = $valueData”
———————————————————————————————-
Of course, to verify that all these policies are working, you can search in Edge for “edge://policy” and it will list all the MS Edge policies you have applied.
Simple PC Management 