Today's top stories

Security and compliance considerations for Microsoft Teams

Admins will need to make these decisions around security and governance when porting from Office 365 Pro Plus to Microsoft Teams.

Office 365 Pro Plus users were recently upgraded from Skype for Business to Microsoft Teams, joining some 13 million users of Microsoft’s new collaboration platform. Teams can provide a great deal of productivity and communication, but it can also introduce security and compliance issues. Take the time to plan and you can build in security and compliance from the initial roll-out.

If you are deploying Office 365 Pro Plus, you need to do some security and governance framework tweaks for Teams Those currently using Skype for Business will need to plan on governance and security decisions surrounding Teams as you face a deadline to upgrade by July 31, 2021.

Tracking and logging options

Like many other Office 365 products, the options you have for tracking and logging depends on your license. Unless you have a Azure AD P1 or Azure AD P2 license, you won’t be able to set some guidelines on Microsoft Teams that may have impacts relevant to human resources. This includes actions such as setting rules for team and channel naming, setting policies of naming including rules that set prefixes or suffixes, and custom blocked words that allow you to block any potentially harmful or dangerous words inside your organization.

To continue reading this article register now

Get the best of CSO ... delivered. Sign up for our FREE email newsletters!