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
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.
If you are about to take a Microsoft Fundamentals exam, or are thinking of taking one in the future, it is perfectly natural to ask questions pertaining to that exam such as 'What is a Microsoft Fundamentals exam actually like?' 'How many questions are there?' 'What can I do to prepare to give myself the best opportunity to pass?' Having taught both the Azure (AZ-900TO1A) and Microsoft 365 (MS-900TO1A) courses several times this year across the UK and Ireland, it may come as little surprise that I get these questions a lot. I am always happy to answer them. I am a firm believer that if we can understand these exams and what we are facing, we are better prepared to go in and give our best performance without any surprises which may negatively impact the end result. This is a collection of FAQ's from those deliveries which I hope can help you go on to achieve the result you need
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.
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.
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.
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.