starred/CIPP

Fork 0

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

[GH-ISSUE #1929] [Feature Request]: Multi-Select for Forward Email to Another User in Offboarding Wizard #999

New issue

Closed

opened 2026-03-02 13:40:44 +03:00 by kerem · 3 comments

kerem commented

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

Owner

Originally created by @JRivett-ITSG on GitHub (Nov 30, 2023).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1929

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.

Previously requested allowing multiple automapping for full access to mailbox and One Drive, also would like it in "forward email to other user".

Contributor status is on https://github.com/ITSupportGuys, not this account, I cannot submit requests as the org.

This would make all offboardings faster, as we wouldn't have to manually make the transport rule.

We could use a transport rule to do this, as it looks like you only have the option to forward to a single recipient when using forwarding at the user level. Maybe we could add a switch to forward as a transport rule.

PowerShell commands you would normally use to achieve above request

New-TransportRule -name TestPwshForward -RecipientAddressMatchesPatterns email@email.com -BlindCopyTo address1,address2

Originally created by @JRivett-ITSG on GitHub (Nov 30, 2023). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1929 ### 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. Previously requested allowing multiple automapping for full access to mailbox and One Drive, also would like it in "forward email to other user". Contributor status is on https://github.com/ITSupportGuys, not this account, I cannot submit requests as the org. This would make all offboardings faster, as we wouldn't have to manually make the transport rule. We could use a transport rule to do this, as it looks like you only have the option to forward to a single recipient when using forwarding at the user level. Maybe we could add a switch to forward as a transport rule. ### PowerShell commands you would normally use to achieve above request New-TransportRule -name TestPwshForward -RecipientAddressMatchesPatterns email@email.com -BlindCopyTo address1,address2

kerem

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

closed this issue
added the
enhancement

Planned
labels

kerem commented

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

Author

Owner

@KelvinTegelaar commented on GitHub (Dec 1, 2023):

Planned.

@KelvinTegelaar commented on GitHub (Dec 1, 2023): Planned.

kerem commented

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

Author

Owner

@KelvinTegelaar commented on GitHub (Dec 5, 2023):

You can only set one address as a forwarding address in exchange, however we now show the option to forward to mailing lists/dls as well.

@KelvinTegelaar commented on GitHub (Dec 5, 2023): You can only set one address as a forwarding address in exchange, however we now show the option to forward to mailing lists/dls as well.

kerem commented

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

Author

Owner

@JRivett-ITSG commented on GitHub (Feb 6, 2024):

You can only set one address as a forwarding address in exchange, however we now show the option to forward to mailing lists/dls as well.

Right which is why I suggested a switch to convert the forwarding within CIPP to a transport rule forward. Something like this:
New-TransportRule -name TestPwshForward -RecipientAddressMatchesPatterns email@email.com -BlindCopyTo address1,address2

@JRivett-ITSG commented on GitHub (Feb 6, 2024): > You can only set one address as a forwarding address in exchange, however we now show the option to forward to mailing lists/dls as well. Right which is why I suggested a switch to convert the forwarding within CIPP to a transport rule forward. Something like this: New-TransportRule -name TestPwshForward -RecipientAddressMatchesPatterns email@email.com -BlindCopyTo address1,address2

kerem referenced this issue

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

[PR #999] [MERGED] Dev to release #3087

kerem referenced this issue

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

[PR #1071] [CLOSED] Update package-lock.json #3115

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#999

No description provided.

Rows
Columns