[GH-ISSUE #1772] [Feature Request]: Bulk disable Shared Mailboxes with Enabled Account #937

New issue

Closed

opened 2026-03-02 12:46:26 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 12:46:26 +03:00

Owner

Originally created by @BayonIT on GitHub (Sep 28, 2023).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1772

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.

I see the CIPP can report on Shared Mailboxes with Enabled Account, but I don't see a while to bulk disable all of them at once. I can click on each one, but that is tedious. This would be a handy feature for tenants that first get introduced to CIPP to get to a good baseline. Then we can use CIPP to disable enabled account using the offboarding wizard moving forward to further prevent the problem.

I'm also new to CIPP and maybe there is already a way to do this, but I poked around and didn't see a way.

PowerShell commands you would normally use to achieve above request

No response

Originally created by @BayonIT on GitHub (Sep 28, 2023). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1772 ### 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. I see the CIPP can report on Shared Mailboxes with Enabled Account, but I don't see a while to bulk disable all of them at once. I can click on each one, but that is tedious. This would be a handy feature for tenants that first get introduced to CIPP to get to a good baseline. Then we can use CIPP to disable enabled account using the offboarding wizard moving forward to further prevent the problem. I'm also new to CIPP and maybe there is already a way to do this, but I poked around and didn't see a way. ### PowerShell commands you would normally use to achieve above request _No response_

kerem

2026-03-02 12:46:26 +03:00

closed this issue
added the
enhancement

no-priority
labels

kerem commented

2026-03-02 12:46:27 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 28, 2023):

Thank you for creating a feature request!
Your current priority is set to "No Priority". No Priority Feature requests automatically get closed in two days if a contributor does not accept the FR.

If you are a sponsor you can request an upgrade of priority. To upgrade the priority type "I would like to upgrade the priority".
If you want this feature to be integrated you can always do this yourself by checking out our contributions guide at https://cipp.app/docs/dev/. Contributors to the CIPP project reserve the right to close feature requests at will.
If you'd like this feature request to be assigned to you, please comment "I would like to work on this please!".

@github-actions[bot] commented on GitHub (Sep 28, 2023): Thank you for creating a feature request! Your current priority is set to "No Priority". No Priority Feature requests automatically get closed in two days if a contributor does not accept the FR. If you are a sponsor you can request an upgrade of priority. To upgrade the priority type "I would like to upgrade the priority". If you want this feature to be integrated you can always do this yourself by checking out our contributions guide at https://cipp.app/docs/dev/. Contributors to the CIPP project reserve the right to close feature requests at will. If you'd like this feature request to be assigned to you, please comment "I would like to work on this please!".

kerem commented

2026-03-02 12:46:27 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Sep 28, 2023):

Only sponsors can create FRs

@KelvinTegelaar commented on GitHub (Sep 28, 2023): Only sponsors can create FRs

kerem referenced this issue

2026-03-02 13:56:40 +03:00

[PR #937] [MERGED] Main to dev #3060

kerem referenced this issue

2026-03-02 13:56:41 +03:00