Use this topic if you're using classification labels as part of your GDPR protection plan.
-->
If you're using labels for protection of personal data in Office 365, Microsoft recommends you start with retention labels. With retention labels, you can:
Jul 26, 2013 Download, email, edit and share these manuals with your friends and colleagues. They’re yours now, enjoy. Our free manuals page is updated regularly with the latest training aids, so be sure to check back regularly for new guides. Visit the free Microsoft Office Training Manuals page. Sep 28, 2015 Read more From new Microsoft Teams experiences to the all-new Project Cortex—here’s what’s coming soon to Microsoft 365 Get started with Microsoft 365 Microsoft 365 brings together Office 365, Windows 10, and Enterprise Mobility + Security.
Cloud App Security doesn't currently support retention labels, but you can use Office 365 sensitive information types with Cloud App Security to monitor personal data that resides in other SaaS apps.
Sensitivity labels are currently recommended for applying labels to files on premises and in other cloud services and providers. These are also recommended for files in Office 365 that require Azure Information Protection encryption for data protection, such as trade secret files.
At this time, using Azure Information Protection to apply encryption is not recommended for files in Office 365 with data that is subject to the GDPR. Office 365 services currently cannot read into AIP-encrypted files. Therefore, the service can’t find sensitive data in these files.
Retention labels can be applied to mail in Exchange Online and these labels work with Office 365 data loss prevention.
In the illustration:
Use retention labels and sensitive information types across Microsoft 365 for information protection
The following illustration shows how retention labels and sensitive information types can be used in label policies, data loss prevention policies, and with Cloud App Security policies.
For accessibility, the following table provides the same examples in the illustration.
Prioritize auto-apply label policies
For personal data that is subject to GDPR, Microsoft recommends auto-applying labels by using the sensitive information types you curated for your environment. It is important that auto-apply label policies are well designed and tested to ensure the intended behavior occurs.
The order that auto-apply policies are created and whether users are also applying these labels affect the result. So, it's important to carefully plan the roll-out. Here’s what you need to know.
One label at a time
You can only assign one label to a document.
Older auto-apply policies win
If there are multiple rules that assign an auto-apply label and content meets the conditions of multiple rules, the label for the oldest rule is assigned. For this reason, it's important to plan the label policies carefully before configuring them. If an organization requires a change to the priority of the label policies, they'll need to delete and recreate them.
Manual user-applied labels trump auto-applied labels
Manual user applied labels trump auto-applied labels. Auto-apply policies can't replace a label that is already applied by a user. Users can replace labels that are auto-applied.
Auto-assigned labels can be updated
Auto-assigned labels can be updated by either newer label policies or by updates to existing policies.
![]()
Be sure your plan for implementing labels includes:
Example priority for creating the auto-apply policies
Create labels and auto-apply label policies
Create labels and policies in the security center or the compliance center.
The following illustration shows how to create an auto-apply label for the Customer data label.
Microsoft Office 365 Personal User Manual Download
In the illustration:
Microsoft Office 365 Personal Uk
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2020
Categories |