These recommendations are based on Microsoft’s experience working with many customers and real-world use-cases and have proven to be the most successful for end-user adoption and understanding. To come up with an organization’s labels, IT should work closely with the Information Management (IM) team. Adhering to Microsoft’s label recommendations is a sound approach and you should only deviate from it if there is a very good reason to do so. #1 – Keep labels simple, unambiguous and obvious What are some strategies you can use to keep your AIP deployment simple? Read on. The labels are stored in clear text as either metadata in files (you’ll see the label as a sensitivity property in Advanced properties) or in email headers to allow other services (DLP, custom solutions, etc.) to identify the classification and take appropriate action. In AIP, you use labels to apply classification to documents and emails. Microsoft Azure Information Protection team Enable intuitive, non-intrusive experience for end-users.Protect data using encryption, authentication and use rights.Classify data based on sensitivity, and add labels – manually or automatically.What is Azure Information Protection (AIP)? It lets organizations classify, label, and protect data at the time of creation or modification. With AIP, users can: Get too complicated and your users will hate the control “IT” is forcing upon them and will look to other tools to “get the job done”.
Have you been tasked with implementing Azure Information Protection (AIP) in your organization? If the KISS principle ever applied to anything in the O365 service, it definitely applies to the AIP world of classification and labeling.
0 kommentar(er)
