How close is Yammer Office 365 Group Services for Existing Yammer groups?

%3CLINGO-SUB%20id%3D%22lingo-sub-72272%22%20slang%3D%22en-US%22%3EHow%20close%20is%20Yammer%20Office%20365%20Group%20Services%20for%20Existing%20Yammer%20groups%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72272%22%20slang%3D%22en-US%22%3E%3CP%3EWe've%20been%20planning%20for%20this%20event%20which%20is%20still%20in%20development.%20How%20imminent%20is%20it%3F%20How%20will%20roll%20out%20work%3F%20Will%20first%20release%20be%20leveraged%20at%20all%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72500%22%20slang%3D%22en-US%22%3ERe%3A%20How%20close%20is%20Yammer%20Office%20365%20Group%20Services%20for%20Existing%20Yammer%20groups%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72500%22%20slang%3D%22en-US%22%3EWe%20have%20many%20many%20Yammer%20groups%20already%20paired%20with%20SharePoint%20sites%20and%20this%20will%20create%20a%20lot%20of%20duplication.%20We're%20figuring%20out%20which%20old%20sites%20can%20be%20retired%20after%20migrating%20content%20and%20which%20ones%20cannot%20(usually%20because%20they%20require%20custom%20scripting%20or%20other%20features%20in%20legacy%20publishing%20sites).%3CBR%20%2F%3E%3CBR%20%2F%3EI%20do%20think%20many%20Yammer%20based%20teams%20that%20use%20multiple%20groups%20will%20end%20up%20with%20a%20proliferation%20of%20groups%20and%20sites%20they%20don't%20actually%20need.%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72381%22%20slang%3D%22en-US%22%3ERe%3A%20How%20close%20is%20Yammer%20Office%20365%20Group%20Services%20for%20Existing%20Yammer%20groups%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72381%22%20slang%3D%22en-US%22%3EGeoffrey%2C%20I'm%20interested%20in%20what%20your%20plans%20have%20considered%3F%20Are%20you%20concerned%20about%20a%20potentially%20much%20larger%20list%20of%20groups%20people%20will%20be%20exposed%20to%20when%20going%20to%20other%20O365%20workloads%20like%20Planner%20or%20Power%20BI%3F%20Are%20you%20preparing%20messaging%20to%20your%20users%20about%20this%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72370%22%20slang%3D%22en-US%22%3ERe%3A%20How%20close%20is%20Yammer%20Office%20365%20Group%20Services%20for%20Existing%20Yammer%20groups%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72370%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%2C%20I%20guess%20our%20tenant%20hasn't%20been%20enabled%20then%20%3A(%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72361%22%20slang%3D%22en-US%22%3ERe%3A%20How%20close%20is%20Yammer%20Office%20365%20Group%20Services%20for%20Existing%20Yammer%20groups%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72361%22%20slang%3D%22en-US%22%3EHard%20to%20check%20if%20a%20tenant%20is%20included%20in%20the%20rollout%2C%20as%20we're%20going%20as%20fast%20as%20we%20can%20safely%20do%20it%2C%20so%20the%20list%20can%20be%20quite%20dynamic.%3CBR%20%2F%3E%3CBR%20%2F%3EAs%20far%20as%20requirements%2C%20besides%20the%20two%20you%20mention%20there's%20some%20more%20info%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FYammer-and-Office-365-Groups-d8c239dc-a48b-47ab-b85e-6b4b8191a869%22%20target%3D%22_blank%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%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72348%22%20slang%3D%22en-US%22%3ERe%3A%20How%20close%20is%20Yammer%20Office%20365%20Group%20Services%20for%20Existing%20Yammer%20groups%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72348%22%20slang%3D%22en-US%22%3E%3CP%3EHow%20can%20I%20check%20if%20my%20tenant%20is%20included%20in%20this%20rollout%3F%20And%20what%20are%20the%20requirements%2C%20e.g.%20O365%20Groups%20enabled%2C%20Exchange%20mailbox%2C%20etc.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72346%22%20slang%3D%22en-US%22%3ERe%3A%20How%20close%20is%20Yammer%20Office%20365%20Group%20Services%20for%20Existing%20Yammer%20groups%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72346%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20rollout%20happens%20as%20fast%20as%20we%20can%20go%2C%20however%20if%20a%20tenant%20has%20restricted%20creation%20of%20Office%20365%20groups%20we%20will%20not%20be%20automatically%20connecting%20those%20to%20their%20respective%20Yammer%20groups.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72336%22%20slang%3D%22en-US%22%3ERe%3A%20How%20close%20is%20Yammer%20Office%20365%20Group%20Services%20for%20Existing%20Yammer%20groups%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72336%22%20slang%3D%22en-US%22%3EThat's%20great%2C%20we%20will%20keep%20watching%20for%20that.%20I%20was%20not%20sure%20as%20the%20365%20roadmap%20site%20still%20says%20in%20development.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72330%22%20slang%3D%22en-US%22%3ERe%3A%20How%20close%20is%20Yammer%20Office%20365%20Group%20Services%20for%20Existing%20Yammer%20groups%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72330%22%20slang%3D%22en-US%22%3E%3CP%3EGreat%20to%20hear%20it's%20happening%20so%20soon.%20What's%20the%20process%20for%20users%2C%20does%20the%20admin%20have%20to%20tick%20a%20box%20to%20enable%20creation%3F%20We've%20restricted%20creation%20of%20O365%20groups%20in%20our%20tenant%20to%20select%20individuals%20so%20would%20be%20good%20to%20know%20if%20it%20will%20stick%20to%20these%20rules%20or%20%26nbsp%3Bnot.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72303%22%20slang%3D%22en-US%22%3ERe%3A%20How%20close%20is%20Yammer%20Office%20365%20Group%20Services%20for%20Existing%20Yammer%20groups%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72303%22%20slang%3D%22en-US%22%3E%3CP%3EExisting%20Yammer%20groups%20are%20already%20being%20connected%20to%20their%20Office%20365%20counterparts%20under%20a%20controlled%20rollout%2C%20so%20I'd%20say%20it's%20quite%20imminent%20%3B)%3C%2Fimg%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFirst%20release%20is%20not%20being%20used%20for%20this%20rollout.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Super Contributor

