We have a solution for this ask and have moved this on our backlog! Keep watching here for updates as we get closer to completing this work.
An error occurred while saving the commentJosh King commented
I could have sworn that I'd left a comment on this a *long* time ago, ah well better late than never.
This is the ONE thing stopping our IT dept (and by extension our entire org) from adopting Teams as opposed to Slack. I've stood up a ChatOps POC in Slack and my team (no pun intended) is really keen to jump in full force but I'm putting the breaks on as I really want the platform we end up settling on being Teams... I mean it's part of what we're paying for after all.
At the moment we're at a cross roads, but I can't keep pumping the breaks on this for long. Eventually I'm going to have to give in and make a move. My fear is that this will end up being a move to Slack and at that stage we'll become entrenched on that service and it'll be a hard sell to transition over to Teams when it finally "catches up."
Appreciate the updates, and understand the technical hurdles. As an end user on the outside it's just frustrating that Teams didn't launch with feature parity compared to your biggest and most direct (imho) competitor.Josh King supported this idea ·