SharePoint team says the Teams Channel rename bug is fixed, but it doesn't appear to be

%3CLINGO-SUB%20id%3D%22lingo-sub-2258794%22%20slang%3D%22en-US%22%3ESharePoint%20team%20says%20the%20Teams%20Channel%20rename%20bug%20is%20fixed%2C%20but%20it%20doesn't%20appear%20to%20be%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2258794%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmicrosoft-sharepoint-blog%2Fsharepoint-roadmap-pitstop-march-2021%2Fba-p%2F2245785%22%20target%3D%22_self%22%3ESharePoint%20Roadmap%20Pitstop%3A%20March%202021%20post%3C%2FA%3E%20(posted%203%2F31)%20included%20the%20following%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22PhoenixMS_0-1617802001323.png%22%20style%3D%22width%3A%20686px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F270734iF68DF52DDDF3E810%2Fimage-dimensions%2F686x60%3Fv%3Dv2%22%20width%3D%22686%22%20height%3D%2260%22%20role%3D%22button%22%20title%3D%22PhoenixMS_0-1617802001323.png%22%20alt%3D%22PhoenixMS_0-1617802001323.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EI've%20tested%20this%20in%20two%20different%20tenants%20(one%20standard%2C%20one%20early%20release)%20and%20the%20issue%20has%20not%20been%20resolved.%20There's%20no%3C%2FSPAN%3E%26nbsp%3Bcorresponding%20roadmap%20item%2C%20and%20no%20update%20has%20been%20posted%20to%20the%20two%20UserVoice%20items%20%3CA%20href%3D%22https%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F555103-public%2Fsuggestions%2F16934143-rename-of-team-channel-doesn-t-rename-associated-s%23%7Btoggle_previous_statuses%7D%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E%20and%20%3CA%20href%3D%22https%3A%2F%2Fsharepoint.uservoice.com%2Fforums%2F329214-sites-and-collaboration%2Fsuggestions%2F20029231-make-rename-in-teams-reflect-name-changes-in-share%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20had%20luck%20seeing%20this%20fix%20in%20their%20tenant%2C%20or%20have%20any%20more%20info%20on%20when%20we%20can%20expect%20this%20to%20take%20effect%3F%20This%20is%20a%20huge%20problem%20that%20is%20causing%20lots%20of%20headaches%20in%20many%20orgs%20and%20has%20been%20on%20the%20backlog%20for%20around%20four%20years%2C%20so%20I'm%20excited%20to%20finally%20seeing%20it%20possibly%20getting%20resolved.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2258794%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EFiles%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2258955%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20team%20says%20the%20Teams%20Channel%20rename%20bug%20is%20fixed%2C%20but%20it%20doesn't%20appear%20to%20be%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2258955%22%20slang%3D%22en-US%22%3EHello!%20That's%20major%20news%20and%20it%20sure%20sounds%20strange%20that%20this%20should%20be%20fixed%20without%20having%20heard%20a%20thing%20about%20it!%20I%20noticed%20you%20replied%20to%20the%20blog%2C%20I%20will%20certainly%20follow%20up%20on%20that.%20Thanks%20for%20the%20heads-up!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2272287%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20team%20says%20the%20Teams%20Channel%20rename%20bug%20is%20fixed%2C%20but%20it%20doesn't%20appear%20to%20be%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2272287%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EJust%20bumping%20this%2C%20as%20I%20was%20really%20hoping%20to%20hear%20from%20the%20product%20team%20on%20why%20this%20long-awaited%20bug%20fix%20was%20announced%20as%20fixed%2C%20but%20seemingly%20has%20not%20been.%20Thank%20you!%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2272858%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20team%20says%20the%20Teams%20Channel%20rename%20bug%20is%20fixed%2C%20but%20it%20doesn't%20appear%20to%20be%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2272858%22%20slang%3D%22en-US%22%3EWe%20noted%20it%20as%20beginning%20to%20release%20within%20the%20latest%20roadmap%20pitstop%20blog.%20It%20is%20not%20at%20complete%20100%25%20rollout%20as%20of%20now.%20The%20fix%20was%20identified%20and%20making%20progress.%20Thanks%20for%20reaching%20out.%20The%20teams%20are%20working%20hard%20to%20ensure%20the%20integration%20between%20SharePoint%20and%20Teams%20is%20more%20seamless%20over%20time%2C%20and%20it%20helps%20to%20know%20those%20who%20have%20the%20updated%20experience%20are%20seeing%20progress%2C%20knowing%20that%20others%20do%20not%20have%20the%20experience%20yet.%20-%20Mark%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2273081%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20team%20says%20the%20Teams%20Channel%20rename%20bug%20is%20fixed%2C%20but%20it%20doesn't%20appear%20to%20be%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2273081%22%20slang%3D%22en-US%22%3EAppreciate%20the%20response%20Mark%2C%20thanks!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2272363%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20team%20says%20the%20Teams%20Channel%20rename%20bug%20is%20fixed%2C%20but%20it%20doesn't%20appear%20to%20be%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2272363%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F399787%22%20target%3D%22_blank%22%3E%40PhoenixMS%3C%2FA%3E%26nbsp%3BYes%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F96%22%20target%3D%22_blank%22%3E%40Mark%20Kashman%3C%2FA%3E%26nbsp%3Breally%20should%20reply%20to%20that%2C%20at%20least%20in%20the%20blog%20post%2C%20as%20it's%20far%20too%20big%20news.%20You%20can't%20post%20something%20like%20that%20and%20not%20follow%20up%20the%20questions.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2293968%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20team%20says%20the%20Teams%20Channel%20rename%20bug%20is%20fixed%2C%20but%20it%20doesn't%20appear%20to%20be%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2293968%22%20slang%3D%22en-US%22%3EOne%20thing%20I've%20noticed%20is%20that%20SharePoint%20groups-based%20sites%20originally%20created%20by%20creating%20a%20Team%20have%20the%20feature%20where%20it%20indicates%20a%20folder%20is%20connected%20to%20a%20Team.%20But%20sites%20created%20with%20M365%20groups%20years%20ago%20do%20not%20display%20this.%20I%20hope%20that%20this%20feature%20about%20fixing%20channel%20renames%20works%20for%20all%20groups%2Fteams%20connected%20sites.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2298085%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20team%20says%20the%20Teams%20Channel%20rename%20bug%20is%20fixed%2C%20but%20it%20doesn't%20appear%20to%20be%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2298085%22%20slang%3D%22en-US%22%3EThis%20item%20was%20just%20added%20to%20the%20Roadmap%20today%20-%20I%20wonder%20if%20this%20is%20the%20peg%20for%20this%20bug%20fix%3F%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Froadmap%3Ffilters%3D%26amp%3Bsearchterms%3D81945%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Froadmap%3Ffilters%3D%26amp%3Bsearchterms%3D81945%3C%2FA%3E%3CBR%20%2F%3ESharePoint%3A%20Updates%20for%20Microsoft%20Teams%20connected%20team%20sites%3CBR%20%2F%3E%3CBR%20%2F%3EEvery%20Microsoft%20Teams%20team%20is%20connected%20to%20a%20SharePoint%20team%20site.%20If%20you%20create%20a%20private%20channel%2C%20it%20gets%20a%20unique%20team%20site.%20You%20will%20see%20specific%20updates%2C%20including%20updates%20to%20site%20features%2C%20site%20permissions%20alignment%2C%20site%20classifications%20and%20sensitivity%20labels%2C%20and%20improvements%20to%20the%20user%20interface.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2298984%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20team%20says%20the%20Teams%20Channel%20rename%20bug%20is%20fixed%2C%20but%20it%20doesn't%20appear%20to%20be%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2298984%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F399787%22%20target%3D%22_blank%22%3E%40PhoenixMS%3C%2FA%3E%26nbsp%3B-%20Hard%20to%20tell%20what%20that%20roadmap%20item%20is%20going%20to%20do%20since%20it's%20incredibly%20vague.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2306626%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20team%20says%20the%20Teams%20Channel%20rename%20bug%20is%20fixed%2C%20but%20it%20doesn't%20appear%20to%20be%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2306626%22%20slang%3D%22en-US%22%3E%3CP%3EThere's%20now%20a%20roadmap%20item%20for%20this%20issue!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Froadmap%3Ffilters%3D%26amp%3Bsearchterms%3D72211%22%20rel%3D%22noreferrer%20noopener%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Froadmap%3Ffilters%3D%26amp%3Bsearchterms%3D72211%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%20Teams%3A%20Pairing%20the%20channel%20and%20the%20corresponding%20SharePoint%20folder%20name.%3C%2FP%3E%3CP%3EWhen%20renaming%20a%20Teams%E2%80%99%20channel%2C%20the%20corresponding%20SharePoint%20folder%20will%20be%20renamed%20and%20reflect%20the%20new%20name.%20This%20will%20help%20create%20consistency%20across%20Microsoft%20365%20endpoints%2C%20making%20it%20easier%20on%20users%20to%20find%20their%20files%20from%20anywhere.%20This%20new%20feature%20will%20be%20available%20for%20all%20Standard%20and%20Private%20channels.%20For%20Standard%20channels%20%E2%80%93%20The%20corresponding%20folder%20in%20SharePoint%20will%20be%20renamed.%20For%20Private%20channels%20%E2%80%93%20The%20corresponding%20site%20name%20and%20the%20folder%20in%20SharePoint%20will%20be%20renamed.%20For%20legacy%20Teams%20channels%20that%20were%20renamed%20prior%20to%20this%20rollout%2C%20there%20will%20be%20no%20change%20in%20experience.%20When%20a%20legacy%20channel%20is%20renamed%20after%20this%20release%2C%20it%20will%20simultaneously%20rename%20the%20corresponding%20SharePoint%20folder.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F551905%22%20target%3D%22_blank%22%3E%40ChristianBergstrom%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2306644%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20team%20says%20the%20Teams%20Channel%20rename%20bug%20is%20fixed%2C%20but%20it%20doesn't%20appear%20to%20be%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2306644%22%20slang%3D%22en-US%22%3EThat's%20more%20like%20it!%20And%20way%20better%20official%20channel%20than%20in%20a%20blog%20post%20(no%20offence%20Mark).%20Thanks%20for%20%40mentioning%20me!%3C%2FLINGO-BODY%3E
Contributor

