[GH-ISSUE #3702] [Feature Request]: Add option to remove all Forwarding addresses from User in Offboarding Wizard

kerem commented

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

Owner

Originally created by @patrick-synium on GitHub (Feb 26, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3702

Originally assigned to: @kris6673 on GitHub.

Please confirm:

I have searched existing feature requests (open and closed) and found no duplicates.
**me or my organization is currently an active sponsor of the product at the $99,- level.

Problem Statement

When using the Offboarding Wizard, there's currently no option to automatically remove any forwards set on a user account. We currently have to check the user record for forwards and remove them separately.

Scenario - If a user moves to a competitor, we have known some users add a forwarder to their account, which would be unauthorised when the user is offboarded.

Benefits for MSPs

Adding this feature would save MSPs time each time a user is offboarded - can complete the complete task from Offboarding Wizard tool, rather than having to check another area to ensure all forwards have been removed for the offboarded user.

Improves customer data security by preventing external/unauthorised access to offboarded user's email.

Competitor Tools to CIPP, used by MSPs - already have this feature added.

Value or Importance

It's not critical, as we can always run reports on accounts with forwards, or check an individual account, but would be "nice-to-have" as it would save valuable time, and is often configured at the time that user's are offboarded.

PowerShell Commands (Optional)

Get-Mailbox -ResultSize Unlimited | Where-Object { $.ForwardingAddress -ne $null -or $.ForwardingSmtpAddress -ne $null } | ForEach-Object {
Set-Mailbox -Identity $_.Identity -ForwardingAddress $null -ForwardingSmtpAddress $null
}

Originally created by @patrick-synium on GitHub (Feb 26, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3702 Originally assigned to: @kris6673 on GitHub. ### Please confirm: - [x] **I have searched existing feature requests** (open and closed) and found no duplicates. - [x] **me or my organization is currently an active sponsor of the product at the $99,- level. ### Problem Statement When using the Offboarding Wizard, there's currently no option to automatically remove any forwards set on a user account. We currently have to check the user record for forwards and remove them separately. Scenario - If a user moves to a competitor, we have known some users add a forwarder to their account, which would be unauthorised when the user is offboarded. ### Benefits for MSPs Adding this feature would save MSPs time each time a user is offboarded - can complete the complete task from Offboarding Wizard tool, rather than having to check another area to ensure all forwards have been removed for the offboarded user. Improves customer data security by preventing external/unauthorised access to offboarded user's email. Competitor Tools to CIPP, used by MSPs - already have this feature added. ### Value or Importance It's not critical, as we can always run reports on accounts with forwards, or check an individual account, but would be "nice-to-have" as it would save valuable time, and is often configured at the time that user's are offboarded. ### PowerShell Commands (Optional) Get-Mailbox -ResultSize Unlimited | Where-Object { $_.ForwardingAddress -ne $null -or $_.ForwardingSmtpAddress -ne $null } | ForEach-Object { Set-Mailbox -Identity $_.Identity -ForwardingAddress $null -ForwardingSmtpAddress $null }

kerem

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

closed this issue
added the
enhancement

no-priority
labels

kerem commented

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

Author

Owner

@deadshotdann commented on GitHub (Feb 26, 2025):

This would be a useful time save. I often have to manually go into the mailbox after running a CIPP offboarding and check and remove any existing forwards.

@deadshotdann commented on GitHub (Feb 26, 2025): This would be a useful time save. I often have to manually go into the mailbox after running a CIPP offboarding and check and remove any existing forwards.

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Feb 26, 2025):

Hello,

Thank you for your interest in improving CIPP!
To keep our development process focused and manageable, feature requests are limited to paying users. This policy helps us prioritize improvements that directly benefit those actively supporting CIPP and ensures we can sustain our development and support.

When a sponsor makes a feature request, their support covers training, development, documentation, and security checks. Allowing non-sponsor requests could lead to a backlog that slows down updates and stretches resources thin, ultimately affecting the quality and sustainability of CIPP.

While we’ve closed this request, we appreciate your input. You’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer, feel free to open a PR that includes your feature request or comment "I’d like to work on this!" to assign the issue to yourself.

Did you get this notification in error? Reply with a screenshot of your sponsorship payment and we’ll reopen the issue.

Thank you for understanding,
The CIPP Team

@github-actions[bot] commented on GitHub (Feb 26, 2025): Hello, Thank you for your interest in improving CIPP! To keep our development process focused and manageable, **feature requests are limited to paying users**. This policy helps us prioritize improvements that directly benefit those actively supporting CIPP and ensures we can sustain our development and support. When a sponsor makes a feature request, their support covers training, development, documentation, and security checks. Allowing non-sponsor requests could lead to a backlog that slows down updates and stretches resources thin, ultimately affecting the quality and sustainability of CIPP. While we’ve closed this request, we appreciate your input. You’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer, feel free to open a PR that includes your feature request or comment "**I’d like to work on this!**" to assign the issue to yourself. **Did you get this notification in error?** Reply with a screenshot of your sponsorship payment and we’ll reopen the issue. _Thank you for understanding,_ **The CIPP Team**

kerem commented

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

Author

Owner

@patrick-synium commented on GitHub (Feb 26, 2025):

Hi @KelvinTegelaar - we are indeed a sponsor/paying customer. See screenshot below. Happy to send you copy of the full invoice PDF if you have a private location I can send it?

@patrick-synium commented on GitHub (Feb 26, 2025): Hi @KelvinTegelaar - we are indeed a sponsor/paying customer. See screenshot below. Happy to send you copy of the full invoice PDF if you have a private location I can send it? ![Image](https://github.com/user-attachments/assets/2d693baf-632b-44f7-a695-f1d835682400)

kerem commented

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

Author

Owner

@patrick-synium commented on GitHub (Feb 27, 2025):

Hi @KelvinTegelaar - can you see the above? We are paying customers. Can you consider re-opening this feature request pls.

@patrick-synium commented on GitHub (Feb 27, 2025): Hi @KelvinTegelaar - can you see the above? We are paying customers. Can you consider re-opening this feature request pls.

kerem commented

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

Author

Owner

@kris6673 commented on GitHub (Mar 3, 2025):

I would like to work on this please!

@kris6673 commented on GitHub (Mar 3, 2025): I would like to work on this please!

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Mar 3, 2025):

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

@github-actions[bot] commented on GitHub (Mar 3, 2025): Great! I assigned you (@kris6673) to the issue. Have fun working on it!

kerem commented

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

Author

Owner

@kris6673 commented on GitHub (Mar 3, 2025):

@patrick-synium Just to be sure, you want an way to disable any and all forwarding for the user you are offboarding?
Not get all mailboxes and disable all forwarding, like in the powershell example you provided.

@kris6673 commented on GitHub (Mar 3, 2025): @patrick-synium Just to be sure, you want an way to disable any and all forwarding for the user you are offboarding? Not get all mailboxes and disable all forwarding, like in the powershell example you provided.

kerem commented

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

Author

Owner

@patrick-synium commented on GitHub (Mar 3, 2025):

Yes, sorry, powershell script was not correct. Intention is to be able to remove all forwarders for a user being offboarded, as part of CIPP's offboarding process. Thank you for your support!

@patrick-synium commented on GitHub (Mar 3, 2025): Yes, sorry, powershell script was not correct. Intention is to be able to remove all forwarders for a user being offboarded, as part of CIPP's offboarding process. Thank you for your support!

kerem commented

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

Author

Owner

@kris6673 commented on GitHub (Mar 3, 2025):

Added in dev

@kris6673 commented on GitHub (Mar 3, 2025): Added in dev

Rows
Columns

[GH-ISSUE #3702] [Feature Request]: Add option to remove all Forwarding addresses from User in Offboarding Wizard #1643

Please confirm:

Problem Statement

Benefits for MSPs

Value or Importance

PowerShell Commands (Optional)