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.
We have raised the priority of this work item, and it is currently being worked on. We don’t have any dates to share at this point, but will update when we have new status. Thank you!
my biggest bugbear right now ..... please sort it !!!
@Alex - We need an Update!
Alex, we need an update on this! One year is too long!
Brad Goldman commented
FIXED | Rename a channel in a Teams team and gets updated properly in the corresponding SharePoint folder
Note: if a folder is being synced via OneDrive sync, the new channel/folder name will not yet update through to the synced desktop folder with OneDrive shared folders. It is known and being addressed.
We made the roadmap!
Microsoft Teams: Pairing the channel and the corresponding SharePoint folder name.
When renaming a Teams’ channel, the corresponding SharePoint folder will be renamed and reflect the new name. This will help create consistency across Microsoft 365 endpoints, making it easier on users to find their files from anywhere. This new feature will be available for all Standard and Private channels. For Standard channels – The corresponding folder in SharePoint will be renamed. For Private channels – The corresponding site name and the folder in SharePoint will be renamed. For legacy Teams channels that were renamed prior to this rollout, there will be no change in experience. When a legacy channel is renamed after this release, it will simultaneously rename the corresponding SharePoint folder.
Mark Kashman at Microsoft reported on 4/14 that the fix for this was "beginning to release" but "It is not at complete 100% rollout as of now".
Has anyone been able to see the fix in action in their tenant?
Shane O'Donohoe commented
I wanted to add my voice to this as the lack of compatibility between SharePoint folders and libraries and Teams Channels is not only confusing me, it is making me look bad to my internal clients.
Jason Klare commented
This is quite ridiculous... any update would be appreciated.
Same for shared and localy stored in Windows Onedrive file folder. This is also showing still the original channel name from Sharepoint. Shall also get updated.
Joost van der Hoeven commented
As you can see from the votes this is a very annoying design flaw... not having responded to to it over 14 months doesn't give us any confidence. @Alex any update?
Pedro Cardoso commented
Working on it for over a year tells me that it's not being worked on. Is there an update here Alex? This is a significant problem.
Admin IPI Apps commented
Over a year later...
Do you have any updates on this request to share, please?
One of the things I wish I knew prior to migrating from Google Drive. If I had known this, I would have named my Teams structure differently to avoid the too many characters issue. Fortunately most of my users are either not on Windows or do not sync OneDrive files locally, but those that do are very vocal about it.
[Deleted User] commented
This is complete ****. I'm thinking about moving my organisation away from Microsoft. This ticket has been open since 2016 and they give one BS update per year that they are "working on it". One would think that the developer team would be embarassed.
Doug Booth commented
It's been over a year. Please, can't we have a more current status of this critical vulnerability? Time has been lost in confusion and support when people shoot themselves in the foot with the gun Microsoft has left on the table. This is enough time.
Any Updates @Alex?
Hi there - can you please advise when this work will be finished? It is really problematic that the names don't update across Sharepoint and Teams