The SharePoint Roadmap Pitstop: March 2021 post (posted 3/31) included the following:

 

PhoenixMS_0-1617802001323.png

I've tested this in two different tenants (one standard, one early release) and the issue has not been resolved. There's no corresponding roadmap item, and no update has been posted to the two UserVoice items here and here.

 

Has anyone had luck seeing this fix in their tenant, or have any more info on when we can expect this to take effect? This is a huge problem that is causing lots of headaches in many orgs and has been on the backlog for around four years, so I'm excited to finally seeing it possibly getting resolved.

23 Replies
Hello! That's major news and it sure sounds strange that this should be fixed without having heard a thing about it! I noticed you replied to the blog, I will certainly follow up on that. Thanks for the heads-up!

Just bumping this, as I was really hoping to hear from the product team on why this long-awaited bug fix was announced as fixed, but seemingly has not been. Thank you!

@PhoenixMS Yes @Mark Kashman really should reply to that, at least in the blog post, as it's far too big news. You can't post something like that and not follow up the questions.

We noted it as beginning to release within the latest roadmap pitstop blog. It is not at complete 100% rollout as of now. The fix was identified and making progress. Thanks for reaching out. The teams are working hard to ensure the integration between SharePoint and Teams is more seamless over time, and it helps to know those who have the updated experience are seeing progress, knowing that others do not have the experience yet. - Mark
Appreciate the response Mark, thanks!
One thing I've noticed is that SharePoint groups-based sites originally created by creating a Team have the feature where it indicates a folder is connected to a Team. But sites created with M365 groups years ago do not display this. I hope that this feature about fixing channel renames works for all groups/teams connected sites.
This item was just added to the Roadmap today - I wonder if this is the peg for this bug fix?
https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=&searchterms=81945
SharePoint: Updates for Microsoft Teams connected team sites

