Configure Local Network Access Policy for Microsoft eCDN
From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.Rollout
Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".
What the notice says
Microsoft’s text, safely structuredUpdated February 19, 2026: We have updated the content. Thank you for your patience.
We're making some changes to the Microsoft eCDN configuration.
Starting with Chrome 146, browsers will enforce Local Network Access restrictions that may impact Microsoft eCDN peer-to-peer functionality.
How this will affect your organization
You are receiving this message because our reporting indicates one or more users in your organization may be using Microsoft eCDN. To maintain optimal performance for Teams Live Events and Town Halls, admins must configure the LocalNetworkAccessAllowedForUrls policy for Chrome-based browsers.
What you need to do to prepare
For complete, up-to-date details (including required URLs, deployment methods, and tenant-specific considerations), see the official Microsoft eCDN documentation: Configure Local Network Access Policy for Microsoft eCDN.
What changed
Between archive captures, newest first- Tags
User impact, Admin impact→ Updated message, User impact, Admin impact
Updated February 19, 2026: We have updated the content. Thank you for your patience. We're making some changes to the Microsoft eCDN configuration. Starting with Chrome
142,146, browsers will enforce Local Network Access restrictions that may impact Microsoft eCDN … reporting indicates one or more users in your organization may be usingthisMicrosoft eCDN. To maintain optimal performance for Teams Live Events and Town Halls, admins must configure the LocalNetworkAccessAllowedForUrls policy for Chrome-basedbrowsersbrowsers. What you need to do to prepare:Admins will need to: Add the following URLs to the LocalNetworkAccessAllowedForUrls policy in your environment: *.ecdn.teams.microsoft.com https://teams.microsoft.com *.ecdn.teams.cloud.microsoft https://teams.cloud.microsoft https://engage.cloud.microsoft/ Apply these settings via Group Policy or registry keys for: Microsoft Edge: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\ Google Chrome: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ForUS Government tenants, use GCC/GCC High-specific hostnames as outlined in the documentation. Additional Notes: This change aligns with Microsoft’s Unified Domains initiative. Ensure your network filters include both legacycomplete, up-to-date details (including required URLs, deployment methods, andnew domains. Pair this configuration with WebRtcLocalIpsAllowedUrls for full peer-to-peer functionality. Firefox restrictions are planned but not yet enforced. See documentation for full guidance:tenant-specific considerations), see the official Microsoft eCDN documentation: Configure Local Network Access Policy for MicrosofteCDNeCDN.- Tags
- Services
Microsoft 365 for the web, Microsoft 365 apps→ Microsoft Teams, Microsoft 365 for the web, Microsoft 365 apps
- Services
- · first version seen
Learn more
Links from the notice and their documentation checks- LocalNetworkAccessAllowedForUrlsNot read yet
- Configure Local Network Access Policy for Microsoft eCDNNot read yet
Related public evidence
No related evidence found in this installation's recent collection. This does not establish that no announcement exists.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
- 2 linked pages have not been read yet.