Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: Retention Policies and holds #3437

Open
gtgamit opened this issue Jan 23, 2025 · 0 comments
Open

[Feature Request]: Retention Policies and holds #3437

gtgamit opened this issue Jan 23, 2025 · 0 comments
Labels
enhancement New feature or request no-priority

Comments

@gtgamit
Copy link

gtgamit commented Jan 23, 2025

Description of the new feature - must be an in-depth explanation of the feature you want, reasoning why, and the added benefits for MSPs as a whole.

We were working on getting some of our client's mailboxes archived using retention policies and found that CIPP does not have a convenient way to review and deploy it. as well as assist in troubleshooting.
Ideally, if possible, under the user exchange settings we would be able to:

  1. Set retention policies and view which one is applied to a mailbox.
  2. See retention hold status for troubleshooting purposes since archiving will not run if the retention hold is active. this can also have a toggle to disable the retention hold but I fear this might be dangerous so I'm fine with no ability to toggle the retention hold but at least see if it's enabled or not.

PowerShell commands you would normally use to achieve above request

Setting retention policies:
Set-RetentionPolicy and Get-RetentionPolicy

Mailbox retention hold status and setting.
Get-Mailbox -Identity example@example.com | fl hold
Set-Mailbox example@example.com -RetentionHoldEnabled $false

@gtgamit gtgamit added enhancement New feature or request no-priority labels Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request no-priority
Projects
None yet
Development

No branches or pull requests

1 participant