mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #5331] Standards Templates - False Positive & No Auto-Remediation #2566
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#2566
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cvalencia-ryc on GitHub (Feb 5, 2026).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/5331
Required confirmations before submitting
Issue Description
Issue Description:
1- CIPP Standards Template throwing false positive alerts, for example, a shared mailbox with sign-in disabled is being reported as enabled.
2- Even deleting the templates won't stop the alerts. Tickets are still being created with no templates or drifts created.
How to reproduce:
1- Going into Tenant Admin -> Standard Management -> Templates
2- Created a new template for all tenants and added a few standards like: "disable unlicensed resources" and "disabled shared mailboxes Entra accounts"
3- Setting up each standard to "remediate", "report" and "alert"
Result:
Disabled unlicensed resources and disabled shared mailboxes are being picked up as enabled.
Action Taken:
Deleted the whole template and the alerts are still being created.
Environment Type
Sponsored (paying) user
Front End Version
v10.0.9
Back End Version
v10.0.9
Relevant Logs / Stack Trace
@github-actions[bot] commented on GitHub (Feb 5, 2026):
Thank you for reporting a potential bug. If you would like to work on this bug, please comment:
Thank you for helping us maintain the project!
@KelvinTegelaar commented on GitHub (Feb 5, 2026):
!support
@github-actions[bot] commented on GitHub (Feb 5, 2026):
Hello,
Thank you for reaching out! This report has been classified as a support request rather than a bug or feature request. To keep our development process focused, support requests are limited to paying users. This policy allows us to prioritize resources for those actively supporting CIPP, helping us maintain high-quality development and support.
Sponsors can contact our helpdesk directly via email for assistance with any issues or questions. For non-sponsor support, please refer to our documentation and community discussions—many questions have been answered there.
Did you get this notification in error? Reply with a screenshot of your sponsorship payment, and we’ll gladly reopen the request.
Thank you for your understanding,
The CIPP Team