This is obviously a great option to have – it’s perfect for any content we want to make sure is deleted on a timely basis. In most organisations c. 60-80% of content will likely fall into this category and need to be subject to an automated deletion process.
These are the only two options you have with retention policies. There is no option to review or consider items that need to be transferred to archive – you can merely automatically delete or chose to do nothing. The good news is that retention labels provide far more flexibility!
What options do I have with retention labels?
The first thing to mention is that retention labels also provide both of the same end-of-retention options as retention policies – the only difference is that they provide a wealth of other alternative approaches too. In addition to being able to ‘Do nothing’ or ‘Delete items automatically’, retention labels also let us choose from the following options at the end of retention:
Start a disposition review
At the centre of most of my retention architectures in Microsoft 365, this approach triggers a process that allows content to be reviewed at the end of retention. The idea is that you have an opportunity to appraise some of your more important content to determine its ongoing value and whether it is sent to archive or deleted.
Different retention labels can be associated with different groups of reviewers – something that I’ve used to ensure that content is only sent to the relevant users for assessment. This is invaluable in scenarios where multiple organisations share the same tenant, ensuring that content is reviewed by staff working in the relevant organisation. Before the ability to delegate disposition review was introduced last year it presented a significant gap in the retention story in Microsoft 365.
You can have up to five sequential stages of review, with different reviewers at each stage. However, the disposition review process is very focused on ‘deletion’, with the only way of moving from one stage to another being to mark the item for disposition. I really wish that Microsoft would extend this process further by providing the ability to mark files for transfer to an archive – something that I feel would prove invaluable for many organisations.
One of the major downsides of triggering a disposition review is that it requires E5* licences for all users who can modify content that is subject to a review label – in many (but not all) scenarios this means that all users need a premium licence.
* or Microsoft 365 E5 Compliance/ Microsoft 365 E5/A5 Info Protection & Governance
Change the label
Only introduced a few weeks ago, this capability allows you to chain retention labels together, so when the first reaches the end of retention a different label is automatically applied. This is actually more useful than it might at first appear. For example, you might have files tagged with a standard retention label, which staff can modify for the first few years of their life. When this label reaches the end of its retention period, you could choose to automatically re-classify the content with a record label, making those same files immutable for a further 5 or 10 years.
Any new retention option is more than welcome – and generally, I feel that there will be some scenarios where changing the label is a very useful approach. I do wish that we could conditionally determine which label is applied though – perhaps allowing us to automatically apply one label or another based upon the content’s other metadata – as this would introduce significantly more flexibility.
Run a Power Automate flow
Another option introduced in May this year that I can see is certainly going to see extensive use. This approach allows us to automatically trigger a Power Automate process at the end of an item’s retention period. For those of you who aren’t familiar with Power Automate – it’s Microsoft 365’s workflow solution, which makes it incredibly easy to implement your own dynamic business processes.
Still in preview, Microsoft has introduced a new Power Automate trigger, which will run whenever an item in SharePoint reaches the end of its retention period. Supplementing this are two new workflow actions – the ability to delete items at the end of retention and the ability to move content between SharePoint sites.
Figure 1: Options for Ending Retention in Microsoft 365 – Run a Power Automate Flow
At the moment this workflow solution seems to only function for content in SharePoint – I’d need to test to see what happens when content in other workloads reaches the end of retention (my guess is nothing at the moment – however, I’d be surprised if Microsoft didn’t quickly extend this capability to function wherever a retention label has been applied).
This approach is obviously the most flexible we have to date – effectively we can implement any business process we want at the end of retention. We could automatically send notifications, or tag content, or check metadata, or move files from one location to another.
Now, I’ve not seen it documented, but I’ve been told that this capability requires Power Automate premium licences (if anyone from Microsoft is reading, please let me know!). The problem is, I don’t know how many licences will be needed. If I understand it correctly, it will depend entirely on the ‘value’ that is derived from the process:
“If the flow uses premium connectors and only the owner is getting the value from the flow, since the trigger is an automated trigger, only the owner needs a premium license.”*
*(Source: Frequently asked questions about Power Automate licensing – Power Platform | Microsoft Docs – my emphasis)
But who is getting value from running a process at the end of retention? Is it the records management team who might otherwise need to run a manual process? Or is it everyone in the organisation? The answer is critical – as at £11.30 per user/month, the cost could quickly add up.
One alternative might be to consider a per-flow plan which is currently priced at £4,524 per year for 5 premium flows – which is very likely worth considering.
Webhook on item expiration
I’ll be honest, I was absolutely delighted to see Microsoft provide us with a webhook. This is something I’ve been asking Erica Toelle and Roberto Yglesias to provide in addition to the Power Automate connectors over the past year – and I’m excited by the flexibility and extensibility offered by this approach.
For those of you who aren’t developers, a webhook is effectively a custom trigger, which allows us to attach our own logic and code to it. This means that when an item reaches the end of retention, the webhook will fire and allow us to call into a custom API and invoke any process we’d like to. Without a doubt, this will be my preferred approach for automating the most complex post-retention activities, such as undertaking security reviews and managing transfers to archives.
It’s important to note that this option will not (initially at least) be shown in the UI – if we want to make use of webhooks, we’ll need to set them up with PowerShell: