We’re fixing bugs identified in the comments, and other user reports we’ve received around markdown, but we’ve decided we’re not going to fundamentally change our markdown support.
This is the first time we’ve declined a request, and it didn’t come easily. We weighed this against other important features we’re working on to deliver and we had to make some tough choices.
Really appreciate your understanding on this, and please feel free to ping me if you have any questions, complaints, or need to rant.
SuphatraNestor Diaz commented
I agree that Markdown support should be improved. The current implementation is buggy and pretty much unusable for anything longer than a couple of words. This makes the tool unwieldy for dev teams, to the point where many would rather switch to a different tool (as evidenced by this thread).
Performance has been and continues to be a big focus area for Teams. One main area we have made improvements in is responsiveness for the most frequent user actions of switching between Chat, Channel, and Activity. We are also focused on reducing resource consumption and application load time. More improvements are on the way.
~AlexNestor Diaz commented
This is my one concern as Teams moves closer to convergence with Skype for Business. All versions of Skype are huge and bloated, and Teams already struggles with bloat. The biggest pain since moving from Slack has been performance. It's currently usable, but not really optimal. Please make this a priority.
This feature request is still being worked upon.
I am still trying to get details on what we could expect for Cortana in Teams and will share examples once something is available.
This item is still under review. I’ll keep following up with the feature team and sharing all your feedback.
Clippy is flattered by all the attention but plans to continue his retirement.
We’re updating our command library all the time, so keep checking the menu in the command box to see what’s new by typing / or @.
We know you are patiently waiting for this feature. This feature is being implemented in stages. Fast tenant switching is currently in testing both internally and with early customers. We expect to release to the public in the Fall. I’ll post an update once it’s rolling out.
Full multi-tenant, multi-user support will be added after fast tenant switching.