SOLVED

Converting Yammer groups to O365 Connected Yammer Groups

%3CLINGO-SUB%20id%3D%22lingo-sub-139239%22%20slang%3D%22en-US%22%3EConverting%20Yammer%20groups%20to%20O365%20Connected%20Yammer%20Groups%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-139239%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20have%20only%20given%20selected%20users%20the%20permissions%20to%20create%20Office%20365%20Groups.%20Creating%20a%20Yammer%20group%20with%20an%20account%20without%20this%20permission%20results%20in%20a%20normal%20Yammer%20group%20(not%20an%20O365%20Connected%20Yammer%20Group).%20This%20is%20fine%2C%20but%20we%20do%20want%20these%20groups%20to%20be%20converted%20to%20Connected%20Groups%20later%20on.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhat%20I%20did%20to%20test%20this%20was%20added%20an%20account%20with%20the%20permissions%20to%20create%20O365%20Groups%20as%20an%20admin%20to%20the%20Yammer%20group.%20Nothing%20happened.%20Logged%20in%20with%20the%20account%20that%20created%20the%20group%20and%20left%20it%2C%20but%20still%2C%20nothing%20happened.%20My%20assumption%20was%20that%20all%20Yammer%20groups%20will%20be%20converted%20to%20O365%20Connected%20Yammer%20groups%20if%20they%20are%20eligible.%20I%20can%20create%20connected%20groups%20with%20the%20account%20that%20has%20the%20right%20permissions%2C%20but%20I%20can't%20figure%20out%20how%20to%20convert%20the%20normal%26nbsp%3B%20Yammer%20groups.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-139239%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EYammer%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297804%22%20slang%3D%22en-US%22%3ERe%3A%20Converting%20Yammer%20groups%20to%20O365%20Connected%20Yammer%20Groups%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297804%22%20slang%3D%22en-US%22%3E%3CP%3Ewhen%20your%20network%20has%20the%20correct%20configuration%20and%20it%20still%20doesn't%20work%2C%20then%20I%20would%20recommend%20creating%20a%20ticket%20with%20MSFT%20support.%20Have%20shared%20the%20requirements%20above.%20Have%20also%20noticed%20that%20in%20the%20security%20settings%20for%20Yammer%20it%20might%20say%20that%20connected%20groups%20are%20enabled%20even%20if%20you%20have%20multiple%20Yammer%20networks.%20It%20also%20won't%20say%20%22disabled%22%20if%20users%20don't%20have%20the%20permissions%20to%20create%20O365%20groups.%26nbsp%3BThe%20fact%20that%20it%20shows%20%22disabled%22%20means%20that%20something%20else%20needs%20to%20be%20fixed%20and%20the%20only%20thing%20that%20I%20can%20think%20of%20that%20would%20result%20in%20it%20being%20disabled%20is%20when%20you're%20not%20enforcing%20O365%20identities.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-297557%22%20slang%3D%22en-US%22%3ERe%3A%20Converting%20Yammer%20groups%20to%20O365%20Connected%20Yammer%20Groups%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-297557%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%20i%20have%20enabled%20the%20network%20settings%20on%20our%20tenant%20but%20still%20shows%20disabled%20for%20the%20office%20365%20group%20creation%20tenant%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-284680%22%20slang%3D%22en-US%22%3ERe%3A%20Converting%20Yammer%20groups%20to%20O365%20Connected%20Yammer%20Groups%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-284680%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2144%22%20target%3D%22_blank%22%3E%40Pooya%20Obbohat%3C%2FA%3E%20for%20the%20follow%20up%20info!%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-281069%22%20slang%3D%22en-US%22%3ERe%3A%20Converting%20Yammer%20groups%20to%20O365%20Connected%20Yammer%20Groups%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-281069%22%20slang%3D%22en-US%22%3E%3CP%3EIssue%20was%20fixed%20and%20now%20I%20can%20confirm%20that%20toggling%20of%20the%20privacy%20setting%20still%20works.%20Couple%20of%20things%20you%20could%20check%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-%20make%20sure%20you%20have%20a%201%3A1%20network%3Atenant%20configuration.%20To%20check%2C%20simply%20go%20to%20Yammer%20admin%2C%20start%20network%20migration.%20Is%20there%20a%20network%20you%20can%20merge%3F%20if%20not%2C%20then%20it's%201%3A1%3C%2FP%3E%3CP%3E-%20make%20sure%20O365%20identities%20are%20enforced%26nbsp%3B%3C%2FP%3E%3CP%3E-%20make%20sure%20that%20in%20security%20settings%20of%20Yammer%20admin%20portal%2C%20connected%20groups%20is%20enabled%3C%2FP%3E%3CP%3E-%20user%20needs%20permission%20to%20create%20O365%20groups%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOnly%20public%20and%20private%20%26amp%3B%20listed%20groups%20are%20supported.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-280933%22%20slang%3D%22en-US%22%3ERe%3A%20Converting%20Yammer%20groups%20to%20O365%20Connected%20Yammer%20Groups%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-280933%22%20slang%3D%22en-US%22%3E%3CP%3ECreation%20of%20connected%20groups%20as%20stopped%20working%20in%20my%20own%20tenant.%20Have%20to%20create%20a%20ticket%20because%20the%20network%20meets%20all%20requirements%20and%20Office%20365%20group%20creation%20is%20enabled%20(tested%20by%20creating%20a%20Plan).%20Will%20report%20back%20when%20that%20is%20fixed.%20Can't%20test%20this%20unfortunately%20on%26nbsp%3Bother%20networks%20I%20have%20access%20to.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-279242%22%20slang%3D%22en-US%22%3ERe%3A%20Converting%20Yammer%20groups%20to%20O365%20Connected%20Yammer%20Groups%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-279242%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20anyone%20confirm%20if%20this%20toggling%20of%20the%20privacy%20setting%20still%20works%20to%20connect%20an%20existing%20group%20to%20an%20O365%20group%3F%20I%20tried%20it%20several%20times%20today%20without%20success.%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3EBrian%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-197311%22%20slang%3D%22en-US%22%3ERe%3A%20Converting%20Yammer%20groups%20to%20O365%20Connected%20Yammer%20Groups%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-197311%22%20slang%3D%22en-US%22%3E%3CP%3EAre%20you%20switching%20the%20privacy%20setting%20of%20the%20group%20by%20using%20an%20account%20with%20the%20permission%20to%20create%20Office%20365%20groups%3F%20When%20you%20have%20other%20O365%20connected%20Yammer%20groups%2C%20this%20means%20that%20you%20already%20have%20a%201-on-1%20network-tenant%20configuration%20and%20you%20are%20enforcing%20the%20O365%20identities.%20The%20only%20other%20requirement%20for%20connected%20Yammer%20groups%20is%20that%20the%20account%20creating%20the%20group%20(or%20in%20this%20case%2C%20the%20account%20changing%20the%20privacy%20setting%20to%20public%20and%20back%20to%20private%20%26amp%3B%20listed%20in%20the%20directory)%20has%20the%20permission%20to%20create%20O365%20groups.%20The%20only%20other%20thing%20I%20can%20think%20of%20that%20could%20cause%20this%20is%20when%20you%20already%20have%20an%20O365%20group%20with%20the%20same%20name.%20Not%20sure%20what%20will%20happen%20then.%20Changing%20the%20privacy%20setting%20has%20worked%20for%20me%20in%20multiple%20tenants%20where%20only%20a%20selected%20group%20of%20people%20are%20allowed%20to%20create%20O365%20groups.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-197229%22%20slang%3D%22en-US%22%3ERe%3A%20Converting%20Yammer%20groups%20to%20O365%20Connected%20Yammer%20Groups%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-197229%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20Pooya%20for%20your%20quick%20reply.%3C%2FP%3E%3CP%3EUnfortunately%2C%20this%20doesn%E2%80%99t%20seem%20to%20make%20it%20for%20me.%3C%2FP%3E%3CP%3EIf%20I%20create%20a%20new%20Yammer-group%20it%20is%20an%20Office%20Group%20with%20all%20its%20capabilities%20such%20as%20SharePoint%20and%20OneNote.%20However%2C%20now%20I%20would%20like%20to%20convert%20the%20old%20Yammer%20groups%20which%20is%20very%20active%20and%20with%20a%20lot%20of%20members%20to%20an%20Office%20Group%20enabled%20Yammer%20group.%20The%20trick%20worked%20on%20a%20%E2%80%9Csandbox%E2%80%9D%20group%20I%20have%20that%20was%20private%2C%20however%2C%20when%20I%20try%20on%20my%20public%20main%20group%20it%20doesn%E2%80%99t%20work.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-197159%22%20slang%3D%22en-US%22%3ERe%3A%20Converting%20Yammer%20groups%20to%20O365%20Connected%20Yammer%20Groups%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-197159%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20Office%20365%20group%20will%20be%20created%20and%20linked%20automatically.%20All%20I%20had%20to%20do%20was%20change%20the%20privacy%20setting%20of%20the%20Yammer%20group%20and%20set%20it%20back%20to%20the%20previous%20setting.%20This%20initiates%20the%20provisioning%20of%20the%20O365%20group.%20You%20do%20need%20the%20following%20to%20make%20this%20work%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-%20The%20user%20doing%20this%20should%20be%20allowed%20to%20create%20Office%20365%20groups%3C%2FP%3E%3CP%3E-%20Private%20Yammer%20groups%20are%20only%20supported%20if%20they%20are%20listed%20in%20the%20directory%3C%2FP%3E%3CP%3E-%20O365%20connected%20Yammer%20groups%20only%20work%20if%20you%20have%201%20Yammer%20network%26nbsp%3B%3C%2FP%3E%3CP%3E-%20O365%20connected%20Yammer%20groups%20only%20work%20if%20you%20have%20enforced%20O365%20identities%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-196976%22%20slang%3D%22en-US%22%3ERe%3A%20Converting%20Yammer%20groups%20to%20O365%20Connected%20Yammer%20Groups%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-196976%22%20slang%3D%22en-US%22%3E%3CP%3EDo%20I%20have%20to%20create%20an%20Office%20group%20with%20the%20same%20name%20as%20the%20Yammer%20Group%20to%20be%20able%20to%20perform%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-141193%22%20slang%3D%22en-US%22%3ERe%3A%20Converting%20Yammer%20groups%20to%20O365%20Connected%20Yammer%20Groups%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-141193%22%20slang%3D%22en-US%22%3E%3CP%3EAll%20I%20had%20to%20do%20was%20change%20it%20to%20public%20and%20back%20to%20private%20and%20the%20group%20was%20automatically%20converted%20to%20an%20Office%20365%20Connected%20Yammer%20Group.%20Thanks%20for%20sharing%20the%20solution.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-139603%22%20slang%3D%22en-US%22%3ERe%3A%20Converting%20Yammer%20groups%20to%20O365%20Connected%20Yammer%20Groups%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-139603%22%20slang%3D%22en-US%22%3ETry%20this.%3CBR%20%2F%3E%3CBR%20%2F%3EFirst%2C%20make%20sure%20the%20eligible%20user%20you%20added%20as%20an%20admin%20in%20Yammer%20is%20also%20listed%20as%20an%20owner%20for%20the%20underlying%20group%20in%20the%20Office%20365%20admin%20portal.%3CBR%20%2F%3E%3CBR%20%2F%3ESecond%2C%20change%20the%20group%20from%20private%20to%20public%20and%20back%20again%20(or%20vice%20versa).%20We%20had%20a%20case%20where%20MSFT%20advised%20us%20to%20do%20this%20to%20force%20provisioning.%20%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E
Regular Contributor

