Disable Yammer group and Office 365 Yammer connected group creation.

%3CLINGO-SUB%20id%3D%22lingo-sub-201284%22%20slang%3D%22en-US%22%3EDisable%20Yammer%20group%20and%20Office%20365%20Yammer%20connected%20group%20creation.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-201284%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20disabled%20Office%20365%20Group%20creation%20in%20our%20tenant%20and%20control%20this%20via%20an%20internal%20process%20(coded)%26nbsp%3Bwith%20some%20built%20in%20governance.%3C%2FP%3E%3CP%3EI'm%20aware%20that%20doing%20this%20still%20enables%26nbsp%3Bthe%20user%20to%20create%20a%20Yammer%20Group%20via%20the%20UI%20(not%20a%20Office%20365%20Yammer%20connected%26nbsp%3Bgroup)%26nbsp%3Bwish%20gives%20us%20a%20real%20problem%20as%20we%20want%20to%20use%20an%20internal%20process%20to%20create%20these%20as%20Office%20365%20Yammer%20connected%26nbsp%3Bgroups.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20way%20that%20we%26nbsp%3Bcan%20turn%20off%20the%20option%20entirely%20for%20creating%20both%20Yammer%20groups%26nbsp%3Band%20Office%20365%26nbsp%3BYammer%26nbsp%3Bconnected%20groups%20so%20that%20users%20can%20not%20bypass%20our%20internal%20process%20and%20just%20go%20ahead%26nbsp%3Band%26nbsp%3Bcreate%20Yammer%20groups%20via%20the%20UI%26nbsp%3Binstead%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20In%20advance.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-201284%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EYammer%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-203764%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20Yammer%20group%20and%20Office%20365%20Yammer%20connected%20group%20creation.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-203764%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20also%20facing%20the%20same%20challenge.%20Having%20followed%20the%20instructions%20referenced%20by%20Forrest%20at%20%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Fmanage-who-can-create-office-365-groups-4c46c8cb-17d0-44b5-9776-005fced8e618%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Fmanage-who-can-create-office-365-groups-4c46c8cb-17d0-44b5-9776-005fced8e618%3C%2FA%3E%26nbsp%3Bwe%20are%20still%20unable%20to%20block%20O365%20Group%20integrated%20group%20creation%20in%20Yammer.%20We%20have%20created%20a%20security%20group%20in%20Azure%20AD%20using%20the%20above%20instructions.%20Following%20these%20instructions%20seem%20to%20work%20for%20Teams%20and%20allows%20us%20to%20block%20Team%20creation%20and%20also%20for%20Planner%20to%20block%20Plan%20creation.%20This%20structure%20was%20in%20place%2C%20now%20we%20have%20recently%20enabled%20Yammer%20O365%20integration.%20Our%20existing%20architecture%20is%20not%20blocking%20O365%20group%20integration%20in%20Yammer.%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20else%20been%20able%20to%20restrict%20O365%20group%20creation%20coming%20from%20Yammer%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-202315%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20Yammer%20group%20and%20Office%20365%20Yammer%20connected%20group%20creation.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-202315%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20also%20interested%20in%20why%20a%20Yammer%20Group%20can%20be%20created%20when%20the%20directions%20given%20by%20MS%20%3CA%20title%3D%22Manage%20who%20can%20create%20Office%20Groups%22%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Fmanage-who-can-create-office-365-groups-4c46c8cb-17d0-44b5-9776-005fced8e618%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EHere%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eindicate%20that%20it%20will%20block%20Yammer%20too.%26nbsp%3B%20Managing%20all%20these%20different%20API%20and%20Groups%2FSharePoint%20content%20access%20is%20becoming%20overwhelming.%26nbsp%3B%20I%20am%20envisioning%20the%20day%20when%20someone%20gets%20access%20to%20content%20they%20shouldn't.%26nbsp%3B%20In%20My%20opinion%2C%20Office%20365%20Groups%2C%20Teams%2C%20Yammer%2C%20Planner%2C%20SharePoint%20(everything)%20should%20have%20a%20common%20access%20control%20and%20permissions%20management%20UI.%20Not%20the%20convoluted%20morass%20we%20have%20to%20try%20and%20get%20ahold%20of.%3C%2FP%3E%3CP%3E%26nbsp%3BOK%20%2C%20I'll%20try%20and%20relax%20now.%3C%2FP%3E%3CP%3EForrest%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Regular Visitor

Hi,

 

We have disabled Office 365 Group creation in our tenant and control this via an internal process (coded) with some built in governance.

I'm aware that doing this still enables the user to create a Yammer Group via the UI (not a Office 365 Yammer connected group) wish gives us a real problem as we want to use an internal process to create these as Office 365 Yammer connected groups.

 

Is there a way that we can turn off the option entirely for creating both Yammer groups and Office 365 Yammer connected groups so that users can not bypass our internal process and just go ahead and create Yammer groups via the UI instead?

 

Thanks In advance.

 

 

2 Replies
Highlighted

I am also interested in why a Yammer Group can be created when the directions given by MS Here 

indicate that it will block Yammer too.  Managing all these different API and Groups/SharePoint content access is becoming overwhelming.  I am envisioning the day when someone gets access to content they shouldn't.  In My opinion, Office 365 Groups, Teams, Yammer, Planner, SharePoint (everything) should have a common access control and permissions management UI. Not the convoluted morass we have to try and get ahold of.

 OK , I'll try and relax now.

Forrest

Highlighted

We are also facing the same challenge. Having followed the instructions referenced by Forrest at https://support.office.com/en-us/article/manage-who-can-create-office-365-groups-4c46c8cb-17d0-44b5-... we are still unable to block O365 Group integrated group creation in Yammer. We have created a security group in Azure AD using the above instructions. Following these instructions seem to work for Teams and allows us to block Team creation and also for Planner to block Plan creation. This structure was in place, now we have recently enabled Yammer O365 integration. Our existing architecture is not blocking O365 group integration in Yammer. 

Has anyone else been able to restrict O365 group creation coming from Yammer?