Combining retention policies and retention labels

 

You don't have to choose between using retention policies only or retention labels only. Both methods can be used together and in fact, complementary each other for a more comprehensive solution.The following examples are just some of the ways in which you can combine retention policies and retention labels for the same location.For more information about how retention policies and retention labels work together and how to determine their combined outcome, see the section on this page that explains the principles of retention and what takes precedence. For more at Data Retention Policy

Example for users to override automatic deletion

Scenario: By default, content in users' OneDrive accounts is automatically deleted after five years but users must have the option to override this for specific documents.You create and configure a retention policy that automatically deletes content five years after it's last modified, and apply the policy to all OneDrive accounts.You create and configure a retention label that keeps content forever and add this to a label policy that you publish to all OneDrive accounts. You explain to users how to manually apply this label to specific documents that should be excluded from automatic deletion if not modified after five years.

Scenario: By default, SharePoint items are automatically retained and then deleted after five years, but documents in specific libraries must be retained for ten years.You create and configure a retention policy that automatically retains and then deletes content after five years, and apply the policy to all SharePoint and Microsoft 365 Groups instances.You create and configure a retention label that automatically retains content for ten years. You publish this label to SharePoint site admins, so that they can apply it as a default label to be inherited by all items in specific document libraries.Example to delete items in a shorter time period

 

Scenario: By default, emails aren't retained but are automatically deleted after ten years. However, emails related to a specific project that has a prerelease code name must be automatically deleted after one year.You create and configure a retention policy that automatically deletes content after ten years, and apply the policy to all Exchange recipients.You create and configure a retention label that automatically deletes content after one year. Options for applying this label to relevant emails include:You create an auto-labeling policy that identifies content by using the project code name as the keyword, and apply the policy to all Exchange recipientsYou publish the label and instruct users involved in the project how to create an automatic rule in Outlook that applies this labelYou publish the label and instruct users to create a folder in Outlook for all emails related to the project and they apply the published label to the folder, and then create an Outlook rule to move all project-related emails to this folder For more at Data Retention Policy