How to Prepare for Chromium’s Local Network Access Changes in Version 141
In late September 2025, Google Chrome and Microsoft Edge (both based on Chromium) will roll out a privacy feature that blocks local network access by default. This change aims to stop websites from scanning your home or office network without permission. But if you use OneDrive for Web, SharePoint Document Libraries, or Microsoft Lists, you might see prompts asking to allow local network access. Denying these prompts can break offline access and slow down performance. Here’s how to stay ahead of this change.
Why This Matters
Chromium’s new privacy feature stops websites from talking directly to devices on your local network, such as file servers or local caches. Without explicit permission, offline sync and other local features in Microsoft 365 apps may not work. Users will see pop-up dialogs asking for access. If they click “Block,” offline files won’t sync and page load times could increase.
Identify Your Trusted URLs
Before you set any policies, gather the URLs your users need. Common ones include:
Add more if you use other Microsoft 365 services that rely on local network calls.
Configure the Policy in Intune
The easiest way for managed devices is using Intune’s Settings Catalog:
- In the Intune portal, go to Devices > Configuration profiles.
- Click Create profile and choose Settings Catalog.
- Search for LocalNetworkAccessAllowedForUrls.
- Select it, then add your trusted URLs one per line.
- Assign the profile to device groups that need access.
After deployment, devices will allow those URLs to use local network calls automatically. Users won’t see prompts, and offline features stay on.
Alternative Methods
If you don’t use Intune, you can apply the policy with Group Policy or directly in the registry.
Group Policy (ADMX)
- Open the Group Policy Management Console.
- Create or edit a policy under Computer Configuration > Administrative Templates > Microsoft Edge > Network Settings.
- Enable LocalNetworkAccessAllowedForUrls and enter your URL list.
- Link the policy to your Active Directory OU.
Chrome uses a similar path under Google > Google Chrome if you import its ADMX file.
Registry Settings
For unmanaged or script-based deployments, set registry keys on each PC.
- Edge:
Key:HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge
Value Name:LocalNetworkAccessAllowedForUrls(REG_MULTI_SZ)
Data: List your URLs. - Chrome:
Key:HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome
Value Name:LocalNetworkAccessAllowedForUrls(REG_MULTI_SZ)
Data: List your URLs.
Each URL goes on its own line in the multi-string value.
What to Watch For
- User Experience: Without this policy, users must click “Allow” on each prompt. Blocking the prompt stops offline sync.
- Policy Propagation: It can take hours for policies to reach every device. Plan ahead and monitor compliance.
- Existing Settings: If your admins already set “Open with Explorer” or other network policies, keep both. They serve different needs.
Verify and Monitor
After rollout:
- Test on a sample device. Open OneDrive for Web, go offline, and make sure files still sync.
- Use Intune or Group Policy reporting to confirm devices have applied the setting.
- Ask a few users to check their apps and report any new prompts.
Conclusion
Chromium’s local network change improves privacy but can disrupt your Microsoft 365 workflows. By proactively configuring LocalNetworkAccessAllowedForUrls in Intune, Group Policy, or the registry, you keep offline access and performance intact. Your users won’t see annoying prompts, and their work stays smooth.