Hi all,

 

We have only given selected users the permissions to create Office 365 Groups. Creating a Yammer group with an account without this permission results in a normal Yammer group (not an O365 Connected Yammer Group). This is fine, but we do want these groups to be converted to Connected Groups later on. 

 

What I did to test this was added an account with the permissions to create O365 Groups as an admin to the Yammer group. Nothing happened. Logged in with the account that created the group and left it, but still, nothing happened. My assumption was that all Yammer groups will be converted to O365 Connected Yammer groups if they are eligible. I can create connected groups with the account that has the right permissions, but I can't figure out how to convert the normal  Yammer groups. 

12 Replies
best response confirmed by Pooya Obbohat (Regular Contributor)
Solution
Try this.

First, make sure the eligible user you added as an admin in Yammer is also listed as an owner for the underlying group in the Office 365 admin portal.

Second, change the group from private to public and back again (or vice versa). We had a case where MSFT advised us to do this to force provisioning.

All I had to do was change it to public and back to private and the group was automatically converted to an Office 365 Connected Yammer Group. Thanks for sharing the solution. 

Do I have to create an Office group with the same name as the Yammer Group to be able to perform this?

The Office 365 group will be created and linked automatically. All I had to do was change the privacy setting of the Yammer group and set it back to the previous setting. This initiates the provisioning of the O365 group. You do need the following to make this work:

 

