Anonymous

My feedback

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

    We’ll send you updates on this idea

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

    We’ll send you updates on this idea

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

    We’ll send you updates on this idea

    1791 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. 173 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We’ll send you updates on this idea

    under review  ·  75 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. 434 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We’ll send you updates on this idea

    233 comments  ·  Public » Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for providing this feedback. We are sorry you are experiencing this issue, and are working on a fix.

    This issue is specific to screen (desktop) sharing scenario and for 3440×1440 resolution specifically. In the meantime, please try using either ‘application sharing’, or change your resolution to a higher or lower resolution for screen sharing.

    I will update when the fix is available. Thanks.

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

    We’ll send you updates on this idea

    under review  ·  87 comments  ·  Public » Mobile  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  9. 484 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 →
    Anonymous supported this idea  · 
  10. 1,398 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    182 comments  ·  Public » Notifications  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
    An error occurred while saving the comment
    Anonymous commented  · 

    Microsoft, this needs sorting ASAP. It's essential to manage privacy, it really needs doing. Thanks

Feedback and Knowledge Base