The check for sensitivity order should also be done after the creation of a new label. Another post-migration task is therefore to review the list of labels to ensure that the correct order is kept. The order becomes important when a user removes a label or replaces it with another label, because if the new label is of lower sensitivity, label settings might require them to justify this action. You can move labels up or down in the list using commands exposed in the ellipsis menu. The SCC displays labels in order of precedence with the label with the lowest sensitivity at the top of the list and the one with the highest sensitivity at the bottom, and you should take care to create labels in order of sensitivity. These labels were originally called classification labels, but the Office 365 UIs have now been updated to use their new name.įollowing the migration, the original AIP labels and protection templates are still available through the Azure portal, but any work on labels intended for use within Office 365 should be done via Security and Compliance Center (Figure 1).įigure 1: Office 365 Sensitivity Labels (image credit: Tony Redmond) You’ll find two types of labels here: sensitivity and retention, the latter being used to assign retention periods to Office 365 content. Management of sensitivity labels is through the Classifications section of the Security and Compliance Center (SCC). Labels and Security and Compliance Center The most confidential material can be protected using labels that invoke rights management encryption. As you’ll recall, sensitivity labels are how users mark documents and messages with various levels of confidentiality. In part 1 of this mini-series, I described the migration process to transform a set of Azure Information Protection (AIP) labels into Office 365 sensitivity labels.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |