Disposition Review does not trigger on Last Modified retention labels in SharePoint Online – is this expected?

Dear @Alex,   

Thank you again for reaching out for the detailed description. You’ve done an excellent job isolating the behavior and I completely understand why this is concerning.  

When retention is meant to reflect true inactivity, any invisible system-driven updates can create a gap between expectation and what the disposition review engine actually evaluates. Your analysis is thoughtful and absolutely valid. 

Based on what you’ve described, it’s very likely that an internal compliance or background SharePoint process is updating the system-level LastModifiedDateTime property (the version used by the Compliance engine), even though the visible SharePoint UI “Modified” column remains unchanged. These background updates are not surfaced to the user but can reset the retention clock, which would match the symptoms you're seeing with a 1‑day policy not progressing to disposition. 

Because these internal signals and service-level operations aren’t exposed in the tenant UI, further validation requires Microsoft’s engineering telemetry. At this point, raising a Microsoft Support ticket is the best next step so they can: 

• Pull the compliance-level modification timestamps used by the retention engine 
• Check if any hidden system processes or label re-evaluations are extending the retention clock 
• Confirm whether your tenant is seeing document-level system updates related to SharePoint, Syntex, search indexing, or compliance processing 
• Verify if your policy configuration is being interpreted as expected by the backend 

This will give you authoritative insight. 

• I sincerely recommend reaching out to your IT administrator to create a support ticket via Microsoft Admin Center > Support > Help & Support for further investigation. 

• Microsoft provides customer service phone numbers based on your region. You can find the appropriate contact number here: Customer service phone numbers - Microsoft Support   

Please note that this is a user-to-user support forum. Moderators and contributors, including external Microsoft employees, cannot directly intervene in Microsoft product features or access back-end systems. Our role is limited to providing technical guidance on reported issues, requests or ideas. 

Thank you for your patience and understanding throughout this process. Should you have any questions or need further assistance, feel free to reach out at any time.

Dear @Alex, 

Welcome to the Q&A Community. 

Thank you for sharing such a clear explanation of your testing scenario. I truly appreciate the effort you put into outlining the details, as it helps provide accurate guidance. 

To clarify, here is how disposition reviews behave when a retention label is configured to start based on Last modified. This setting is supported. However, the retention clock resets every time the item is modified. Consequently, a disposition review will only appear after the item remains unchanged for the full retention period. 

You may find this article helpful for further details: 
RetentionLabel resource type - Microsoft Graph v1.0 | Microsoft Learn 

Because the retention period restarts with each modification, short-duration tests (such as one day) can fail if even minor edits or automated system updates occur, as these push the retention end date forward and prevent the review from being triggered. 

• Why “Created date” worked but “Last modified” didn’t: 

Created date provides a fixed, stable start point. 

Last modified recalculates each time the item changes, so any update during the test window extends the retention period. 

• Does the disposition review engine evaluate the Last Modified date only when the label is applied? 

No. The system always uses the item’s current Last Modified value when determining if retention has ended; it is not a one-time snapshot. 

• Is this a limitation, or is there a reliable configuration? 

This is expected behavior. To reliably test “Last modified,” the item must remain unchanged for the entire retention period. 

In the meantime, you can refer to the following workarounds: 

Option 1: Continue using Last Modified, but stabilize the content 

Use a controlled library with no workflows or automated updates. 

Consider increasing the retention duration (e.g., 3 or 7 days). 

Avoid libraries with versioning, content approval, or metadata enrichment. 

Prevent any system-triggered updates such as: Modified column recalculations, autosave (Office Online), sync client refreshes and retention label reprocessing. 

Option 2: Event‑based retention (for predictable triggers) 

If your retention is tied to a real-world action (e.g., project completion), an event‑based label gives you a precise and reliable start point. 

• Create an event type 

Go to Microsoft Purview > Records management > Event types. 

Select Create event type. 

Give it a name. 

Save it. 

• Create a retention label that uses this event 

Go to Records management > File plan > Create label. 

In retention settings, choose Start retention when an event occurs. 

Select the Event Type you created. 

Set the retention duration. 

Publish the label. 

• Apply the label to your documents 

Open the document library 

Select the file > Details > Choose your retention label. 

(Optional) Fill in the Asset ID column to link that file to a future event 

• Raise the event when it happens 

Go to Records management > Events. 

Select Create event. 

Choose the Event Type. 

Enter the event date and Asset ID(s). 

Create it. 

This action officially starts the retention countdown. 

Option 3: Use Created date or Labeled date 

These options provide fixed retention timelines and work better for frequently updated content. 

Additionally, Microsoft has announced support for retention based on last accessed in OneDrive and SharePoint. If your goal is to manage content based on inactivity, this may be a better long‑term fit once available in your tenant. 

• You can follow the rollout and timing in the Microsoft 365 Roadmap (look for Roadmap ID 472030). 

• If you have admin access, you can also view this information in the Message Center in the Microsoft 365 admin center under ID: MC999442. 

As community moderators, we kindly ask for your understanding that our access to internal development details is limited. Our primary role is to guide users toward the appropriate resources and support channels. While we may not have visibility into performing deeper backend analysis, we’ll continue doing our best to support you within the scope of our responsibilities.  

I hope this information is helpful. Please follow these steps and let me know if it works for you. If not, we can work together to resolve this.    

Thank you for your patience and understanding. If you have any questions or need further assistance, please feel free to share them in the comments on this post so I can continue to support you. 

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have any extra questions about this answer, please click "Comment". 

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.