A retention label may look like a small piece of metadata, but it can determine whether a contract is retained, a clinical record is protected, or redundant content is disposed of on schedule. Knowing how to create Microsoft 365 retention labels is therefore not simply an administrative task. It is the point where your organisation’s retention rules become enforceable across SharePoint, OneDrive, Teams and other Microsoft 365 services.

The configuration itself is straightforward. The harder work is agreeing on what each label means, where it should be used and who is accountable for disposal decisions. A well-designed label structure reduces risk without making day-to-day document management harder for staff.

Start with the retention decision, not the label name

Before opening the Microsoft Purview portal, document the business rule each label will represent. Speak with records management, legal, information security and the business area that owns the content. A label called “Finance - 7 years” is not enough on its own. You need clarity on when the seven-year period starts, whether the content must be retained, whether it is deleted at the end of the period, and whether a person must approve deletion.

For example, an accounts payable invoice may need to be retained for seven years from the end of the financial year. A project working document may only be needed for two years after the project closes. A signed agreement may be retained for its term plus a defined period after expiry. These are materially different rules, even if they all sit in the same SharePoint site.

Keep the first label set focused. Organisations often begin with a large, detailed file plan that employees cannot apply consistently. A smaller set based on genuine record categories is usually more effective, with further detail introduced once adoption is established.

How to create Microsoft 365 retention labels in Purview

Retention labels are managed in the Microsoft Purview portal. Your tenant’s interface may vary slightly as Microsoft updates the portal, but the core process remains consistent. You will need an appropriate role, such as Records Management, Compliance Administrator or a role that has been assigned the required retention management permissions.

Create the label and set its retention period

In Microsoft Purview, go to Records Management and open the File plan section. Select the option to create a new retention label, then provide a clear name and, where useful, a description for administrators and users.

Choose whether the label will retain content, delete content, or do both. In most governed environments, the common pattern is to retain content for a defined period and then trigger a disposal action. Deleting content without a prior retention period can be appropriate for low-value, high-volume information, but it requires care. A deletion rule should never be used as a substitute for understanding business, legal and regulatory obligations.

Next, define when the retention period starts. Microsoft 365 supports several options, including when an item was created, last modified, labelled, or when an event occurs. An event-based trigger is useful where the lifecycle depends on a known business milestone, such as employee termination, contract expiry or project completion. It gives greater accuracy, but it also requires a reliable process to create and apply those events.

If the label is intended for formal records, consider whether users should be able to mark items as records. Declaring a document as a record can restrict editing and deletion, depending on your settings. This is valuable for approved policies, executed agreements and final reports, but can frustrate teams if applied to documents that are still being developed.

Configure disposition review where accountability matters

For labels that delete content after a retention period, decide whether to use disposition review. With this setting, items reaching the end of their retention period are presented to nominated reviewers before permanent disposal. The reviewer can approve disposal, extend retention, or relabel the content where there is a valid reason to keep it.

Disposition review is particularly useful for regulated documents, sensitive operational records and content subject to possible legal or audit requirements. It creates an accountable checkpoint rather than relying on an entirely automated deletion process.

It does, however, create a workload. Assign reviewers who understand the records and establish a process for handling the queue. If nobody is responsible for reviews, expired content will accumulate and the intended disposal programme will stall.

Publish labels to the right people and locations

Creating a label does not make it available to employees. You must publish it through a retention label policy. In Purview, create a policy, select the labels to publish, then choose the users, groups or locations that should receive them.

For SharePoint and OneDrive, publish labels only where they are meaningful. A finance label should not appear in every project site, just as a clinical record label should not be offered to communications teams. A short, relevant label menu helps people choose correctly and improves the quality of reporting later.

Teams needs particular attention because files shared in a channel are stored in the connected SharePoint site, while chat files are generally stored in users’ OneDrive locations. Your policy design needs to account for where content actually resides, not just where users believe they are working.

Allow time for policies to take effect and test with a pilot group before broad release. Microsoft 365 retention settings are powerful and not always immediately visible. Confirm that users can see the intended labels, that the labels can be applied to the right content types, and that the retention behaviour matches the design.

Make label application practical in SharePoint

Users can apply published labels manually through the Microsoft 365 interface, but manual application is only suitable when staff can confidently identify the right record category. If the decision is unclear, labels become inconsistent or are ignored altogether.

For structured SharePoint libraries, default retention labels can reduce this burden. A library that stores board papers, for example, can apply a default label to every item placed there. This approach works well where the library contains one clear record class. It is less suitable for broad team sites with a mix of working documents, templates, meeting notes and final records.

You can also use auto-application methods where content can be identified reliably through metadata, keywords or trainable classifiers. This can be valuable for large document estates, but it should be introduced carefully. Keyword-based rules can misclassify documents, while classifier-based approaches require testing against representative content. Automation should improve consistency, not create a false sense of control.

A practical model often combines methods: default labels for dedicated record libraries, manual labels for mixed business content, and auto-application for high-volume content with predictable characteristics.

Design for search, Copilot and everyday work

Retention labels are part of a wider information architecture. They work best when paired with sensible SharePoint site structures, clear library purposes, managed metadata and ownership responsibilities. A label cannot repair a library where every document type has been placed in one folder with no consistent naming or access model.

This matters even more as organisations prepare content for Microsoft 365 Copilot and other AI-assisted tools. Better-labelled, well-governed information is easier to manage over time. Retention labels do not control permissions, and they do not decide what a user can access, but they support a clearer lifecycle for the information that users can find and work with.

Avoid treating labels as a security classification system. Sensitivity labels and retention labels solve different problems: sensitivity labels help protect content through controls such as encryption and access restrictions, while retention labels manage how long content is kept and what happens at the end of that period. In many environments, a document may require both.

Test the exceptions before rollout

A retention programme should be tested against real scenarios, not only ideal documents. Test a file that is edited after labelling, a file moved between SharePoint locations, a Teams channel document, an item under legal hold, and a document that reaches its disposal date. Check what the user sees, what the records team sees and what appears in audit reporting.

Also test the business exceptions. What happens when a project is extended? How is a document held for an investigation? Can a staff member recognise when a draft becomes a final record? These questions expose the process and training requirements that configuration alone cannot solve.

Document the decisions, label definitions, policy scope and ownership model. This provides a defensible record of how the programme was designed and makes future changes safer. Retention schedules change, business structures change and Microsoft 365 capabilities evolve. Governance needs to be maintained, not configured once and forgotten.

For organisations with complex SharePoint estates or regulated content, an initial pilot is usually the safest path. Start with one high-value document category, prove the lifecycle from creation through to disposition, then extend the model with confidence.