Purview Lifecycle Management: Retention by Last Access Date

Is your organization struggling to manage aging files in OneDrive or SharePoint? Microsoft Purview has introduced a significant enhancement to Data Lifecycle Management (DLM): retention policies based on the “last accessed” date. This new feature—announced in February 2025 update—gives administrators more granular control over unstructured data, enabling smarter compliance strategies and improved data hygiene.

Let’s explore what this update brings, how it works, and how you can take advantage of it.

Why Data Lifecycle Management Matters

In modern digital workplaces, data volume grows exponentially – often beyond what’s necessary or secure. Effective Data Lifecycle Management ensures content is preserved only as long as required, protecting sensitive information, minimizing risk, and optimizing storage costs.

Microsoft Purview is the unified solution for DLM across Microsoft 365 services. Its retention policies allow businesses to automatically retain or delete content. Based on metadata like creation date, modification date, and now—thanks to the February 2025 update—last accessed date.

This new condition addresses a gap in legacy retention models, which couldn’t distinguish between actively used and stale content unless modified.

What’s New: Retention Based on Last Access Date

The update enables admins to define retention rules for OneDrive and SharePoint files using the “last accessed” date. This gives organizations the ability to:

• Identify content that hasn’t been used in a specified time frame
• Trigger deletion or archival actions
• Meet compliance standards with reduced storage footprints

Previously, retention decisions could only rely on “created” or “last modified” metadata. But many files—like reference documents, policy PDFs, or old project folders—can remain unmodified for years while still being occasionally accessed. The new “last accessed” condition offers a more accurate picture of content relevance.

Absolutely! Here’s the updated blog section with extended explanations (each point is now around 50 words) for headings 3, 4, 5, 6, and 7.

Key Use Cases for Admins

1. Clean Up Dormant User Data
   Many OneDrive accounts contain old personal files that are no longer used. By applying “last accessed” retention rules, admins can automatically delete files that haven’t been opened in, say, two years—helping free up valuable cloud storage without relying on users to manually clean their folders.
2. Optimize Long-Term Retention
   SharePoint document libraries with thousands of items often store outdated records. This feature lets you identify those untouched for years and archive them to low-cost storage, such as Microsoft Syntex Archive, ensuring long-term retention while keeping active environments lean and responsive for end users.
3. Secure Legacy Content
   Sensitive content from former employees or past projects can pose data leakage risks if left unattended. With last accessed-based retention, such files can be deleted or locked automatically when they remain untouched, helping IT teams implement zero-trust policies and reduce the chance of accidental exposure or misuse.
4. Support Legal Holds and Audits
   Retention by last accessed date helps legal and compliance teams retain only necessary documents. During audits or litigation holds, active records can be preserved based on access logs, while old, irrelevant documents can be safely discarded, streamlining the discovery process and minimizing the scope of regulatory risks.
5. Enable Tiered Storage Strategies
   Admins can now create policies that distinguish between frequently used files and dormant data. Active content stays in SharePoint or OneDrive, while unused files are redirected to cheaper storage tiers. This tiered approach improves cost-efficiency, aligns with data value, and supports hybrid cloud or backup solutions.

How the “Last Accessed” Retention Works

1. Create or Edit a Retention Policy
   Admins can navigate to Microsoft Purview’s Compliance Portal to create or modify retention policies. This intuitive interface allows selection of storage locations, rules, and content types. The new update introduces “last accessed” as a condition—enhancing how retention is triggered for OneDrive and SharePoint files.
2. Choose a Location
   This feature currently supports OneDrive and SharePoint Online. Admins must select one or both of these as the scope for their retention policy. Microsoft may expand this to other services like Teams and Exchange in future updates, but for now, it is focused on collaboration content storage.
3. Set the Retention Condition
   In the policy configuration, you can choose “when items were last accessed” as the trigger. This ensures that retention actions—such as deletion or archival—are based on real user interaction, rather than creation or modification timestamps which may not reflect actual content usage or relevance.
4. Define the Duration
   You can specify a time threshold, such as “delete files not accessed in 365 days.” This flexibility allows policies to align with corporate governance frameworks, departmental needs, or industry regulations—ensuring your data retention practices are both automated and legally defensible across different content scenarios.
5. Apply and Monitor
   Once configured, policies take effect across the selected scope. Admins can monitor enforcement using Microsoft Purview’s activity logs or Content Explorer. This visibility allows teams to audit retention activity, troubleshoot unexpected deletions, and refine retention logic for better accuracy and policy tuning.

Looking for SharePoint Consulting services? Let us know!

Benefits of Last Access-Based Retention

1. Better Data Hygiene
   Files that haven’t been accessed in years are often irrelevant, outdated, or abandoned. This new retention method enables organizations to automatically identify and remove such files—reducing clutter, enhancing user experience, and maintaining cleaner, more navigable data environments across Microsoft 365.
