Anonymous

My feedback

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

    We’ll send you updates on this idea

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

    We’ll send you updates on this idea

    688 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →

    if you have an existing post that you want to show in a different channel, you can edit the message and cross-post. This will add the top-level post to the different channel, but will not include the full set of replies. We will keep this request in mind as we evolve the cross-posting feature in the future and update if the status changes.

    Details on cross posting can be found here: https://support.office.com/article/cross-post-a-channel-conversation-in-teams-9c1252a3-67ef-498e-a7c1-dd7147b3d295.

    Anonymous supported this idea  · 
  3. 17,040 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1359 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →

    As stated in the last update, the ability to use multiple Teams accounts at the same time is being implemented in stages for Desktop. Faster tenant switching functionality on the Windows client has been rolled out to the public ring fully, and Mac will begin rolling out soon. Work is in progress on cross-tenant notification improvements, and support for multiple accounts on desktop will follow. We’ll keep you posted!

    Note: The ability to use multiple Teams accounts at the same time is supported on iOS & Android today.

    Thanks,
    Alex & the Teams team

    Edited

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

    We’ll send you updates on this idea

    2 comments  ·  Public » Meetings  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  5. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Anonymous shared this idea  · 
  6. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bug Reports » Client - iOS  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  7. 14,976 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1775 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  8. 9,347 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    865 comments  ·  Public » Performance  ·  Flag idea as inappropriate…  ·  Admin →

    Great performance and user experience remain a topmost priority for us. Application launch time has seen improvements in the recent build. We will continue making improvements across the product including channel to chat switching and overall resource consumption.

    An error occurred while saving the comment
    Anonymous commented  · 

    We need an urgent update on this. We are looking to roll out Teams in our company, but this is impossible with the current desktop client. The performance hit is STAGGERING. Memory usage aside, the whole PC is reduced to a crawl when the Teams client is running in the background. It's like going back to a single-core processor! Window re-draws, task switching, opening apps all go from more or less instant to taking several seconds on our (relatively modern) hardware. It's not clear what the Teams client is doing to cause this (CPU usage remains low, for example), but it's definitely doing something evil. Normal performance resumes as soon as we quit the desktop client.

    Anonymous supported this idea  · 

Feedback and Knowledge Base