Anonymous

My feedback

  1. 20 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 » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  2. 4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Public » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  3. 45 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    14 comments  ·  Public » Account Access (Sign-In)  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  4. 29,980 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2552 comments  ·  Public » Account Access (Sign-In)  ·  Flag idea as inappropriate…  ·  Admin →

    The engineering team is continuing to work on adding support for multiple accounts on desktop clients. We will first launch support for 1 work/school account and 1 personal account so users can enjoy Teams for work and personal side-by-side. Windows and MacOS. Support for multiple work accounts is still being worked on and will come at a later date.

    You can track status via the roadmap here: https://www.microsoft.com/microsoft-365/roadmap?searchterms=68845.

    Thanks!

    An error occurred while saving the comment
    Anonymous commented  · 

    Nope. For the sake of security, mobile device management, this should be enabled via the ability to have multiple clients open. Multiple identities in the same app instance just invites problems.

  5. 3,016 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    420 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    Also respectfully disagree.

    Chat and Teams are two different things. One is completely private, and the other is either completely public, or at least public to the team.
    If it is even remotely possible that anyone will ever say something in a team that was meant for a chat there is no way I'd want to take the chance.
    If you don't believe me, try "mentioning" something in a loud voice that to blow off steam in your next exec-level meeting. See how well that works, since "teams" and "chats" are the same thing.
    Not to mention what might be a plethora of compliance issues, becuase group chats are the ONLY thing that is really private in teams, and there also may be a discovery protection against "private" converstations in chats (okay, maybe...)

    Having not used Hipchat and not used Slack is a good thing here, becuase I can see how different and in my opinion, badly, things could be designed.

  6. 2,114 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    86 comments  ·  Public » PowerBar  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    I think you'll find bots to be more powerful, after an initial adjustment period.

Feedback and Knowledge Base