Microsoft Teams Windows Firewall pop up
Issue : Microsoft Teams client is showing prompt “Windows Firewall has blocked some features of this app” even after adding Windows Firewall Rules. Issue is explained in the article https://docs.microsoft.com/en-us/microsoftteams/get-clients but no resolution.
Eric Shaw commented
Anyone working on this? Guess not.
Mohamed AIT SALAH commented
In real world (Broad deployment) it's critical to remove this popup for end user!!! Thank you very much for your work !!!
Ian Wright commented
Putting apps in the user context is a nightmare as it also allows users to install non-managed applications without admin access.
To even have this as a user voice is just plain ridiculous.
It's ridiculous we should have to even vote for this feature.... should be fixed ASAP
Still waiting for an solution (which is not to turn off all firewall settings)
how has this not been fixed yet?
It is possible to just add %PROGRAMDATA%\%username%\microsoft\teams\current\teams.exe in the GPO and it works fine. /Charleswood
Please fix Windows Firewall. This doesn't just apply to Teams, but for any applications that within the local appdata folder.
John W commented
This is a huge pain with no clear solution.
I've advised my users to cancel the prompt because I'm not just turning off their firewalls and I'm not VNCing to each user's machine every time the prompt comes up.
The location of the executable changes for each user.
The list of ports and protocols for Teams is virtually endless.
If they cancel the firewall prompt things "usually" work okay but there are stutters on screen sharing and other issues.
The only choice I can find is: turn off the software firewall because our software is not thoughtfully designed, or have software that feels extremely unreliable and will make your users think you're incompetent.
David Covert commented
This is still an issue for my company. We roll out laptop's to new remote users and the IT team has to RDP into the system and supply to local admin credentials when they initiate or receive their first call via Teams.
This is obviously a drain on my teams time for a large environment.
Is there no fix/workaround for this yet?
David Covert commented
The last post on this thread was August 09, 2018?
I'm still seeing this problem in my environment over a year later???
Has there been no further progress on this issue by Microsoft?
Martin Skovmand commented
Would be awesome if it would respect the use of %localappdata%, in order to support adding the firewall rule with a GPO.
Rick Smith commented
I don't understand why MS teams cannot just comply with GPO Firewall settings like we can do with Skype. Why do we need to run a PS1 script at logon to keep adding firewall entries for every user that does not have admin rights.
ce problème décourage certains d'utiliser ce produit.
Paulo Venancio commented
Dear Support, I confirm this problem is a little bit annoying, as users are resqueting our Support about this message... In order to go forward we are planning to communicate to user to not consider this message and just click "Cancel",
BUT, can you confirm that doing that there not impact on TEAMS APP Behavior ???
because, clicking "cancel" it will create a "Block" rule in firewall, so my concern is if Teams is going to continue work normally ?
Any update on the solution or do we need to stick to workaround for the schedule task.
I am not in favor of running a schedule task just for this it will impact the login performance of the machine with no reason
MS can you please do something about this
Having various problems for one of our clients with Skype for Business Web App for the same reason!
Roger Lundqvist commented
+1! In my organization they are about to activate Teams for 55 000 users ...
Users are domain users without admin rights, so they will get this prompt.
What was misleading for me was the fact that Microsoft official article is telling that you can press the Cancel and ingnore this warning, but when you go to check the windows firewall you will see 2 Block rules for the teams.exe. This makes you think that the MS Teams will be blocked from that moment on, but it is not.