Make rename in Teams reflect name changes in Sharepoint?
When I rename a folder in the Teams app, the underlying folder is not renamed in sharepoint. This is most confusing.
Quick update on this suggestion. We are still working on this with MS Teams. We don’t have an ETA to share still.
Do you have an update on this issue? On the teams forum they just updated that it is being worked on. Is this being worked on from both the teams development side and the SharePoint development side and could you provide at time estimate for when you expect it fixed? In advance thank you.
The suggestion from the teams side have over 15.000 votes, this is of course because from a UX prespective we see the error occur when we rename in Teams. So please take all these votes into account and all the users who have not tried to rename a channel in Teams and therefore not expirenced the error yet.
Please fix this urgently - this is a huge problem. Every new team I stand up has this issue, as the original project name we come up inevitably changes. I've just hit this issue again a year after I last hit it - is a real pain.
Interesting that an update should come today in the Teams uservoice... but not in the SharePoint.
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 teams or channels each time, _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!
Star D. commented
I haven't attempted it yet. I admit I am a bit less interested in the *seemingly* easier fix of changing the name of a subfolder in a SharePoint Online document library (i.e, a standard channel) than in changing the name of a SharePoint Online site collection (i.e., a private channel, or the entire Team being renamed)
Star D, I tried both and neither is working. Are you seeing this work in your tenant?
Star D. commented
Anonymous, were you renaming a standard or private channel?
The SharePoint team snuck this text into their monthly roadmap update: "FIXED | Rename a channel in a Teams team and gets updated properly in the corresponding SharePoint folder". See: https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/sharepoint-roadmap-pitstop-march-2021/ba-p/2245785.
However, it's still not fixed for me after testing in several tenants (early and standard releases). Can anyone get this to work properly in their tenant?
Martina Unger commented
In terms of e.g. IS0 9001:2015 "Quality Management Systems" Document Control and clear trustful traceability is a requirement.
Hope to see this soon please!
This issue causes other problems within Teams. With a renamed channel, the SharePoint folder retains the original name, and "Files" tab in the renamed channel continues to reference the previous folder. Now it's possible to create another Teams channel and name it the same as the previous channel (before the rename), which uses the existing folder in SharePoint for file storage. This is a problem because the same files now appear in two different channels, and editing/deleting applies to "both" channels. Users expect edits and deletions to only affect one channel. When there are two channels pointing to the same file folder, this edits/deletes files in "both locations" because they're the same file(s).
Renaming the folder in SharePoint *breaks* the linkage with the Teams site - so the files disappear in the Teams channel. Then SharePoint automatically re-creates the previous folder name and includes the files BUT Teams oddly can't see those files. It shows a blank slate in the Files tab.
Because channels can't be re-created with the same name (except in the instance of a renamed channel detailed previously), users have almost no ability to fix this other than coming up with an entirely new naming scheme that doesn't fit their business.
This is seriously broken.
I named a channel with square brackets , this causes the SharePoint folder to also be named with square brackets. We cannot save files directly to the SharePoint folder now, it can only be uploaded or new MS office files created on the SharePoint itself. Thus, i need to be able to rename the SharePoint folder associated to the Channel!
It is now been 21 months since Admin stated his "Quick update".
Anybody but me think it is time for another update now?
Very frustrating. This is a site that should help with organisation but this bug makes things more confusing
So confusing...it would be great if this can be fixed ASAP!
4 years later...still waiting for a fix. As a software developer, I know this is not complicated, yet it is a big deal for users. Come on, Microsoft! Easy win, here!
Haritha Reddy Sama commented
This is causing confusion for our users. Need this fixed.
Hi, so you guys have had over 4 years to work on this simple issue. Do you plan on every fixing this?
Or should customers continue to pay for a software/services that are riddled with bugs and issues?
Hi, we have an issue as we renamed a channel in Teams where the files inside the channel still point to the old channel name so the files don't appear now in teams under the new channel name.
We can still see the files in office.com under the new name but can no longer see them in Teams.
I love teams, but it is problematic if we can't change names....and have a way to fix links that break between Teams and Sharepoint....Please don't ask us to never change channel names or not to move files around - we need to have ways of combining channels and a good archiving solution also please
Please fix this bug asap...big issue.
This is currently the biggest SharePoint issue !
Please fix it as soon as possible because this make impossible to make work Teams and SharePont togheter