Unfortunately due to re-prioritization this item has slipped back onto the “backlog” for the time being.
I hope to see it move back into “working on it” soon and will continue to engage the feature team with your feedback.
This is extremely disappointing to hear.
Personally for my organization, the two remaining features needed in order to start rolling out Teams to our users en masse are Private Channels and Archiving Channels, until then we're stuck in pilot mode with Slack users gaining more and more ammunition against us. They were able to archive channels before Teams was even released.
I am one of the precious few users in my company actually trying to champion Teams while Slack and G-Suite are hammering at the front door. I can't tell my company to wait another 2-3 years before Teams is actually usable, they’ve already been waiting since November 2016 when we first told them about it, with excitement in our voices. That excitement has devolved into discouragement.
I don’t want to belittle the work that's been done so far, any Teams fan can acknowledge the current state of the Teams app is much better than what we experienced in the Preview. That being said…Teams fans can also acknowledge that too much time will go by from the announcement of this app to the time it's truly mass marketable.
Those of us in IT trying to push Teams are starting to look like hopeless fools every time we say something like "Microsoft is working on it…" "Don’t buy more Slack licenses, Teams is better…I mean it WILL be better…eventually…I hope?...scrap that they just put that feature on the backlog…"
Forgive the rhetoric, I have no doubt, Teams will eventually become a powerhouse productivity app….but all the while, at the pace you’re releasing features, other solutions are swooping in and engaging end users, securing their market share. So let's get it together Microsoft.
Just had a lovely conversation with Microsoft Support about this...basically there is no such thing as interoperability despite their documentation regarding coexistence modes.
The very minute a users even tries Teams just once...they break the ability to use Skype to talk to you if you're using Teams.
Here's the quote from the rep, "Teams is designed to only send messages to Skype for Business if the recipient has NEVER used Teams. Once the recipient like USER B has signed into Teams (even just once), all messages from other Teams user like USER A, would ONLY be sent to Teams."
The support rep even admitted Microsoft's documentation does not match this current broken system. There is no actual migration path from Skype to Teams, there is no actual interoperability. If you have a 1,000 users and just one tried out Teams then you have to decide either everyone uses Skype or everyone uses Teams, nothing in between.
It's crazy but the truth is you can safely disregard everything in this article: https://docs.microsoft.com/en-us/microsoftteams/teams-and-skypeforbusiness-coexistence-and-interoperability
I'm desperately trying to keep Slack at bay in my organization, but this just gives Slack users more ammunition.
Microsoft, please get it together.
+1, It would be nice for the team to be notified that a new channel has been added
Hey Microsoft Teams users — I want you to weigh in on new features around channels and group chats. The engineering team and I have put together this survey to find out how you want to see channels improve. You can fill it out here: https://microsoft.qualtrics.com/jfe/form/SV_esTxHdABLQxKLvn
And I’m still waiting on approval to get you a good update about Private Channels. I can say that we ARE working on it, fervently.
I’m so happy to share an update with you! The feature team has let me know that they are working hard at this and are aiming for a spring time release.
Please comment below if you might be interested in testing or TAP, and include the industry, company size, and location of your org. We would likely want to hit a very wide range of demographics.