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
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.
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
I am not a hybrid SharePoint expert. In passing this exam, its fair to say that I am still not a hybrid SharePoint expert. Of all the exams I have taken over the course of the last year, this is the one where I have learnt the most. It's also the one I came out the other end having a far greater appreciation of both the technology and the experts who do this on a day to day basis.
I think it's fair to say that a lot of people will do this exam because of Microsoft Teams. Teams is, after all, the fastest growing app in Microsoft history. At the time of writing there are over 500,000 organisations using it. 91% of the Fortune 500. At the time of writing (May 2019) there has been lots of functionality introduced this year or coming in the next few months. It's hard to keep up - even for those administering it every day. Private Teams, Information Barriers, Busy on Busy, Round Robin, App Deployment Policies, Supervision.