Ports needed for Microsoft Teams

[Ben Oostdam ☁]

Hello,

I've been looking for the list of ports (TCP/UDP) that MS Teams needs.
Working in a highly secured DEV environment :)
I cannot find the ports required for installation & communications.
Anyone a link or a list for me ?  Guess lots of more administrators will need this.

Thanks in advance for your replies.

[#2]

Hello Ben

It's mainly 80 & 443 the most required ports for Microsoft teams communication, you can use the following command while you loginig to Microsoft teams to detect which protocol stacked.

from CMD type the following

netstat -n

Or you can use fiddler to check the same behaviour.

Skype for Business Online and Microsoft Teams

ID	Category	ER	Addresses	Ports
11	Optimize Required	Yes	13.107.64.0/18, 52.112.0.0/14	UDP:3478, 3479, 3480, 3481
12	Allow Required	Yes	*.lync.com, *.teams.microsoft.com, teams.microsoft.com 13.70.151.216/32, 13.71.127.197/32, 13.72.245.115/32, 13.73.1.120/32, 13.75.126.169/32, 13.89.240.113/32, 13.107.3.0/24, 13.107.64.0/18, 51.140.155.234/32, 51.140.203.190/32, 51.141.51.76/32, 52.112.0.0/14, 52.163.126.215/32, 52.170.21.67/32, 52.172.185.18/32, 52.178.94.2/32, 52.178.161.139/32, 52.228.25.96/32, 52.238.119.141/32, 52.242.23.189/32, 52.244.160.207/32, 104.215.11.144/32, 104.215.62.195/32, 138.91.237.237/32, 2603:1027::/48, 2603:1037::/48, 2603:1047::/48, 2603:1057::/48, 2620:1ec:6::/48, 2620:1ec:40::/42	TCP:443, 80
13	Allow Required	Yes	*.broadcast.skype.com, broadcast.skype.com 13.70.151.216/32, 13.71.127.197/32, 13.72.245.115/32, 13.73.1.120/32, 13.75.126.169/32, 13.89.240.113/32, 13.107.3.0/24, 13.107.64.0/18, 51.140.155.234/32, 51.140.203.190/32, 51.141.51.76/32, 52.112.0.0/14, 52.163.126.215/32, 52.170.21.67/32, 52.172.185.18/32, 52.178.94.2/32, 52.178.161.139/32, 52.228.25.96/32, 52.238.119.141/32, 52.242.23.189/32, 52.244.160.207/32, 104.215.11.144/32, 104.215.62.195/32, 138.91.237.237/32, 2603:1027::/48, 2603:1037::/48, 2603:1047::/48, 2603:1057::/48, 2620:1ec:6::/48, 2620:1ec:40::/42	TCP:443
14	Default Required	No	quicktips.skypeforbusiness.com	TCP:443
15	Default Required	No	*.sfbassets.com, *.urlp.sfbassets.com, skypemaprdsitus.trafficmanager.net	TCP:443, 80
16	Default Required	No	*.keydelivery.mediaservices.windows.net, *.msecnd.net, *.streaming.mediaservices.windows.net, ajax.aspnetcdn.com, mlccdn.blob.core.windows.net	TCP:443
17	Default Required	No	aka.ms, amp.azure.net	TCP:443
18	Default Optional Notes:Federation with Skype and public IM connectivity: Contact picture retrieval	No	*.users.storage.live.com	TCP:443
19	Default Optional Notes:Applies only to those who deploy the Conference Room Systems	No	*.adl.windows.com	TCP:443, 80
22	Allow Optional Notes:Teams: Messaging interop with Skype for Business	Yes	*.skypeforbusiness.com 13.70.151.216/32, 13.71.127.197/32, 13.72.245.115/32, 13.73.1.120/32, 13.75.126.169/32, 13.89.240.113/32, 13.107.3.0/24, 13.107.64.0/18, 51.140.155.234/32, 51.140.203.190/32, 51.141.51.76/32, 52.112.0.0/14, 52.163.126.215/32, 52.170.21.67/32, 52.172.185.18/32, 52.178.94.2/32, 52.178.161.139/32, 52.228.25.96/32, 52.238.119.141/32, 52.242.23.189/32, 52.244.160.207/32, 104.215.11.144/32, 104.215.62.195/32, 138.91.237.237/32, 2603:1027::/48, 2603:1037::/48, 2603:1047::/48, 2603:1057::/48, 2620:1ec:6::/48, 2620:1ec:40::/42	TCP:443
25	Default Required	No	scsinstrument-ss-us.trafficmanager.net, scsquery-ss-asia.trafficmanager.net, scsquery-ss-eu.trafficmanager.net, scsquery-ss-us.trafficmanager.net	TCP:443
26	Default Required	No	*.msedge.net, compass-ssl.microsoft.com	TCP:443
27	Default Required	No	*.mstea.ms, *.secure.skypeassets.com, mlccdnprod.azureedge.net, videoplayercdn.osi.office.net	TCP:443
29	Default Optional Notes:Yammer third-party integration	No	*.tenor.com	TCP:443, 80
127	Default Required	No	*.skype.com	TCP:443, 80

[#3]

Are there a list of TCP/UDP ports for audio and video?  I was thinking from a QoS perspective.

[#4]

Here is some of the guidance for networking and Teams:

Prepare your organization's network for Microsoft Teams

Office 365 URLs and IP address ranges

Optimize your current Skype for Business environment for Microsoft Teams

[#5]

I ended up doing a test.  It uses the same ports as Skype 4 Business.  The .exe is Teams.exe.  voice port 50000:50019 (mark DSCP 46), video ports 50020:50039 (mark DSCP 34), and sharing ports 50040:50059 (mark DSCP 24). I did TCP and UDP, but audio and video should only be UDP.

Thanks,

Alex

[#6]

If you want Communications then 3478 to 3481 will also be needed ... https://julianfrank.wordpress.com/2017/10/03/understanding-media-flows-in-microsoft-teams-my-notes/

[#7]

Teams may not need the 50K range... it 3478 through 3481 only

[#8]

Yes Off course, Here you go
https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-ab...

[#9]

I wonder if it uses those ports for the phone application.  When I was doing a Skype call a couple of days ago it was using a low port like that but I didn't save the capture.  I will do another test and get back with you.

Thanks,

Alex

[#10]

I know this is an old thread but in testing _ teams meeting. I was seeing all media coming from a single source port 50016 for audio, video and VBSS. See picture

So a bit worried now.

Is there any documentation on this?

Also will the client mark for QOS? I think QOS still has a place to play for P to P calls and bring your won SIP trunk situations 

When I say that with SFB I see there is a divergence in clients. Windows continues to not mark and works as it always has done while Mac, IOS and Android now mark EF and AF41.

[#11]

Is there any calls happening between teams and Skype4B? Check using netstat -b ...

[#12]

Nope. To be sure I killed off SFB and netstat -b not showing anything the looks out of the ordinary.

So in testing today (with SFB killed etc) SRC port for audio is UDP 50022

Video is also UDP 50022

VBSS is interestingly UDP 500046 

Again this is a meeting client <=> 13.93.124.30 (meeting)

What are other seeing?

[#13]

That worked for me! Had to add those ports under TCP rule and everything loaded fine.

[#14]

Quality of Service (QoS) in Microsoft Teams

https://docs.microsoft.com/en-us/microsoftteams/qos-in-teams

[#15]

Yes, thanks,..
Glad it's there finally.

[#16]

Hi everybody,

What about peer to peer calls between corporate branch sites to keep the media in the corporate network and direct between the endpoints?

It only need UDP 3478 - 3481 between the branch sites? or other ports are needed?

BR,

Gabriel

[#17]

---

@gacasta wrote:

Hi everybody,

What about peer to peer calls between corporate branch sites to keep the media in the corporate network and direct between the endpoints?

It only need UDP 3478 - 3481 between the branch sites? or other ports are needed?

BR,

Gabriel

---

@gacasta 

The UDP ports 3478 through 3481 should be fine for teams to Teams Communication by default... For Meetings check here Meetings High Ports - Network Planning for Microsoft Teams for clearer response 

[#18]

@Julian Frank When I look at devices running teams there is a listening port that seems to be outside the normal 50000-50059.   Here is an example.   

These ports only have a few flows but it seems like these ports are randomly selected.   

what do port outside 50000-50059 do and are they needed?

[#19]

@Jdschmitz 

Thanks for all the info everyone provided here it was helpful for me. I thought I would also mentions that I see the following ports listed in the Teams Admin Centre, in case it helps: