Yammer Group Name Managing Change - Change Management

%3CLINGO-SUB%20id%3D%22lingo-sub-77093%22%20slang%3D%22en-US%22%3EYammer%20Group%20Name%20Managing%20Change%20-%20Change%20Management%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-77093%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20recent%20changes%20with%20Yammer%20Connected%20groups%20bring%20many%20benefits%3A%20%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FYammer-and-Office-365-Groups-d8c239dc-a48b-47ab-b85e-6b4b8191a869%3Fui%3Den-US%26amp%3Brs%3Den-US%26amp%3Bad%3DUS%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FYammer-and-Office-365-Groups-d8c239dc-a48b-47ab-b85e-6b4b8191a869%3Fui%3Den-US%26amp%3Brs%3Den-US%26amp%3Bad%3DUS%3C%2FA%3E%20but%20one%20behavior%20that%20will%20need%20to%20be%20managed%20is%20educating%20my%20users%20to%20avoid%20changing%20Yammer%20group%20names%20after%20creation.%20I%20tried%20it%20for%20one%20of%20our%20groups%20and%20the%20new%20Yammer%20group%20name%20took%20place%20about%2015%20min.%20after%20I%20saved%20changes.%20I%20could%20see%20the%20change%20in%20desktop%20view%20(within%20the%20group).%20However%2C%20the%20change%20was%20not%20visible%20on%20the%20side%20navigation%20nor%20on%20team%20site%20name%20nor%20on%20the%20mobile%20app.%20old%20Yammer%20group%20name%20reverted%20back%20the%20next%20day.%20Correct%20me%20if%20I'm%20wrong%20this%20should%20be%20expected%20due%20to%20DL%2FO365%20connection.%20So%20aside%20from%20discouraging%20people%20to%20loosely%20make%20name%20changes%20(like%20in%20the%20past)%20my%20question%20-%20what%20is%20the%20best%20practice%20for%20changing%20Yammer%20group%20names%3F%20Has%20anyone%20tested%20changing%20Yammer%20group%20names%20after%20backfill%3F%20How%20are%20you%20managing%20this%20change%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-77093%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EBest%20Practice%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ECommunity%20Management%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EYammer%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-154808%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Group%20Name%20Managing%20Change%20-%20Change%20Management%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-154808%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%2C%20Lilian.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOurs%20was%20also%20an%20exception%20from%20the%20integration%20between%20Yammer%20and%20O365%20groups.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20found%20that%20the%20Yammer%20group%20admin%20who%20was%20making%20the%20changes%20in%20Yammer%20was%20not%20listed%20as%20owner%20in%20O365%2C%20hence%20changes%20were%20being%20overwritten.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESteps%20to%20resolve%3A%3C%2FP%3E%0A%3CP%3E1.%20Added%20the%20Yammer%20group%20admin%20as%20owner%20in%20O365.%20This%20stopped%20the%20changes%20from%20reverting%20back.%20However%2C%20this%20did%20not%20synchronise%20the%20group%20name%20and%20privacy%20settings%20back%20to%20O365.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E2.%20Add%20myself%20as%20group%20admin.%20This%20was%20reflected%20in%20the%20O365%20group%3C%2FP%3E%0A%3CP%3E3.%20Made%20a%20minor%20change%20to%20the%20group%20name%20in%20Yammer.%20This%20started%20reflecting%20in%20O365%3C%2FP%3E%0A%3CP%3E4.%20Change%20the%20Yammer%20group%20name%20back%20to%20what%20we%20want%20it%20to%20be.%20This%20was%20fully%20synchronized%20in%20O365%2C%20including%20group%20privacy%20settings%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI'm%20thinking%20that%20I%20could%20have%20skipped%20step%201.%20Once%20I%20made%20the%20changes%20which%20got%20the%20group%20to%20synchronize%2C%20I%20think%20that%20the%20missing%20group%20admin%20would%20also%20have%20synched.%20But%20that%20will%20be%20a%20test%20if%20I%20run%20into%20this%20again%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-154259%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Group%20Name%20Managing%20Change%20-%20Change%20Management%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-154259%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F78054%22%20target%3D%22_blank%22%3E%40Ivo%20Essenberg%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3ESorry%20for%20the%20late%20response.%20Yes%2C%20MS%20did%20help%20us%20resolve%20the%20issue.%20At%20the%20time%20of%20this%20post%20the%20issue%20was%20due%20to%20an%20exception%20that%20occurred%20when%20the%20integration%20between%20Yammer%20and%20O365%20Groups%20took%20place.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20don't%20know%20if%20there%20is%20a%20more%20efficient%20way%20to%20do%20this%20besides%20having%20the%20O365%20Global%20Admin%20making%20the%20one%20time%20change.%20If%20a%20Yammer%20group%20owner%20wants%20to%20make%20the%20change%20MS%20advised%20changes%26nbsp%3Bshould%20take%20place%20on%20the%20O365%20Group%20side%20first.%20So%26nbsp%3Bwe%20go%20to%20the%26nbsp%3BYammer%20Group%20SP%20site%20(or%20document%20library)%3A%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3ESite%20Information%20%26gt%3B%20Change%20Name.%3C%2FLI%3E%0A%3CLI%3ESite%20Assets%20%26gt%3B%20Change%20OneNote%20Name%3C%2FLI%3E%0A%3CLI%3EYammer%20Group%20Settings%20%26gt%3B%20Change%20Name%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3EFYI%2C%20the%20learning%20for%20me%20was%20to%20educate%20users%26nbsp%3Bto%20take%20some%20time%20to%20THINK%20about%20what%20they%20want%20to%20name%20their%20group%20to%20help%20mitigate%20these%20scenarios%20%3B-).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-152185%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Group%20Name%20Managing%20Change%20-%20Change%20Management%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-152185%22%20slang%3D%22en-US%22%3E%3CP%3ELilian%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EDid%20Microsoft%20ever%20resolve%20this%20one%20for%20you%3F%20I've%20just%20been%20notified%20of%20the%20same%20issue%20with%20one%20of%20our%20(high-profile)%20groups%2C%20and%20will%20be%20raising%20a%20support%20ticket%20shortly.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%20for%20any%20feedback%20or%20updates%20you%20had%20from%20Microsoft.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECheers%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIvo%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-123924%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Group%20Name%20Managing%20Change%20-%20Change%20Management%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-123924%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Joanna%2C%3C%2FP%3E%3CP%3EI'm%20not%20aware%20of%20a%20workaround%20(would%20love%20to%20learn%20if%20there%20is%20one).%20If%20the%20group%20is%20high%20priority%20(high%20impact)%26nbsp%3BI%20would%20advice%20you%20open%20a%20ticket%20and%20escalate%20it%20to%20urgent%20to%20hopefully%20get%20faster%20support.%20Assuming%20the%20issue%20is%20still%20the%20same%20exception%20I'm%20guessing%20it%20might%20be%20faster%20for%20you%26nbsp%3Bsince%20the%20team%20might%20be%20more%20familiar%20now%26nbsp%3B(when%20I%20faced%20this%20it%20was%20just%20surfacing%20as%20an%20issue).%20Sorry%20I%20can't%20help%20further!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-123704%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Group%20Name%20Managing%20Change%20-%20Change%20Management%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-123704%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20i%20am%20having%20the%20issue%20of%20a%20Yammer%20group%20name%20not%20changing.%20This%20is%20for%20quite%20a%20high%20profile%20group%20so%20keen%20to%20get%20it%20fixed%20asap.%20Do%20you%20know%20if%20there%20is%20any%20workaround%20to%20get%20this%20sorted%20-%20just%20concerned%20that%20a%20microsoft%20support%20ticket%20might%20take%20days%20to%20be%20received%20and%20actioned...(plus%20I%20need%20to%20raise%20a%20ticket%20with%20our%20tech%20desk%20for%20them%20to%20raise%20one%20with%20Microsoft%2C%20so%20add%20on%20the%20internal%20process%20time).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-81173%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Group%20Name%20Managing%20Change%20-%20Change%20Management%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-81173%22%20slang%3D%22en-US%22%3EJust%20updating%20this%20thread%20for%20anyone%20having%20this%20issue%20or%20question.%20I%20found%20out%20that%20for%20some%20reason%20there%20was%20an%20exception%20when%20the%20backfill%20occurred%20in%20our%20network%20on%205%2F31.%20Since%20the%20group%20was%20never%20really%20%22connected%22%20the%20Yammer%20group%20name%20change%20kept%20reverting%20back%20to%20old%20name%20and%20change%20did%20not%20reflect%20on%20O365%20group%20side.%20Also%2C%20the%20Yammer%20admins%20did%20not%20carry%20over%20as%20O365%20Group%20owners.%20Further%2C%20since%20the%20O365%20group%20owner%20has%20to%20make%20the%20change%20there%20was%20no%20way%20of%20making%20name%20change%20to%20stick.%20Another%20red%20flag%20to%20let%20you%20know%20there%20is%20a%20problem%2C%20is%20to%20look%20for%20a%20difference%20in%20membership%20numbers%20between%20Yammer%20legacy%20group%20and%20O365%20group%20members.%20These%20have%20to%20match.%3CBR%20%2F%3EThat%20said%2C%20MS%20is%20still%20working%20with%20us%20to%20help%20correct%20the%20problem%20so%20the%20ticket%20is%20still%20open.%20If%20you%20have%20a%20legacy%20group%20that%20hasn't%20synced%20based%20on%20the%20two%20indicators%20I%20mentioned%20above%20you%20might%20want%20to%20open%20a%20ticket%20with%20MS.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-77509%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Group%20Name%20Managing%20Change%20-%20Change%20Management%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-77509%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Larry%2C%20I%20opened%20a%20ticket%20with%20MS%20for%20guidance.%20So%20far%20what%20I%20know%20(and%20what%20they%20said)%20is%20that%20because%20Yammer%20connected%20groups%20touch%20on%20everything%20(SP%2C%20exchange%20etc.)%20it's%20not%20as%20easy%20as%20it%20used%20to%20be%20and%20will%20require%20the%20GA%20to%20help%20make%20changes.%20I'll%20make%20sure%20to%20report%20back%20what%20I%20learned...stay%20tuned!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-77507%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Group%20Name%20Managing%20Change%20-%20Change%20Management%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-77507%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Christopher%2C%3C%2FP%3E%3CP%3EFrom%20what%20I%20understand%2C%20for%20deleted%20Yammer%20groups%2C%20this%20is%20expected%20behavior%20due%20to%20the%20connected%20O365%20resources.%20I%20think%20I%20read%20somewhere%20it%20takes%20about%2030%20days.%20Not%20entirely%20sure%2C%20I'll%20try%20to%20dig%20the%20original%20conversation.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-77506%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Group%20Name%20Managing%20Change%20-%20Change%20Management%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-77506%22%20slang%3D%22en-US%22%3E%3CP%3EAlso%20eager%20to%20hear%20the%20answer.%26nbsp%3B%20Related%20question.%26nbsp%3B%20User%20deleted%20a%20Yammer%20Group.%26nbsp%3B%20After%2024%20hours%2C%20the%20name%20of%20the%20Yammer%20group%20still%20shows%20in%20use%2C%20preventing%20us%20form%20creating%20a%20new%20Yammer%20group%20with%20the%20same%20name.%26nbsp%3B%20Is%20that%20expected%20behavior%3F%26nbsp%3B%20Can%20we%20not%20reclaim%20names%20from%20deleted%20Yammer%20groups%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-77398%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20Group%20Name%20Managing%20Change%20-%20Change%20Management%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-77398%22%20slang%3D%22en-US%22%3EThanks%2C%20Lillian%20for%20the%20great%20question.%20Eager%20to%20learn%20from%20peoples'%20experiences%20here.%3C%2FLINGO-BODY%3E
Highlighted
Regular Contributor

The recent changes with Yammer Connected groups bring many benefits: https://support.office.com/en-us/article/Yammer-and-Office-365-Groups-d8c239dc-a48b-47ab-b85e-6b4b81... but one behavior that will need to be managed is educating my users to avoid changing Yammer group names after creation. I tried it for one of our groups and the new Yammer group name took place about 15 min. after I saved changes. I could see the change in desktop view (within the group). However, the change was not visible on the side navigation nor on team site name nor on the mobile app. old Yammer group name reverted back the next day. Correct me if I'm wrong this should be expected due to DL/O365 connection. So aside from discouraging people to loosely make name changes (like in the past) my question - what is the best practice for changing Yammer group names? Has anyone tested changing Yammer group names after backfill? How are you managing this change?

10 Replies
Highlighted
Thanks, Lillian for the great question. Eager to learn from peoples' experiences here.
Highlighted

Also eager to hear the answer.  Related question.  User deleted a Yammer Group.  After 24 hours, the name of the Yammer group still shows in use, preventing us form creating a new Yammer group with the same name.  Is that expected behavior?  Can we not reclaim names from deleted Yammer groups?

Highlighted

Hi Christopher,

From what I understand, for deleted Yammer groups, this is expected behavior due to the connected O365 resources. I think I read somewhere it takes about 30 days. Not entirely sure, I'll try to dig the original conversation. 

Highlighted

Thanks Larry, I opened a ticket with MS for guidance. So far what I know (and what they said) is that because Yammer connected groups touch on everything (SP, exchange etc.) it's not as easy as it used to be and will require the GA to help make changes. I'll make sure to report back what I learned...stay tuned!

Highlighted
Just updating this thread for anyone having this issue or question. I found out that for some reason there was an exception when the backfill occurred in our network on 5/31. Since the group was never really "connected" the Yammer group name change kept reverting back to old name and change did not reflect on O365 group side. Also, the Yammer admins did not carry over as O365 Group owners. Further, since the O365 group owner has to make the change there was no way of making name change to stick. Another red flag to let you know there is a problem, is to look for a difference in membership numbers between Yammer legacy group and O365 group members. These have to match.
That said, MS is still working with us to help correct the problem so the ticket is still open. If you have a legacy group that hasn't synced based on the two indicators I mentioned above you might want to open a ticket with MS.
Highlighted

So i am having the issue of a Yammer group name not changing. This is for quite a high profile group so keen to get it fixed asap. Do you know if there is any workaround to get this sorted - just concerned that a microsoft support ticket might take days to be received and actioned...(plus I need to raise a ticket with our tech desk for them to raise one with Microsoft, so add on the internal process time).

Highlighted

Hi Joanna,

I'm not aware of a workaround (would love to learn if there is one). If the group is high priority (high impact) I would advice you open a ticket and escalate it to urgent to hopefully get faster support. Assuming the issue is still the same exception I'm guessing it might be faster for you since the team might be more familiar now (when I faced this it was just surfacing as an issue). Sorry I can't help further!

Highlighted

Lilian,

 

Did Microsoft ever resolve this one for you? I've just been notified of the same issue with one of our (high-profile) groups, and will be raising a support ticket shortly.

 

Thanks for any feedback or updates you had from Microsoft.

 

Cheers,

 

Ivo

Highlighted

Hi @Deleted,

Sorry for the late response. Yes, MS did help us resolve the issue. At the time of this post the issue was due to an exception that occurred when the integration between Yammer and O365 Groups took place.

 

I don't know if there is a more efficient way to do this besides having the O365 Global Admin making the one time change. If a Yammer group owner wants to make the change MS advised changes should take place on the O365 Group side first. So we go to the Yammer Group SP site (or document library): 

  1. Site Information > Change Name.
  2. Site Assets > Change OneNote Name
  3. Yammer Group Settings > Change Name

FYI, the learning for me was to educate users to take some time to THINK about what they want to name their group to help mitigate these scenarios ;-).

Highlighted

Thanks, Lilian.

 

Ours was also an exception from the integration between Yammer and O365 groups.

 

We found that the Yammer group admin who was making the changes in Yammer was not listed as owner in O365, hence changes were being overwritten.

 

Steps to resolve:

1. Added the Yammer group admin as owner in O365. This stopped the changes from reverting back. However, this did not synchronise the group name and privacy settings back to O365.

 

2. Add myself as group admin. This was reflected in the O365 group

3. Made a minor change to the group name in Yammer. This started reflecting in O365

4. Change the Yammer group name back to what we want it to be. This was fully synchronized in O365, including group privacy settings

 

I'm thinking that I could have skipped step 1. Once I made the changes which got the group to synchronize, I think that the missing group admin would also have synched. But that will be a test if I run into this again :)