How can we make Microsoft Teams better?

← Public

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.

302 votes
Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

37 comments

Attach a File
Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Mika commented  ·   ·  Flag as inappropriate

    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.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Received this message from a new laptop deployed one week ago. The first Teams call yielded the attached screen. ESC cleared the message and allowed call to proceed. Subsequent Teams call with .PPT presentation completed successfully. Still looks to be an issue.

  • IT commented  ·   ·  Flag as inappropriate

    This warrants and urgent fix. We are forced to switch from S4B to Teams by MS

  • Anonymous commented  ·   ·  Flag as inappropriate

    We are seeing the same issue as OP. Currently just instructing users to hit cancel on the prompt. Would be nice not to have this stumbling block built into the product!

  • Rob Nicholson commented  ·   ·  Flag as inappropriate

    Slightly different wish but in the same ballpark. It's good that the Teams client doesn't need admin rights to install but if the user doesn't have admin rights, would it be possible to not do whatever triggers the firewall prompt (https://i.imgur.com/Bt0qpip.png) because the user then gets https://i.imgur.com/UpaFp9y.png is they click "Allow access"

  • Rob Nicholson commented  ·   ·  Flag as inappropriate

    >The underlying problem is that Teams is getting installed in the users profile. Why are you doing this Microsoft: simple so that users can install the full client without requiring admin rights. Many companies block admin rights locally for security reasons, e.g. nearly every pharma client we work with. At least with installing in the user's profile, they can have the rich client. Although I would imagine many a sysadmin doesn't like this - Chrome does the same.

  • YK commented  ·   ·  Flag as inappropriate

    I'm using a PS script found online. This script works but when I create a scheduled task to have it run upon user login the firewall rules gets added under the administrator profile and not the user who is logging in. I am assuming because the task is running with elevated permissions? Any suggestions?

    Below is the argument in Task Scheduler:
    -Executionpolicy bypass -file "C:\Teams PS1 Task\Untitled1.ps1" -parameter 'value'

    Below is the PS script to add the FW rules:
    $TeamsDir = $env:LOCALAPPDATA + '\Microsoft\Teams\current\teams.exe'
    $firewallRuleName = 'teams.exe'

    $ruleExist = Get-NetFirewallRule -DisplayName $firewallRuleName -ErrorAction SilentlyContinue

    if($ruleExist)
    {
    Set-NetFirewallRule -DisplayName $firewallRuleName -Profile Any -Action Allow
    }
    else
    {
    New-NetfirewallRule -DisplayName $firewallRuleName -Direction Inbound -Protocol TCP -Profile Any -Program $TeamsDir -Action Allow
    New-NetfirewallRule -DisplayName $firewallRuleName -Direction Inbound -Protocol UDP -Profile Any -Program $TeamsDir -Action Allow
    }

  • NF commented  ·   ·  Flag as inappropriate

    I'm using the script provided in the link above, but like everyone else, not thrilled with having to use a workaround.

    I think we would all appreciate if Microsoft did one of two things.

    1. Release a proper version of Teams we can deploy across the enterprise. FYI, the base installation of teams is 300MB. For everyone that has shared computers, that's subpar, and not something you'd equate with Enterprise grade software.

    2. Release a statement indicating they're not changing the installation method, include an explanation on the new delivery method, and a better solution for the firewall nonsense.

    Two simple options, they just need to pick one. This UserVoice post is nearing the one year mark. If Microsoft wants UserVoice to be the channel we use for these issues, maybe someone from the Teams team could participate in the thread?

  • Anonymous commented  ·   ·  Flag as inappropriate

    What the fix for this issue ? Run sccm ps1 script ?
    Be nice to have a real fix from Microsoft.

  • Stefan Schipper commented  ·   ·  Flag as inappropriate

    +1
    The underlying problem is that Teams is getting installed in the users profile. Why are you doing this Microsoft? How should we explain this design issue to our customers? You should know much better...

  • Anonymous commented  ·   ·  Flag as inappropriate

    Same problem here. Tryed adding teams.exe to GPO or runing a powershell or vbs to add it in the computer firewall, nothing is working.

    This need to be fixed.

  • John McAdam commented  ·   ·  Flag as inappropriate

    UPDATE | After now raising the issue with both Intune & Teams support, they have essentially said they know it’s a problem, and will put in on the list of improvements. It’s a really poor response if you ask me :( They have though said they would escalate the issue within, to try to fact track fixing the problem.

  • Jan commented  ·   ·  Flag as inappropriate

    Even though, the following may not comply with someone's security understanding, and the port range may not be 100% accurate, I would like to share this information. Please handle with care:

    You can create two 'Inbound' Port rules:
    1. TCP, Allow Ports 50000-50059
    2. UDP, Allow Ports 3479-3481, 50000-50059

    As a result, the windows firewall will not prompt the user for rule creation anymore.

  • Kazzan commented  ·   ·  Flag as inappropriate

    This should be configurable by MDM or GPO to create these rules in firewall in native Microsoft operating system. Really lowering security says user "do not follow security prompt".

  • Johnnymac1974 commented  ·   ·  Flag as inappropriate

    I am currently working on a 2000+ Win 10 Azure/Intune deployment, and really need a tried & tested non GPO based solution! :( I will get this raised with Microsoft shortly , and will post my findings.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Getting error like
    desktop-bbd2dcf3-b91b-41bf-bf9b-c32d43d4b105
    Error code - Request timeout
    Failed to connect to settings endpoint

    Not able to login Microsoft Teams Desktop App but allowint to login Microsoft Teams web application

← Previous 1

Forum Home

Reference Information for Teams

Public: Desktop

Categories

Feedback and Knowledge Base

(thinking…)

More Teams Information



You are about to visit the UserVoice site for Microsoft Teams

We have partnered with UserVoice, a 3rd party service providing public discussion forums for product-specific feedback.

By clicking "Continue to UserVoice" you agree to UserVoice's Privacy Policy and Terms of Use.