Teams Real Simple with Pictures: Moderating the Team’s Channels

Some channel conversations necessitate a lot of communication between team members. Others may just generate a significant amount of noise which has no real benefit for the Teams' productivity or which regularly goes off on a tangent from the work. Instead of an open style forum where everyone can post and reply, we may simply want a channel where its owners, or a set number of users such as SME's can post focused messages such as instructions, important content or updates for the team to consume. We may simply want a proportion of the team to observe others conversations. We may simply want it for announcements, or to lock down the channel for bots or connectors such as Twitter and Yammer. Whatever the use case, the moderation of Teams channels is about choice as much as it is about good governance as we now have the ability to have very focused channel communications - a very good thing for us all.

Teams Real Simple with Pictures: Applying Data Loss Prevention (DLP) to Chat, Channel Messages and Files

Data Loss Prevention (DLP) is a strategy for ensuring that team members do not send sensitive or critical information outside of the corporate network or to other team members. This could include financial information, personally identifiable information (PII) such as credit card numbers or information pertaining to Intellectual Property (IP) such as the design for a new application. It could even be extended to use cases such as barring profanity to be used in communications. Whilst Teams is a powerful application for users to be able to communicate and collaborate with guests and with other users in other Teams tenants, organisations also need to protect themselves against data leakage and the infringement of compliance regulations such as GDPR. Applying a DLP Policy to Teams is an essential step in any Teams deployment

Teams Real Simple with Pictures: How are the Team accessing Teams? And from where?

Why would we want to know how the Team accesses Teams and from where? Firstly, it can tell us more about the Team - do they prefer to use their apps online as opposed to the desktop? If they use Teams like this maybe they use Office like this? It may determine the device which is ideal for them in the future. It could help us with licencing too. If they don't use desktop apps then maybe they would be better suited to an F1 licence rather than something like an E3. That's good for our business and its the whole point about Microsoft 365 - it facilitates how users want to work. Secondly, it may be important in terms of security: for example, who is accessing Teams outside of work hours and where? We could be considering a conditional access policy and want to see the typical locations that users are accessing it from before applying it. 

Teams Real Simple with Pictures: Changing the App Bar for the Team with an App Setup Policy

There may be an app your Team frequently uses. For the purpose of this article lets take this app to be Microsoft Flow where the Team is repeatedly adding Flows between apps such as Forms and SharePoint and Twitter and Powerapps across multiple Teams. They could always add Flow as a Tab to a particular Team, but with the increasing amount of Teams this wouldn't make much sense as the Team members would have to remember what Team, or - as is more likely - they are now adding Flow Tabs across multiple Teams which is littering Teams with Tabs which don't necessarily need to be there.

Teams Real Simple with Pictures: Setting up Supervision Policies for the Team

Supervision policies in Microsoft 365 are defined as capturing employee communications for examination by designated reviewers (docs.com). In layman's this means policies can be set up for someone to review team members communications who may be disclosing sensitive information or violating HR policy in the use of profanity, racial slurs, taunts or sexually explicit language in Teams channels and private messages.

Teams Real Simple with Pictures: How to share Code Snippets with the Team

A developer or another member of the Team may want to periodically share snippets for review purposes, to pass on the snippets for use or to articulate as examples of solutions  previously used. However in Teams, these can't be simply cut and pasted into the conversation bar as they do not render correctly. Typing them out is possible but in most cases such as needing to share multiple snippets or a large snippet this is completely impractical and time consuming.