2. Reduced Storage Costs
   Microsoft 365 storage can become expensive when unmanaged. By targeting files that haven’t been used for a long time, companies can save on licensing and storage costs. Archiving or deleting unused files helps reduce resource waste and may delay or eliminate the need to purchase additional storage.
3. Enhanced Compliance Alignment
   Retention based on last access ensures that only actively used files are kept, while older ones are automatically disposed of after a set duration. This aligns closely with compliance mandates requiring businesses to minimize unnecessary data retention, especially under privacy laws like GDPR and HIPAA.
4. Smarter Security Posture
   Inactive files left unmonitored often become security liabilities. Removing or locking down unaccessed data reduces exposure to threats like ransomware, unauthorized access, or insider misuse. This feature supports a zero-trust security framework by ensuring stale content doesn’t linger longer than necessary.
5. More Insightful Governance
   Combining last accessed retention with analytics provides deeper insights into organizational data habits. Teams can better understand which content types are actively used, justify retention timelines with data, and continuously improve lifecycle governance strategies. Based on actual behavior, not assumptions or static metadata.

Limitations and Considerations

1. Only for OneDrive and SharePoint
   At this stage, the “last accessed” retention condition only supports OneDrive and SharePoint. While these are major repositories for file storage, admins managing other workloads—like Exchange Online or Teams—will need to continue using traditional retention models until broader support is rolled out.
2. Dependent on Activity Signals
   This feature relies on accurate file access data captured via Microsoft 365 audit logs. If your organization disables audit logging, or users access files through external apps or legacy sync tools, access events may not be recorded consistently—leading to gaps in policy enforcement.
3. May Require Licensing
   Access to this feature may be limited to certain Microsoft 365 plans, such as E5 Compliance or Microsoft Purview add-ons. Organizations on lower-tier subscriptions might need to upgrade or purchase additional licenses to use “last accessed” retention conditions within their compliance center.
4. User Behavior May Affect Accuracy
   File access is counted when a document is opened—not when viewed in previews or through quick glances. So, some content that appears unused could still be relevant to users. Admins should balance automation with thoughtful policy durations to avoid unintended content loss.
5. Cannot Replace All Retention Models
   While powerful, this model should complement—not replace—other retention strategies like classification-based policies or event-based retention (e.g., based on project closure). Organizations must still combine various rules to build a robust and compliant data lifecycle framework that serves all content types and use cases.

Implementation Best Practices

1. Start with a Pilot Policy
   Test the feature on a limited user group or document library before rolling it out company-wide. Monitor results for 30–90 days. This approach ensures policy behavior aligns with expectations and provides a safety net to fine-tune logic before full-scale deployment.
2. Audit Your Data Landscape
   Use Microsoft Purview’s Content Explorer and Audit Log Search to understand data usage patterns across OneDrive and SharePoint. This helps you target the right libraries, users, or departments where access-based retention can have the biggest impact on reducing clutter or enforcing compliance.
3. Combine with Syntex Archive
   For content that needs to be retained but not frequently accessed, consider moving it to Microsoft Syntex Archive instead of deleting it. This approach supports long-term records management and compliance needs, while also lowering the cost of retaining large volumes of inactive content.
4. Inform Users
   Let employees know about the new retention model and its implications. Clearly explain that unaccessed files may be deleted or moved—even if they haven’t been edited recently. This improves adoption, reduces surprises, and encourages users to engage with content they want to preserve.
5. Document Your Retention Strategy
   Maintain written policies that describe your retention logic, including the use of “last accessed” conditions. This documentation supports internal governance, facilitates audits, and serves as proof of compliance for regulatory reviews or industry certifications like ISO 27001 or SOC 2.

Looking Ahead: A Smarter Future for Records Management

Microsoft’s move to support retention based on “last accessed” signals a broader shift in adaptive data governance. As machine learning, Syntex AI, and Microsoft Copilot continue to evolve, retention decisions will become even more dynamic—perhaps even automated based on content sensitivity, usage patterns, and employee roles.

For now, this feature marks a major leap forward in helping organizations reclaim control over data sprawl without compromising compliance.

By combining this feature with other Microsoft Purview capabilities—like retention labels, records management, and audit logging—you can design an end-to-end data lifecycle framework that’s both cost-effective and defensible.

Final Thoughts

The addition of retention policies based on the “last accessed” date empowers organizations to align data governance with actual content usage. This enhances not only compliance but also operational efficiency.

Whether you’re managing sprawling SharePoint libraries, dormant OneDrive accounts, or planning a structured data cleanup project—this update is a must-have in your toolkit.

As enterprise data continues to grow, automated lifecycle management isn’t just a convenience-it’s a necessity.