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.
Nooooooooooo.. It has moved again to November 2021..
A Right Royal PITA
I see the release date for this has now moved to July 2021 from June 2021.
Hi team, how could we manage team members at the channel levels ?
2 days to go.. Will it happen??
Following earlier comment from Martin:
Perhaps a checkbox when renaming something in teams that says "Rename connected Site in Sharepoint". Or "Rename Sharepoint Folder Path". That after Ticked or is ticked by default will allow you to specify the new linked folder pathway in the team sharepoint site. That would allow for some customisation to the change in the event it shouldn't have the same name for whatever reason.
Yes would like this but not always, sometimes we want the SharePoint folder name to by different so that it's shorter, as it makes the synced path in OneDrive shorter, which helps with the 256 character limitation, but at the same time we can use a slight different longer name in Teams, which makes it more obvious what the channel is for.
Just as an FYI, it would be great if there was an option to NOT change the SP site when this is 'fixed'...... We have projects where the SP site and group email is set up with just the project number, but then update the name of the team site to include the project name for ease of navigation..... so the current 'problem' actually works rather well for us as is.....
MS “Actively Working on it”! Hooray! Wonder how long before it goes on the backburner…..
Doug Booth commented
To Anonymous with broken links to your linked SPO library: This is a pitiful situation. Microsoft left the cover off the manhole for any member of a Team to walk right in. Here's a description of the risk and the only mitigation available until it's fixed: https://blogs.perficient.com/2020/02/02/the-pains-of-renaming-channels-in-teams-2/
HI everybody, I did change the team name, but I lost the link to the documents in Teams. Also, this creates 1 copy of the channel in Sharepoint one with the old and the other the new name.
How could I change the name in teams and keep the documents link?
How could I get the link back?
Jan Henk commented
Come on Alex, you can give us a better update than just 'actively working on this'..... for 4 years !
Active User commented
Maybe it’s just me, but this update just frustrated me more. Is there any reason for us to believe that Microsoft is working on this any more than they did 4 years ago?
Really excited this is now being worked on. I'm also hoping it'll have flow-on effects and help resolve similar issues such as currently not being able to move a channel to a different team. Fingers crossed!
John Baldwin commented
Interesting that this update should come today.
JUST THIS MORNING I had to deal with this issue (again).
If management changes a team name, or a product name, we change the matching team or channel in Teams. If we created NEW ones, _all_our_history_would_be_lost_ (or at least split up all over the place) -- either way, unfindable.
But renaming things and then just accepting your design bug is nearly as bad.
Imagine telling your developers,
"oh yeah, the things you find in Teams at
Windows Experience > Windows XP > Files > Release Notes > foo.docx can be reached at
You'd have a bunch of angry developers at Microsoft and a bunch of confused people looking at the wrong things.
Microsoft is supposed to be our Productivity Partner, and not a hindrance to our own development. PLEASE FIX THIS SOON!
Hmmm... you've been "actively working on this" since 2017. Literally 4 years now... Isn't this just a simple "run a script to rename a few associated backend items"? Why is this 4 years of work?
Achmad Dimyati commented
Thank you for the update, hope we will get the solution asap.
Hooray - this is a huge issues when you have 50% Teams users and 50% SharePoint users accessing the same content (synced to local machine) especially with e Teams->Files->General being in a sub folder and the top level SharePoint Documents library not being visible in Teams
All a nightmare!
It does not rename the Sharepoint site toooooo...
AAaaaaannnndddd still we wait .... Yyyaaawwwnnnn. c'mon Mickey$oft this should never have been an issue. Change a folder name it updates everywhere.. Surely !!!