starred/CIPP

Fork 0

mirror of https://github.com/KelvinTegelaar/CIPP.git synced 2026-04-25 08:16:01 +03:00

[GH-ISSUE #928] FEATURE REQUEST: Litigation Hold #485

New issue

Closed

opened 2026-03-02 12:42:37 +03:00 by kerem · 5 comments

kerem commented

2026-03-02 12:42:37 +03:00

Owner

Originally created by @nc-azure on GitHub (May 19, 2022).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/928

Originally assigned to: @AdamWillford on GitHub.

Hi Kelvin,

I love what you have done with CIPP, awesome product.

Would it be possible to add a feature to enable Litigation on mailboxes?

Examples:

This would be the command to enable litigation hold on all mailboxes on a tenant:

Get-Mailbox -ResultSize Unlimited | Set-Mailbox -LitigationHoldEnabled $true

This would be a command to report on which mailboxes have Litigation Hold enabled:

get-mailbox | where-object {$_.litigationholdenabled -eq $true} | fl name

Originally created by @nc-azure on GitHub (May 19, 2022). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/928 Originally assigned to: @AdamWillford on GitHub. Hi Kelvin, I love what you have done with CIPP, awesome product. Would it be possible to add a feature to enable Litigation on mailboxes? Examples: This would be the command to enable litigation hold on all mailboxes on a tenant: Get-Mailbox -ResultSize Unlimited | Set-Mailbox -LitigationHoldEnabled $true This would be a command to report on which mailboxes have Litigation Hold enabled: get-mailbox | where-object {$_.litigationholdenabled -eq $true} | fl name

kerem

2026-03-02 12:42:37 +03:00

closed this issue
added the
enhancement

no-priority
labels

kerem commented

2026-03-02 12:42:38 +03:00

Author

Owner

@AdamWillford commented on GitHub (May 19, 2022):

I would like to work on this please!

@AdamWillford commented on GitHub (May 19, 2022): I would like to work on this please!

kerem commented

2026-03-02 12:42:38 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (May 19, 2022):

Great! I assigned you (@AdamWillford) to the issue. Have fun working on it!

@github-actions[bot] commented on GitHub (May 19, 2022): Great! I assigned you (@AdamWillford) to the issue. Have fun working on it!

kerem commented

2026-03-02 12:42:38 +03:00

Author

Owner

@nc-azure commented on GitHub (May 19, 2022):

Awesome, thank you Adam :)

@nc-azure commented on GitHub (May 19, 2022): Awesome, thank you Adam :)

kerem commented

2026-03-02 12:42:38 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (May 20, 2022):

Not going to implement this; Microsoft no longer recommends using this, but use DLP policies instead: https://docs.microsoft.com/en-us/exchange/security-and-compliance/in-place-and-litigation-holds

@KelvinTegelaar commented on GitHub (May 20, 2022): Not going to implement this; Microsoft no longer recommends using this, but use DLP policies instead: https://docs.microsoft.com/en-us/exchange/security-and-compliance/in-place-and-litigation-holds

kerem commented

2026-03-02 12:42:38 +03:00

Author

Owner

@nc-azure commented on GitHub (May 23, 2022):

Hi Kelvin,

Reading that article and then clicking on the second article from that page, it doesn't seem to be referencing Litigation Hold being removed, but more the On-Hold feature being removed.

https://docs.microsoft.com/en-us/microsoft-365/compliance/legacy-ediscovery-retirement?view=o365-worldwide

It is still your call at the end of the day, but I thought I would try get some more clarity on this :)

Thanking you in advance

@nc-azure commented on GitHub (May 23, 2022): Hi Kelvin, Reading that article and then clicking on the second article from that page, it doesn't seem to be referencing Litigation Hold being removed, but more the On-Hold feature being removed. https://docs.microsoft.com/en-us/microsoft-365/compliance/legacy-ediscovery-retirement?view=o365-worldwide It is still your call at the end of the day, but I thought I would try get some more clarity on this :) Thanking you in advance

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/CIPP#485

No description provided.

Rows
Columns