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.
SuphatraDan LaBar commented
This perfectly encapsulates my hatred for Microsoft. Their products don't ever "just work". They don't really care about making it work because they already sold it to your employer who is forcing you to use it. To top if off, the broken feature is supposed to be an "automation" that makes your life easier by "improving" on a great OSS solution but actually just makes you want to scream into the void of the corporate abyss.
Reminds me of Grapes of Wrath...
> We're sorry. It's not us. It's the monster. The bank isn't like a man.
> Yes, but the bank is only made of men.
> No, you're wrong there- quite wrong there. The bank is something else than men. It happens that every man in a bank hates what the bank does, and yet the bank does it. The bank is something more than men, I tell you. It's the monster. Men made it, but they can't control it.
This item is still on the backlog.
This feature item is still in the works. We will keep you posted as we have new info from the feature team.
We know many of you are waiting for a Teams client for Linux, and we’re pleased to confirm we’re actively working on it. Stay tuned for more information.
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.