- The user doing this should be allowed to create Office 365 groups

- Private Yammer groups are only supported if they are listed in the directory

- O365 connected Yammer groups only work if you have 1 Yammer network 

- O365 connected Yammer groups only work if you have enforced O365 identities

Thank you Pooya for your quick reply.

Unfortunately, this doesn’t seem to make it for me.

If I create a new Yammer-group it is an Office Group with all its capabilities such as SharePoint and OneNote. However, now I would like to convert the old Yammer groups which is very active and with a lot of members to an Office Group enabled Yammer group. The trick worked on a “sandbox” group I have that was private, however, when I try on my public main group it doesn’t work.

Are you switching the privacy setting of the group by using an account with the permission to create Office 365 groups? When you have other O365 connected Yammer groups, this means that you already have a 1-on-1 network-tenant configuration and you are enforcing the O365 identities. The only other requirement for connected Yammer groups is that the account creating the group (or in this case, the account changing the privacy setting to public and back to private & listed in the directory) has the permission to create O365 groups. The only other thing I can think of that could cause this is when you already have an O365 group with the same name. Not sure what will happen then. Changing the privacy setting has worked for me in multiple tenants where only a selected group of people are allowed to create O365 groups. 

Can anyone confirm if this toggling of the privacy setting still works to connect an existing group to an O365 group? I tried it several times today without success.

