Teams 203: Protect Teamwork with Governance & Security (Recap)

by | Apr 7, 2020 | Collaboration, Managed Services

Microsoft Teams is a great collaboration platform, but poor governance of data and Team creation can leave your organization exposed. In our experience, by considering what can be done and solid planning, the resultant Teams roll-out will be a better experience for your employees and your organization. By securing your Teams settings and guidance from the outset, you can stay focused, and avoid Team clutter. Microsoft Teams governance and security is designed to keep you on the right track!

Creation

There are three key factors to consider when creating your Teams site. Naming, classification, and guest access. Naming is the process of how you will name various Teams in your network. Common naming conventions are via department type, function, or customer. Next, you have to consider the classification. This includes, not only level of sensitivity but also, who can access the Team, upload files, and remove files. Finally, guest access must be considered. If guest access is allowed, who outside of your organization can access the Team, and who can control that access.

Expiration

Similarly, configuring Teams expiration (automatic deletion of unused Teams to control clutter) consists of three key factors:

  • Expiration Date: how long the team is active or available to members.
  • Data Retention: how long the team is able to be revised or added to.
  • Archive: how long the team will be available on the site.

When building your Teams site, it is important to consider expiration to help control Teams clutter.

Features

Next, when creating your Teams site, you can limit what features are available and to whom. By restricting features available to the tenant, you can control the features available for any new Teams created. This enables administrators to limit the number of apps or add-ins that can be added to your unique site. Then, you must consider how access should be limited by user. By controlling user access, you can restrict application access. This process of limitation will prevent the misuse of applications and add-ins.

Security & Compliance

Finally, when introducing Microsoft Teams to your network, security and compliance standards across Office 365 and other platforms should be taken into account. Areas to consider are eDiscovery, Data Loss Prevention (DLP), Mobile Application Management (MAM), and Multi-Factor Authentication (MFA).

Next Steps

Ready to get started with Microsoft Teams? Reach out to us at info@peters.com or give us a call at 630.832.0075. We can chat about important factors that will shape your Teams experience such as: documentation, planning, and communication.

Download the slide deck here.

Want to catch the entire recording? Click here.

If you’re shot on time, watch the short snippet below: