Follow Us:
As you probably know, Microsoft Teams and Microsoft 365 Groups (e.g., Outlook Groups, Exchange Groups), are intertwined. Microsoft has made many changes to the default settings of these two items in order to minimize confusion. But the defaults aren't always what you need, and Groups/Teams created before the defaults were changed continue to retain the old settings.
Here are a few issues you might encounter if your settings aren't correct:
In this article, we're going to solve all of the problems listed above without having to learn scary PowerShell commands. However, PowerShell commands can still be very helpful if you want to automate this solution, or if you're in a very large organization and you need to apply these settings across many groups at once.
To change the settings for a Group, all you need to do is:
1. Login to the Microsoft 365 administration portal (https://admin.microsoft.com/) with the proper credentials (e.g., Global Administrator).
2. Select "Groups."
3. Click the Group you want to change.
3. Select the "Settings" tab. The settings you see will most likely be different depending on when your Team and Group were created. But here's how each works:
This setting allows people outside of your organization to send an email to the email address assigned to this list, and everyone on the list will get it. Could be a good idea in some cases; then again, do you really want "everyone@mycompany.com" to be open to spam?
Choosing to send copies of group conversations and events to group members is an important setting to consider. Check this box if you want your Group to function as a distribution list. If checked, anything sent to the list appears in user inboxes, including invitations to Teams meetings.
NOTE: When you change this setting, the user preferences for all users of the Group will automatically be updated to "Follow in Inbox - All Email and Events."
For newly created Teams/Groups, "Hide from my Organization's Global Address List" is checked by default, which means that it won't be available to send to as a distribution list. In some cases, this may be great – do you really need a distribution list for the "My Test Team" team? In other cases, you may want to uncheck it – a distribution list for the "HR Team" may be helpful so that anyone in the organization can email it without having to be a member of their Microsoft Team.
The privacy setting reflects your Team and Group privacy. A private group is not visible to others in the organization – you can only view it if you are invited by an owner. Generally, you should leave this setting up to the Team owner.
Unfortunately, this is the missing setting when managing Groups. Historically, whenever you created a Microsoft Team, the matching Group (that must always be created) was visible. Because there was so much potential for miscommunicating important information, Microsoft switched the default to be invisible. For the most part, this is a better behavior, and when combined with the above settings, it probably covers 95% of your needs. But:
Hopefully that will appear as another setting in this same area soon. In the meantime, hold tight for another article in which we will explain how to show/hide your Microsoft 365 Groups.
To learn more about how to properly deploy, govern, and get the most out of Microsoft Teams in your organization, download C5 Insight's free guide:
Download the Microsoft Teams Deployment and Governance Guide
Have questions? Get in touch with us by call our team at 704-895-2500.
The complementary paper includes over 12 years of research, recent survey results, and CRM turnaround success stories.
Request Download
This 60-second assessment is designed to evaluate your organization's collaboration readiness.
Learn how you rank compared to organizations typically in years 1 to 5 of implementation - and which areas to focus on to improve.
This is a sandbox solution which can be activated per site collection to allow you to easily collect feedback from users into a custom Feedback list.
Whether you are upgrading to SharePoint Online, 2010, 2013 or the latest 2016, this checklist contains everything you need to know for a successful transition.