starred/CIPP

Fork 0

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

[GH-ISSUE #4215] [Feature Request]: Add ability to remove deprecated add-ins for "Report Phishing" and "Report Message" #1906

New issue

Closed

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

kerem commented

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

Owner

Originally created by @HappyEarthDay on GitHub (Jun 5, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4215

Originally assigned to: @rvdwegen 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

We need a streamlined way to remove the legacy "Report Message" and "Report Phishing" add-ins from Microsoft 365 tenants. These older add-ins were deployed via Integrated Apps in the M365 Admin Center and are now in maintenance mode. While the new red “Report” button (targeted by the current standard) can be enabled/disabled easily, many tenants now have both the new and old buttons, leading to user confusion and increased support tickets. We'd like the ability to remove these legacy add-ins at scale to maintain a clean and consistent user experience.
Reference: https://learn.microsoft.com/en-us/defender-office-365/submissions-users-report-message-add-in-configure

Benefits for MSPs

Reduces helpdesk noise: Avoids unnecessary support tickets from users confused by having multiple similar buttons in Outlook.
Saves time: Avoids manually navigating to each tenant’s Integrated Apps page to remove the deprecated add-ins one by one.
Improves consistency: Ensures only the currently supported phishing reporting method is deployed across tenants.
Supports transitions: As Microsoft sunsets the old add-ins, we need tooling to support that change proactively.

Value or Importance

This is a high-value feature for MSPs. Although the older add-ins are going away eventually, we support many clients right now who are experiencing confusion and misreporting due to the duplicate buttons. Without centralized removal, we’re left manually cleaning up legacy add-ins tenant by tenant. That doesn’t scale. Even if temporary, this capability will provide clarity and reduce operational overhead.

PowerShell Commands (Optional)

No response

Originally created by @HappyEarthDay on GitHub (Jun 5, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4215 Originally assigned to: @rvdwegen 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 We need a streamlined way to remove the legacy "Report Message" and "Report Phishing" add-ins from Microsoft 365 tenants. These older add-ins were deployed via Integrated Apps in the M365 Admin Center and are now in maintenance mode. While the new red “Report” button (targeted by the current standard) can be enabled/disabled easily, many tenants now have both the new and old buttons, leading to user confusion and increased support tickets. We'd like the ability to remove these legacy add-ins at scale to maintain a clean and consistent user experience. Reference: https://learn.microsoft.com/en-us/defender-office-365/submissions-users-report-message-add-in-configure ### Benefits for MSPs - Reduces helpdesk noise: Avoids unnecessary support tickets from users confused by having multiple similar buttons in Outlook. - Saves time: Avoids manually navigating to each tenant’s Integrated Apps page to remove the deprecated add-ins one by one. - Improves consistency: Ensures only the currently supported phishing reporting method is deployed across tenants. - Supports transitions: As Microsoft sunsets the old add-ins, we need tooling to support that change proactively. ### Value or Importance This is a high-value feature for MSPs. Although the older add-ins are going away eventually, we support many clients right now who are experiencing confusion and misreporting due to the duplicate buttons. Without centralized removal, we’re left manually cleaning up legacy add-ins tenant by tenant. That doesn’t scale. Even if temporary, this capability will provide clarity and reduce operational overhead. ### PowerShell Commands (Optional) _No response_

kerem

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

closed this issue
added the
enhancement

Planned
labels

kerem commented

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

Author

Owner

@rvdwegen commented on GitHub (Jun 12, 2025):

Don't ask how, but it should be possible. Taking a look tomorrow.

@rvdwegen commented on GitHub (Jun 12, 2025): Don't ask how, but it should be possible. Taking a look tomorrow.

kerem commented

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

Author

Owner

@Zacgoose commented on GitHub (Aug 26, 2025):

I think I have figured this out, will push to a standard and test

@Zacgoose commented on GitHub (Aug 26, 2025): I think I have figured this out, will push to a standard and test

kerem commented

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

Author

Owner

@KelvinTegelaar commented on GitHub (Sep 1, 2025):

added in dev

@KelvinTegelaar commented on GitHub (Sep 1, 2025): added in dev

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

No description provided.

Rows
Columns