Anonymous

My feedback

  1. 1,415 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    166 comments  ·  Public » Calling  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  2. 994 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    123 comments  ·  Public » People  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  3. 34,975 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3567 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your continued feedback. As many people have pointed out, this is available on mobile today. Support for replying to a specific message is on the backlog for desktop. I’ll let you know when we have progress to share. Thanks.

    Anonymous supported this idea  · 
  4. 322 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    52 comments  ·  Public » Calling  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  5. 893 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  92 comments  ·  Public » Desktop  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    Guys,
    MS actually does provide a script, but takes no responsibility for it; please find it below:

    $users = Get-ChildItem (Join-Path -Path $env:SystemDrive -ChildPath 'Users') -Exclude 'Public', 'ADMINI~*'
    if ($null -ne $users) {
    foreach ($user in $users) {
    $progPath = Join-Path -Path $user.FullName -ChildPath "AppData\Local\Microsoft\Teams\Current\Teams.exe"
    if (Test-Path $progPath) {
    if (-not (Get-NetFirewallApplicationFilter -Program $progPath -ErrorAction SilentlyContinue)) {
    $ruleName = "Teams.exe for user $($user.Name)"
    "UDP", "TCP" | ForEach-Object { New-NetFirewallRule -DisplayName $ruleName -Direction Inbound -Profile Domain -Program $progPath -Action Allow -Protocol $_ }
    Clear-Variable ruleName
    }
    }
    Clear-Variable progPath
    }
    }

    this will create an inboud rule on every user account on the machine (and it can be executed as a scheduled task or via gpo from an account with elevated privileges).

    more info and better format in the hyperlink (bottom of the page)
    https://docs.microsoft.com/en-us/microsoftteams/get-clients#sample-powershell-script

    Anonymous supported this idea  · 
  6. 930 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    96 comments  ·  Public » Calling  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your feedback, the team has this request under review. We will share an update as soon as one is available.

    In the meantime, you may want to try using the “Do No Disturb” status if you are in a call or meeting, and do not want to get call notifications (rings and toasts). For more information on the various status settings in Teams and how they effect your notifications, including call notifications, please visit https://support.microsoft.com/en-us/office/change-your-status-in-teams-ce36ed14-6bc9-4775-a33e-6629ba4ff78e.

    Anonymous supported this idea  · 
  7. 812 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    247 comments  ·  Public » Devices (Headphones, Cameras)  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 

Feedback and Knowledge Base