MC1189910 High

(Updated) Configure Local Network Access Policy for Microsoft eCDN

  • Admin
  • Network

Summary AI-generated

Chrome 146 will restrict Local Network Access, potentially affecting Microsoft eCDN peer-to-peer for Teams Live Events; admins must configure the allowlist policy to maintain performance.

Suggested actions AI-generated

  • Review and configure LocalNetworkAccessAllowedForUrls Chrome policy
  • Consult Microsoft eCDN documentation for deployment steps

Written by Azure OpenAI (gpt-4.1) from the text of the post below. It can be incomplete or wrong; the original post is authoritative.

Original post from Microsoft

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 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.

Additional details from Microsoft

Summary
Starting with Chrome 146, Local Network Access restrictions may affect Microsoft eCDN peer-to-peer functionality. To ensure optimal Teams Live Events performance, admins must configure the LocalNetworkAccessAllowedForUrls policy for Chrome-based browsers as detailed in the updated Microsoft eCDN documentation.