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.
At the time of this posting, this request has been declined, but I'd still like to voice my support for this idea. While I get that Teams is trying to emulate Slack's style of markdown, it's frustrating not being able to use the same markdown that I use in Github, Discord, Reddit, VS Code, and for my personal websites. I hope that you change your mind on this in the future, perhaps making it a configurable option to not break existing workflows for those migrating from Slack.Anonymous supported this idea ·