mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #5289] [Feature Request]: Monitor Entra ID Group Membership Changes #2540
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#2540
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 @Jherndon-Xantrion on GitHub (Jan 29, 2026).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/5289
Please confirm:
Problem Statement
CIPP lacks the ability to monitor group membership changes for groups in Entra ID. This is especially important for monitoring groups that control exclusions from Conditional Access rules. Some of our clients are very large, and we can't exclude individual members in CA rules, we require groups. This means that drift templates that monitor CA rules for changes don't notify us when users are excluded from CA rules
Benefits for MSPs
This improves security for the entire MSP community. If we could generate a webhook any time group membership changes for critical groups, it would close a loop the industry has had for years. The use cases are endless
Value or Importance
It's critical. Right now, we can monitor conditional access rules with CIPP for changes.. but someone can easily work around "is my CA rule configured properly and protecting my customers logic in CIPP" simply by adding someone to a group.
PowerShell Commands (Optional)
No response
@github-actions[bot] commented on GitHub (Jan 29, 2026):
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
@Jherndon-Xantrion commented on GitHub (Jan 29, 2026):
Hey Folks,
I'm not sponsoring as an individual, but my organization sponsors CIPP. Not sure where to pull this from, but we're paying the $99 a month and here's the welcome email I got when I signed up
@Jherndon-Xantrion commented on GitHub (Jan 29, 2026):