Forum Discussion
Tenant wide way to stop new Office365 Groups appearing in Exchange Online GAL
There has been some movement on this topic recently, with plans announced to clean up the clutter created by Groups/Teams in Outlook (https://twitter.com/Anne_Michels/status/971485479798415360). As for cleaning up the GAL, I haven't heard anything, but I would definitely appreciate an option similar to the Mailbox plans we have for regular mailboxes, where we can preconfigure some settings.
I'm getting increasingly frustrated by this myself. I can appreciate the approach to empower users to create their own plans, groups and teams but one size does not fit all.
I can't believe the controls have not been created within the Admin GUI to to disable this by default. We shouldn't need to rely on scheduled Powershell tasks to make these type of amendments.
While we would like users to be able to create their own plans (Hidden from the GAL by default), we do not want Groups and Teams created ad infinitum without some thought behind the process. With this open approach 365 can quickly become a dumping ground for "Test Team" and "Test Group" experiments by end users.
As with a lot of new Microsoft products, its a case of great technology but lack of thought behind the governance of these features.
There has been some movement on this topic recently, with plans announced to clean up the clutter created by Groups/Teams in Outlook (https://twitter.com/Anne_Michels/status/971485479798415360). As for cleaning up the GAL, I haven't heard anything, but I would definitely appreciate an option similar to the Mailbox plans we have for regular mailboxes, where we can preconfigure some settings.
We too feel that the addition of groups to the GAL is creating a mess. We would like Microsoft to address this and prevent items from being shown in the GAL by default (much like they finally changed in Teams).
RSAdmin2315 It looks like this will be a major issue for millions of users worldwide using O365 and Exchange Online. Are there any updates on this or is Microsoft just ignoring the issue for now?
