Hi Everyone – thank you for your patience. As was commented by someone below, Suphatra is no longer at Microsoft, but rest assured we are working on this feature.
Please could you point us to the entry in the Office 365 roadmap for this, so we can monitor progress? ...
Couldn't find anything about it in there, in spite of it being "worked on fervently".
And the dedicated page on this is in chocolate teapot usefulness territory ...
As mentioned in the prior status, the channel limit was raised from 100 to 200.
In the near future a retention limit will be set so you can still go back and reinstate a channel you had deleted. Once the retention period has expired then the channel will get a hard delete which will free up the space and no longer count toward the 200 channel limit.
This will help with some of the issues you have voiced in the comments below.
But I understand many of you wish the limit to be further increased. I will continue to provide your votes and comments to the feature team.
Teams only gets 4 points of value out of 100 compared to the other Office 365 apps in a Gartner customer survey ...
With issues like the one that is the subject of this thread, it's not difficult to see why.
Even SharePoint scored more than you lot at 12 points.
One may ask: Are you the old SharePoint Team in disguise?
Did the "modern UI" usher in a new team of people who know what they're doing with SP, and the old SP team got dumped onto writing Teams?
2000 valves in Colossus, eh? ...
Pair them off into flip-flops for a total of 1000 memory locations.
So that's 800 more in 1940 than Microsoft Teams can manage in 2017.
And that's "great news"?
Ref the linkage of this problem with SharePoint, mentioned by one of the Redmond reps at some point: Is it possible that the Teams app is storing the comments in a SP list with a column for the channel, and then using the client object model to filter the comments?
I wonder because that's the only 100 limit constraint that bubbles to the top when searching for it ...
Any comment on that, MS? Not likely, obviously.
Anything that touches that designed to fail Agile / Scrum mess called SharePoint gets dragged down with it. Why couldn't the Teams team have avoided the black hole of DespairPoint and used the newer data storage technologies in the Azure estate to implement the channels?
This is gonna run for years. It's one of *those*.
100 raised to 200.
Is that some kind of joke?
There doesn't appear to be any mention of "trying to work around" or "find a solution" for this 100 channel limt per team problem in the Office 365 roadmap ...
I've tried searching for "Teams" and "Channels" and scanning the up-coming fixes and works. Couldn't find anything.
Unless I've missed something, please could you remove or edit your comment, Suphatra, as it is misleading. There clearly is no active effort to fix this problem in the pipeline, and your message should read accordingly.
Speaking of the 5000 item / document limit in a SP library, what's going to happen when the channel limit is lifted from 99? Let's say we have 500 products / customers / suppliers / employees / projects or whatever, and there is a one channel for each in the Team.
So we get 500 folders all created in the documents library of the SharePoint site associated with the Team. So that's a maximum of 10 documents per channel i.e. maximum 10 documents per product / customer / supplier / employee / project whatever it is you have one channel for.
It's always SharePoint that messes it up for everything around it. 5000 items in a library, 100 channels below a team. wtf this is the 21st century. I bet Alan Turing's machine had more than 5000 memory locations in the 1940's. When are you gonna re-write that dogpile called SharePoint?
This feature request is working its way through the backlog queue. No new details are available yet.
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 item is still in the works. I’m waiting for additional details from the feature team and hope to be able to share something more detailed soon.
Presumably you'll do it through the Graph API, like all the other Office 365 apps, e.g. SharePoint, Groups, Planner - see bottom of left nav in the doc?
And can we have full CRUD on all properties, not some half-baked, never finished, cludge as is the norm for Microsoft?
Hi everyone — we have implemented this on the web version.
We will not be implementing it in the desktop app or mobile app due to other high priority engineering items.
Let me know if you have any questions!
Come on MS, pull your finger out, a ludicrous omission.