We've been planning for this event which is still in development. How imminent is it? How will roll out work? Will first release be leveraged at all?

9 Replies
Highlighted

Existing Yammer groups are already being connected to their Office 365 counterparts under a controlled rollout, so I'd say it's quite imminent ;)

 

First release is not being used for this rollout.

 

Highlighted

Great to hear it's happening so soon. What's the process for users, does the admin have to tick a box to enable creation? We've restricted creation of O365 groups in our tenant to select individuals so would be good to know if it will stick to these rules or  not.

Highlighted
That's great, we will keep watching for that. I was not sure as the 365 roadmap site still says in development.
Highlighted

The rollout happens as fast as we can go, however if a tenant has restricted creation of Office 365 groups we will not be automatically connecting those to their respective Yammer groups.

Highlighted

How can I check if my tenant is included in this rollout? And what are the requirements, e.g. O365 Groups enabled, Exchange mailbox, etc.

Highlighted
Hard to check if a tenant is included in the rollout, as we're going as fast as we can safely do it, so the list can be quite dynamic.

As far as requirements, besides the two you mention there's some more info here: https://support.office.com/en-us/article/Yammer-and-Office-365-Groups-d8c239dc-a48b-47ab-b85e-6b4b81...
Highlighted

Thanks, I guess our tenant hasn't been enabled then :(

Highlighted
Geoffrey, I'm interested in what your plans have considered? Are you concerned about a potentially much larger list of groups people will be exposed to when going to other O365 workloads like Planner or Power BI? Are you preparing messaging to your users about this?
Highlighted
We have many many Yammer groups already paired with SharePoint sites and this will create a lot of duplication. We're figuring out which old sites can be retired after migrating content and which ones cannot (usually because they require custom scripting or other features in legacy publishing sites).

I do think many Yammer based teams that use multiple groups will end up with a proliferation of groups and sites they don't actually need.