Thanks,

Brian

Creation of connected groups as stopped working in my own tenant. Have to create a ticket because the network meets all requirements and Office 365 group creation is enabled (tested by creating a Plan). Will report back when that is fixed. Can't test this unfortunately on other networks I have access to. 

Issue was fixed and now I can confirm that toggling of the privacy setting still works. Couple of things you could check:

 

- make sure you have a 1:1 network:tenant configuration. To check, simply go to Yammer admin, start network migration. Is there a network you can merge? if not, then it's 1:1

- make sure O365 identities are enforced 

- make sure that in security settings of Yammer admin portal, connected groups is enabled

- user needs permission to create O365 groups

 

Only public and private & listed groups are supported. 

Thanks @Pooya Obbohat for the follow up info! 

Hi  i have enabled the network settings on our tenant but still shows disabled for the office 365 group creation tenant

when your network has the correct configuration and it still doesn't work, then I would recommend creating a ticket with MSFT support. Have shared the requirements above. Have also noticed that in the security settings for Yammer it might say that connected groups are enabled even if you have multiple Yammer networks. It also won't say "disabled" if users don't have the permissions to create O365 groups. The fact that it shows "disabled" means that something else needs to be fixed and the only thing that I can think of that would result in it being disabled is when you're not enforcing O365 identities.