Rename of Team Channel doesn't rename associated Sharepoint files Folder
When renaming a Team Channel, the associated Sharepoint folder continues with it's previous name. This could lead to confusion.
Thank you for your continued feedback, the team is actively working on this item. We will share an update as soon as one is available.
A year has gone with raised priority. Still no news.
<Sarcasm>Just imagine how hard this problem must be to solve if they have had RAISED PRIORITY FOR A YEAR AND NOTHING HAS HAPPENED!!
I'll add some concerns to this, and so I can get updates. We changed the name of the project and then changed the URL of our internal sharepoint site. The result is the FILES tab no longer connects to the sharepoint site. This is another reason why the FILES tab needs to be editable, in order to redirect where it is synced to. We don't want to create a whole new team, as all team communications and calendars would be lost.
Really? One year ago you raised priority for this? And NOTHING happens within such a confusing and DANGEROUS situation for the company data? 🤬
Schober Juergen commented
Please fix it. Thanks
Active User commented
YAY! Soon it's been one more year since the last update! Well done Alex!
Stephen P. White commented
If you will not up the private channel limit, this needs to happen - yesterday. :)
Please update. This is such a huge pain to work around, and makes our SharePoint environment far less intuitive. There's only so much change management I can do!
Lex Mangin commented
Hello, is there potential ETA you can share regarding a fix for this channel rename issue? Thank you
Seriously... 4 yrs and 3 mo and still no progress on this issue. Please get this on the RoadMap and fix it!
Tim ONeill commented
Another year rolls by ... sigh.
Great, this will reduce workload to the infrastructure team. Looking forward to it. It can't come soon enough.
This disconnect just doesn't make sense, in another thread microsoft says it designed this way ARghhhh
Lacey Thibodeaux commented
I've wasted SO MUCH TIME trying to fix major issues this has caused my setup only to find out this was reported 4 years ago. Absolutely ridiculous
How can you be working on something for OVER FOUR YEARS?
You never provide updates.
Please provide an update on the solution's potential delivery date
please fix it
Please could this be prioritized further -- this is causing huge headaches not only within Teams but also in the syncing of content with OneDrive.
I also need this solved.
Bart Poelmans commented
Yannick Eberle commented
Is there any update to that topic?
Maybe an update, why this is so hard to implement?