Every Microsoft Teams team is connected to a SharePoint team site. If you create a private channel, it gets a unique team site. You will see specific updates, including updates to site features, site permissions alignment, site classifications and sensitivity labels, and improvements to the user interface.

@PhoenixMS - Hard to tell what that roadmap item is going to do since it's incredibly vague.

There's now a roadmap item for this issue!

 

https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=&searchterms=72211

 

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.

 

@ChristianBergstrom 

That's more like it! And way better official channel than in a blog post (no offence Mark). Thanks for @mentioning me!
@PhoenixMS

I've checked the roadmap and now it says "This feature has been updated to reflect new timing" and the new release date is "February 2022".
Federico
Are there any further details on expected behavior for these changes? I've tested by updating both Standard and Private channels in Teams and the folder names have not been updated in SharePoint hours later (although the site name was immediately updated for the Private channel). Yet, if I try to change the folder names directly in SharePoint, I get an error message: "Error: To update this folder, go to the channel in Microsoft Teams." Really frustrating that there is so little info available about this from Microsoft.
same to us
I think it not publish yet
detail in https://admin.microsoft.com/Adminportal/Home#/MessageCenter/:/messages/MC306666
or https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=&searchterms=72211

Key points

Microsoft 365 Roadmap ID:72211.
Timing: late February through late April
Roll-out: tenant level
Control type: admin control
Action: review and assess

