MORE STATUS
I like the status options in S4B, and so does my boss. It will be important to my boss before accepting the use of MS Teams widely to have a broader range of statuses. Missing statuses are:
* In a meeting
* In a conference call
* In a call
* Presenting
* Be right back
* Off Work

Particularly of importance are "Be right back" and "off work". "Do not disturb" is probably sufficient for "in a meeting", "in a call" and "presenting". But, it sure is nice that S4B auto-detects those three statuses (for the most part).

CUSTOM STATUS
Would like to create a custom status option, such as an out-of-office message.

Honestly, this is a tall order due to the fact that Teams was not launched this way in the first place, but my real world experience, and feedback from the field, is that having Skype-for-Business-like functions in Teams (chat/Presence/etc) be separate from Skype for Business itself is not only confusing for many users, but inhibits adoption. Users want to consolidate the number of apps they use, not increase it. I personally find this to be true.

Teams is an incredible tool with so much potential, but living and breathing in Skype for Business, like so many of us do, Teams isn't a completely organic feel due to the disparity of chat identities. If I could go into Teams, manage my projects/files/OneNote, engage in Chats, see and join my meetings, engage in Audio/Video calls (I can do all this now), AND THEN also place and receive all my PSTN calls, Teams would be my new permanent application for doing all this, and email would start to fade into the background.

This is the direction I truly hope to see things go. Teams' potential is incredible, but realizing its full potential, in my humble opinion, relies on complete Skype for Business integration.

Looking for the ability to create a channel that only channel members can see. Private channels are available in slack. There is an admin for private channels who is the creator, and they are the ones who add/remove users.

Five types of public/privacy that is being asked for by users:

- Public-Open (visible anywhere including outside the org and anyone can join)
- Public-Invitation (visible anywhere including outside the org, must be invited)
- Company-Open (only visible inside the org and anyone in the org can join; outside the org must be invited)
- Company-Invitation (only visible inside the org, must be invited)
- Secret (invisible to everyone except existing members, must be invited)

There is no reason that Teams and Chat should be different top level categories in the left navigation. They are the same thing, perform exactly the same function, and making two different items simply confuses the navigation and makes badge notifications and discoverability much more difficult to use.

Please combine Chats into the Teams tab so that you can browse all conversations in one place rather than needing to navigate to different tabs to see different conversations.

Chats and channels perform essentially the same function, which is talk to some people and collaborate. Forcing the user to check two different lists to see if somebody is messaging them is a really bad experience, it is like having two different chat apps.

This is one usability issues that makes Teams less usable for collaboration than both Slack and Skype.

Korean IME (HANGUL) does NOT work properly

1. When typing Hangul after the character ‘(‘, and a space, the Korean IME combination is broken continuously, and and we can not send messages correctly due to the broken IME compositions. (e.g. when typing (안녕하세요, (안ㅇ하세요ㄴ comes out.

- Looks like it's only happening in MS Teams app since it's working well in Word and Outlook with the sample repro steps.

2. Even if we try to point out a particular person through @, the name comes out twisted with Hangul. (e.g. when typing @홍길동, @홍동길 comes out (the second character and the third character are changed. And sometimes @홍ㅣㄹ comes out (the second component and third component are broken)

With the incorrect IME behaviors, Most Korean cannot use the MS Teams correctly with Hangul due to the issues, and it’s very critical.

Please handle this issue as soon as possible with a high priority.