Microsoft Records Management Best Practices: Lessons from large scale implementations
Infotechtion has helped some of the world’s largest organizations modernize records management with Microsoft Purview. Microsoft has published case studies covering our Purview records management work at Shell, Equinor, Cummins and the UK Food Standards Agency. While these organizations operate in different industries and regulatory environments, the practical lessons are remarkably consistent.
The answer is not to force employees into a separate records system. Records should be managed where people already work, with Microsoft Purview automating classification, retention and disposition wherever practical.
Microsoft Purview provides the native foundation for managing the lifecycle of records across Microsoft 365. It covers record labels, record declaration, file plans, event-based retention and disposition review. In Microsoft terminology, a record label is a retention label configured to mark content as a record.
The Infotechtion i-ARM solution extends Microsoft Purview with the workflows, automation and oversight needed to run records management at enterprise scale. It helps keep the retention schedule and record labels aligned, involve business owners in governance and disposition, turn findings into tracked actions, and extend consistent governance beyond Microsoft 365, without creating another records repository.
Modernize the Governance Requirements First
Technology will not fix an outdated or overly complicated file plan or records retention schedule.
Many file plans and retention schedules were created for paper records. They assume that people manually place records into folders or boxes and review each item before disposal.
Simply recreating that model in Microsoft Purview can lead to hundreds of labels, confusing choices for employees, unreliable metadata and disposition queues that nobody can realistically complete.
Before implementing a paper-based file plan or records retention schedule, modernize it for digital working:
- Simplify the categories.
- Remove distinctions that do not lead to a different retention outcome.
- Separate detailed legal requirements from the labels shown to employees.
- Identify where automation can replace manual filing.
- Use event-based retention only where metadata and triggers are reliable.
- Reserve manual review for information that genuinely requires judgement.
The point is not to abandon the retention schedule. It is to turn it into a digital control model that people can understand and technology can apply.
Establish Corporate Governance
Global organizations need a common governance model that balances corporate requirements with legal, regulatory and local obligations. A cross-functional governance team should define the principles, approve the retention model, manage regulatory changes and decide where local exceptions are justified.
Use Big-Bucket Categories
A large number of narrow retention categories make classification difficult for both employees and machines. Broader categories such as Administrative Records, Financial Records, HR Records, Legal Records and Project Records provide a more manageable starting point. Each category can become a record label in Microsoft Purview.
The detailed legal authorities can remain in the underlying retention schedule. Employees do not need to see every legal citation if it does not change what they must do.
Minimize Manual Disposition Reviews
Manual review makes sense for selected high-value or historically important records. It does not make sense for every digital item. Reviewing one million records at 15 minutes per record would require 31,250 days of work.
Disposition review should focus on records where a person can add real value. Other categories should use approved automatic disposition rules with suitable oversight and evidence.
Manage Non-Records Too
Working documents, chats, emails, recordings, duplicates and obsolete files also need a lifecycle. Automatic deletion of low-value content can improve search, reduce storage, lower migration volumes and reduce the amount of outdated information available to investigations and AI tools.
Records management should therefore be part of a wider data lifecycle strategy.
i-ARM extends the operating model beyond declared records by helping identify obsolete information, coordinate owner review, track clean-up decisions and archive inactive content where continued retention is justified.
Once the governance model has been simplified and approved, the organization can translate it into record labels, classification rules and lifecycle controls in Microsoft Purview.
Move Beyond Manual Record Labelling
Employees can manually apply record labels to documents and emails. This remains useful when business context or judgement is required.
However, manual labelling alone does not scale. Get started with automation as soon as possible. Content Explorer and Activity Explorer can help organizations understand what has been classified, how labels are being used and where classification is inconsistent.
This supports a gradual path from:
- Manual labeling where business judgment is needed.
- Identification of potential records using metadata, content analysis, classifiers and reporting.
- Automatic record labeling for reliable, tested scenarios.
Automation should be introduced iteratively. Start with a small number of business areas and record types, test the results and improve the rules before expanding the scope.
i-ARM supports the iterative classification approach by bringing governance findings, classification activity and follow-up actions into a common process. This helps records teams move from identifying a classification gap to assigning an owner, testing the response and tracking the agreed action.
Configure Record Labels for the Full Lifecycle
A record label is more than a category name. It marks content as a record and defines when the retention clock starts, how long the record is retained, and what happens when the retention period ends. These choices should be agreed before record labels are configured in Microsoft Purview.
Protect the Record and Preserve Later Versions
When a record label is applied to a file in SharePoint or OneDrive, the file is declared as a record and locked against ordinary changes and deletion during its retention period. This protects the record as evidence and supports the ISO 15489 characteristics of authoritative records: authenticity, reliability, integrity and usability.
Locking a record does not mean that the business can never issue an updated version. Microsoft Purview record versioning supports a controlled unlock-and-lock process. An authorized user can unlock the document, make the required changes and lock it again. When a record is unlocked, Microsoft Purview preserves the previously locked version in the Preservation Hold library. The document can then be edited and locked again to establish the updated version as the current record. Subsequent unlock operations preserve additional record versions.
This makes it possible to create a record series in which each formally locked version is retained as a distinct record. For example, an approved policy or contract can be updated without altering or replacing the first record. The current document remains easy to work with, while the record history shows which versions were formally captured as records.
Record versioning applies to record labels in SharePoint and OneDrive, but not to regulatory record labels, which block editing.
Data-Based Retention Trigger
For straightforward requirements, retention can start from a date already held by Microsoft 365:
- Date created
- Date last modified
- Date the label was applied (most common)
The trigger must match the business requirement. Using the last-modified date for a final record, for example, can move the disposal date if the file is changed later. A label-applied trigger is only dependable when the organization controls when and why the label is applied.
Event-Based Retention Trigger
Some retention periods should begin when a business event occurs rather than when a file was created or labelled. Typical examples include a contract expiring, a project closing, an employee leaving or an asset being decommissioned.
Microsoft Purview links an event-based record label to an event type. The relevant records must then be associated with the specific event. This requires a reliable Asset ID identifier in metadata, such as Contract ID, Project ID or Employee ID. When the event is created, Purview uses that identifier to find the related records and start their retention period.
This creates an important dependency: the identifier must be present, consistent and unique enough to select the correct records. The organization also needs an authoritative source for the event and a dependable process for creating it. If either the metadata or the event process is weak, the retention clock may not start for the right content.
A record with an event-based record label is retained until its event occurs. This can be useful, but it also means that missing events can leave records retained indefinitely. Event-based retention should therefore be reserved for requirements that cannot be met reliably with date-created, date-modified or record-label-applied triggers. i-ARM provides two ways to make this easier to operate.
How i-ARM Supports Event-Based Retention:
- Option 1: Proactive Governance, supports record labels configured for event-based retention without requiring an existing Asset ID. A records manager can open Proactive Governance in the Control Centre, run or create a search, review the results and filter by retention type and event. The records manager can then trigger retention immediately for selected records or all results. For more complex cases, i-ARM can assign an i-ARM-generated Asset ID to selected records. The records manager can return later, search for those Asset IDs and trigger retention when the business event has occurred.
- Option 2: Business Events, planned for the Q2 2027 release, is designed for repeatable events such as an employee leaving. An administrator registers the event type, configures integration with the system that reports the event, defines where i-ARM should look for records and specifies how the related records should be identified.
Decide What Happens at the End of Retention
The end-of-retention action should reflect the value and risk of the record category. Common approaches are:
- Automatic deletion: appropriate for high-volume, low-risk categories where the rule is clear and there is little value in reviewing each item.
- Disposition review: routes eligible items to assigned reviewers before deletion. Use this where business, legal, regulatory or historical judgement is genuinely required.
- Retain without automatic deletion: appropriate where the organization must preserve the content and manage disposal through a separate controlled decision.
- A follow-on label: useful for a staged lifecycle where content moves from one retention phase to another rather than being deleted immediately.
Disposition review should not be the default for every record. At scale, item-by-item review quickly becomes unmanageable. Use automatic deletion for approved repeatable scenarios and reserve review for categories where a person can make a meaningful decision.
i-ARM can turn disposition into a controlled business process by routing reviews to the relevant information owners, supporting approval stages and tracking outstanding actions. This allows the central records team to maintain oversight without becoming the reviewer for every record
Plan the Evidence and Audit Trail
There are two different evidence requirements to consider. The first is the disposition record: evidence of what was disposed of, when it was deleted and who completed or approved the action. The second is the wider Microsoft 365 audit log, which records activities across services. These should not be treated as the same thing.
Microsoft Purview Audit Premium provides one-year default retention for specified workloads and appropriately licensed users. Longer retention, up to ten years, requires additional licensing and configured audit retention policies.
For records kept longer than the available audit period, decide whether the organization needs evidence for the full life of the record and beyond disposal. If so, the operating model should preserve the required disposition metadata, approvals and audit evidence in an appropriate long-term store. This is one area where i-ARM can add value by retaining richer governance and disposition evidence for a customer-defined period. i-ARM can preserve richer disposition metadata, decisions and approval evidence for a customer-defined period. This is useful where the organization needs defensible evidence for the full life of the record or beyond the Microsoft 365 audit-retention period.
Use Metadata Where It Helps
Metadata remains important, but it should not become another manual burden. Standard metadata can be applied when sites, libraries and folders are created. Document-specific values can be entered manually where necessary or extracted from content using SharePoint Premium Autofill.
Every metadata field should have a purpose. It should support search, classification, access, retention, reporting or integration. Do not migrate metadata simply because it existed in the previous system.
Make Records Management Simple for Employees
Employees need straightforward guidance on what should be treated as a record. Examples include:
- Evidence of a business decision
- Executed contracts and formal approvals
- Final deliverables
- Information needed for business continuity
- Information that must be retained by law
Relevant record labels should be made available only in the business locations where they are needed. Adaptive scopes can target record-label policies to the appropriate users, groups and sites, while final-records libraries can apply a default record label. This reduces the number of choices presented to employees and the need to classify every document individually.
It is also important not to apply record controls too early. Active documents may still need to be edited and shared. Apply the record label when the document becomes final or reaches the agreed lifecycle point, rather than declaring it as a record while it is still being developed.
Manage the Change, Not Just the Technology
Records management transformation changes how people create, store, classify and dispose of information. A practical change programme should include:
- A clear vision and success criteria
- Defined roles and responsibilities
- Stakeholder engagement
- Leadership communication
- Role-based training
- A network of champions
- Adoption measures
- Action where adoption is low
Employees do not need training on every detail of the retention schedule. They need to understand what matters in their work and what, if anything, they are expected to do.
Measure Whether Governance Is Working
A records management program needs operational measures, not just confirmation that policies have been configured. Useful measures include:
- Workspaces without owners
- Inactive or public Teams
- Content without a lifecycle
- Sensitive files shared externally
- Records approaching disposition
- Outstanding governance actions
- Use of record labels
- Training and ownership attestations
Every significant finding should have an owner and a defined response. A dashboard has limited value if nobody is responsible for acting on it.
i-ARM is designed to connect reporting with action. Findings such as missing ownership, content without a lifecycle or records approaching disposition can be routed to the relevant business owner and tracked through a defined workflow.
Treat Migration as Redesign, Not File Transfer
Replacing a legacy records system with Microsoft 365 creates an opportunity to manage documents and records where people already work. However, legacy systems may contain deep folder structures, complex metadata rules, virtual folders and links from other applications.
Migration should include simplification, clean-up and redesign. Moving every file and recreating every legacy feature usually carries the old problems into the new platform.
i-ARM can support this work by identifying records, sensitive information, inactive content and potential ROT before migration, and by extending governance to repositories that cannot yet be moved into Microsoft 365.