Networking requirements
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. Microsoft Edge and Google Chrome allow the port range to be configured using Chrome for administrators.
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 |
Note
July 20, 2023, we completed transitioning domains from *.ecdn.microsoft.com to *.ecdn.teams.microsoft.com. We ask customers to ensure the addition of the new domain to any firewall, proxy, VPN or mDNS configurations they may have made.
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 |