Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Microsoft eCDN setup has some networking requirements mainly in the following areas.
When a user browses to the event page, the client needs to download the Microsoft eCDN script - that requires an https connection to
*.ecdn.teams.microsoft.com.Once downloaded, it creates a secure WebSocket connection to our backend.
The peer-to-peer connection itself is a UDP connection over the port range 1025-65535, chosen randomly by the browser. Chromium browsers such as Microsoft Edge and Google Chrome allow the port range to be configured using the WebRtcUdpPortRange policy.
External connections
Connections that go out to the internet. Usually packets in these connections go through the firewall and need allow-listing.
| Hostname | Ports | Protocol | Description |
|---|---|---|---|
| *.ecdn.teams.microsoft.com | 443 | HTTPS over TCP | Microsoft eCDN scripts |
| *.ecdn.teams.microsoft.com | 443 | WebSocket over TCP | Microsoft eCDN backend |
| *.ecdn.teams.cloud.microsoft | 443 | same as above two | upcoming unified ___domain |
Important
By the end of June 2025, in accordance with the Unified Domains initiative, we will have transitioned domains from *.teams.microsoft.com to *.teams.cloud.microsoft. We urge customers to add the new ___domain(s) to their firewall, proxy, VPN, and/or mDNS configurations as soon as possible. The transition is not a clean cut-over but gradual, so both versions are required during the transition period, beginning June 1st.
Internal connections
Connections that remain inside the corporate network. Usually packets in these connections don't go through a firewall and wouldn't need any configuration to allow them.
| Hostname | Ports | Protocol | Description |
|---|---|---|---|
| n/a | 1025-65535 | SCTP over DTLS over UDP | P2P communication |