A unified data governance solution that helps manage, protect, and discover data across your organization
The behavior described is consistent with how retention labels are applied and enforced and with known “File not found” patterns when the underlying location or container does not yet exist.
When a folder is being created in SharePoint, the item (the folder object) does not fully exist until the creation operation completes. Retention labels are enforced by policies that must be able to resolve a real location/container. If the label is applied as part of the same “new item” operation before the folder is actually committed, the system can effectively be trying to bind the label to a location that is not yet available, which results in a “File not found”–type error.
Supported and reliable sequence for applying a retention label to a folder in a SharePoint document library is:
- Create and save the folder first (so the folder exists as an item in the library).
- After the folder is created, select it and use the Details pane (or equivalent UI) to apply the retention label.
This aligns with how Microsoft Purview retention and retention label policies work: policies and labels are enforced only after the target location exists and has successfully synced and been processed. Errors in policy distribution or in resolving locations are a known class of issues; Microsoft Purview does not support policies that contain such errors and requires them to be resolved before enforcement works as intended.
If the error persists even when applying the label after the folder exists, the next step is to check for retention/label policy errors in Microsoft Purview and resolve any reported issues before retrying.
References:
- Apply a retention label to a document processing model
- Publish retention labels and apply them in apps
- Automatically apply a retention label to retain or delete content
- Identify errors in Microsoft 365 retention and retention label policies
- Resolve errors in Microsoft 365 retention and retention label policies
- Known issues with document management