In Part 1, I provided steps to troubleshoot the Legacy Exchange Retention policies, and in this part, Part 2, I delve into Compliance Retention policies. I look at two different scenarios that may im...
Published Feb 27, 2023
Version 1.0
Blog Post
Helpful article, thank you. Some feedback on the product:
It's an awkward feeling when I'm looking at a retention policy with a concerned customer, to find:
- "Last Modified by: Mike | When: <recently>"
and then I have to explain we modified the whole organization's retention policy because one user had a problem with their mailbox, and that "I promise, it's all we changed". It's not a good look. Similarly, even though this issue occurs frequently in large orgs, I wouldn't want to delegate the ability to modify org-wide retention policies to the service desk. If "the business" decides that a retention policy should be set on X date, I want the policy's whenChanged date to forever say whatever that date was. I wish Microsoft created tooling to solve this problem without so quickly directing folks to edit such a serious policy.
The solution is to add an archive, and make sure a tag is working against the problematic folder (as you described in the last post), but this is complicated to explain to the service desk. It would be great if there was a more operational-friendly way to solve this problem. It is also concerning to see my preferred way be called "legacy" now, when the "non-legacy" suggestion is frightening.