For this bug correction, there is still a problem to fix.  After a change in the Team or channel name, there is a delay on the share point update, but this is not so critical.  The main problem is that on the "my Sites" side bar, the old name is still there and don´t get updated at all! @PhoenixMS 

 

 

Regarding this bug: https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=&searchterms=72211

@PhoenixMS I am trying to resolve a problem similar to what I'm reading here in this message.

 

A few months back we changed the name of a teams channel from “Youth Groups” to “National Youth Missions”.  When we did that it did not change the file folder host name from “Youth Groups” to “National Youth Missions”.  One of our teammates was trying to correct that and decided to change the name of the folder manually on his Mac through the Finder synced files.  I believe this essentially made the change at the SharePoint location which started a mess.  As I'm sure you know, the name change created the new “National Youth Missions” folder and moved all the files but it disassociated the files from “National Youth Missions” teams channel.  

 

Now, our “Youth Groups” folder that is hosted in the “National Youth Missions” Team channel is empty.  The original files are still in the new folder that was created called “National Youth Missions” but are not associated with the channel.  We'd like to try and keep the teams channel “National Youth Missions” and change the host folder in that channel to the “National Youth Missions” folder that now holds all the files.  However, we are not sure that is possible or can be fixed.

 

According to the Microsoft 365 Roadmap site, "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."  I suspect this we are in the no change to experience group since this problem occurred several months ago.  I think I understand and have read things through on this topic but I may have missed something or there is an answer out there I have overlooked.  What recourse do we have to correct this problem?  Thanks!

workaround, but be careful:

1. in MS Teams: rename channel to old name
2. in MS Teams: delete channel
3. in Sharepoint library for teams: move folder for the deleted channel to one drive
4. in MS Teams: create new channel with correct name

result:
no waste in the teams-sharepoint-library and correct names
problem:
missing the old things of the channel (added apps, publications, files)

a really funny behaviour occur when you
1. create a channel 'A'
2. rename 'A' to 'B' and
3. create a second channel 'A' (you can see the files und communication from old 'A' which is now 'B' in the new 'A' as well)
4. rename new 'A' to 'C' it will loose all connections to old 'A'

@Carey_Tuhaka no, the issue is still there. I just tried it. :(