We have previously explored the implementation of DLP and Supervision policies to the Team. We will now look at applying Sensitivity Labels - currently in Public Preview. By definition, Sensitively Labels allow Teams admins to regulate access to sensitive organizational content created during collaboration within teams. In other words, it can keep Teams private (removing the ability to be set as public) and block Guests from being added. The best thing is that labels can be set at a tenant label and easily applied when creating the Team. It gives administrators so much more control over the Team in terms that users cannot simply join the Team and Owners cannot simply add guests which are not authorised to access it's content. It's another layer of protection which should be added in any Teams roll-out. It's also an answer for blocking guest access on a Team by Team basis: this works well if the creation of Teams are regulated.
I wanted to take the time to thank and acknowledge the many people who have helped me on my journey towards the MVP award. I simply could not have done it without you
In my personal experience, it is not just IT Pro's who want to keep up to date with roadmaps and have an understanding of whats coming to the platforms they manage. Enthusiasts and evangelists are often eager to see new features that they may be able to leverage or rave about to their partners and customers. Support always wants to know what's coming down the pipe in order to prepare for what they see are inevitable issues. Finance loves anything which can lead to greater ROI and save money - and CEO's often like to know they got it right.
We've probably all had it happen to us at some point. The booking for the conference went smoothly. We are on time. The headset is working. Coffee in hand. Good. Good. Then we enter the meeting and start introductions when a synthetic voice plays a few sections later announcing that we have joined the meeting - right over the top of us speaking. A few seconds typically pass after that announcement in awkward silence. In calls with a larger number of speakers jitter is the last thing on ones mind in the opening and closing salvos as the conversation is shot through with these announcements. Good thing there is an easy remedy to this should we choose. It really is surprising how many admins don't realize they have the ability to manage entry and exit announcements and can rectify it within the space of less than 10 minutes.
A set of common links (I.e. https://teams.microsoft.com/start) can be important for a team. Whether to access training, vendor sites, or even files within a channel it democratizes access to information, makes information more readily available and brings it to the users instead of them having to search for it. Yet with Teams there are different ways to create sets of links and each way has it's own pro's and con's. At the time of writing there is no single accepted way which has been recognized by the Tech Community as the best - so its a case of choosing which one is right for the Team. This will show you four potential methods to create a set of links.
With Teams, we have a number of things we can do to keep our Team up to date. This includes group chats, conversations in channels, meetings, notifications, mentions, and adding content to the Wiki. Another way is by leveraging what are called connectors to deliver content from apps such as Twitter and Yammer into the conversation tab of the Team channel. Twitter, for example, is used by millions for posting and interacting with messages. Yammer is an enterprise social networking service for broadcasting one to many communications within the business. Both are places users and organisations post news and status updates first. Now, the benefit of setting up connectors to Twitter and Yammer is that members of the Team no longer have to scour them and jump around between all these different Twitter pages and Yammer groups to get the updates they need - we can simply bring them all into a feed! A great time saver.
Document collaboration and co-authoring (when we work at the same time) is one of the core functionalities of Teams. We have the ability to do this seamlessly whether it is our Word Documents, or Excel Spreadsheets, or PowerPoint presentations, knowing that they are stored in a single place and are accessible from anywhere on any device. However, there may be times where there is a single owner for the Teams documents or we simply need to create documents for viewing purposes only, limiting other members of our team from making changes. Controlling documents in channels and who can edit them is very straightforward, and many issues resulting from unauthorized changes can be easily prevented