Comments on: Create Your Own Adaptive Retention Policies with PowerShell and Azure Automation

By: Tony Berni

Tony Berni — Thu, 02 Mar 2023 12:37:56 +0000

Thanks Tony. this might come in handy for our 265 Microsoft F3 accounts.

By: Tony Redmond

Tony Redmond — Tue, 13 Dec 2022 16:52:51 +0000

In reply to Joe. This sounds like it's a good use case for consideration for adaptive scopes. You could have one policy then instead of lots of individual policies broken down into blocks of 1,000 mailboxes. Cost is an issue (E5 licenses) but maybe it can be justified by the saving in maintenance for all those policies?

By: Joe

Joe — Tue, 13 Dec 2022 16:41:47 +0000

Tony – Could you offer your expertise on how to account for a large environment that needs a policy applied to thousands of mailboxes? We developed our own script to dynamically create/assign retention policies in blocks of 1000 mailboxes but always looking for a “better way”! Thanks

By: Tony Redmond

Tony Redmond — Tue, 13 Dec 2022 08:11:52 +0000

In reply to Erica Toelle.

Interesting that the character limit is not documented anywhere (https://learn.microsoft.com/en-us/microsoft-365/compliance/retention-limits?view=o365-worldwide&WT.mc_id=M365-MVP-9501 just mentions the 1,000 mailbox and 100 site/account limit). Given that the average email address is around 30 characters, my guess is that the limit is 32,000, but it would be good to know.

By: Erica Toelle

Erica Toelle — Tue, 13 Dec 2022 04:23:26 +0000

Hey Tony – could you please add a mention for the 1,000 user/100 site include limit on static policies? Also, it’s a character limit, not a hard limit, so keep that in mind for error handling. Thank you!

By: Albert

Albert — Mon, 12 Dec 2022 16:33:28 +0000

Really nice Tony!