Automatic GLM Safeguard with Threshold Protection, Pause, and Alerting for Abnormal Group Expirations

What is a one sentence summary of your feature request?

Implement a built-in GLM safeguard that automatically detects abnormal mass expiration events, pauses execution, and alerts administrators when configurable thresholds are exceeded.

Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.

Our organization experienced an unexpected mass group expiration event that resulted in a large number of groups being expired unintentionally. Following this incident, GLM had to be disabled to prevent further impact.

Currently, GroupID/Directory Manager does not provide a native safeguard mechanism to identify and stop abnormal mass expiration events before they occur. Although Netwrix Support has provided an external PowerShell-based monitoring solution as a temporary workaround, a product-level safeguard is required for long-term protection.

We request a feature that:

Monitors the number of groups scheduled for expiration.
Supports configurable expiration thresholds.
Automatically pauses or blocks GLM execution when thresholds are exceeded.
Generates alerts and notifications to designated administrators.
Creates audit log entries for all safeguard events.
Provides a review and approval workflow before resuming execution.
Allows administrators to override the safeguard when necessary.
Displays warning messages and affected group counts before processing begins.

This functionality would significantly reduce the risk of accidental mass expirations and provide administrators with sufficient time to investigate abnormal situations before any changes are applied.

How do you currently solve the challenges you have by not having this feature?

Unexpected mass group expirations can lead to access disruptions, operational outages, increased administrative workload, and extensive recovery efforts. Because of the recent mass expiration event, we were forced to disable GLM entirely, and it remains disabled today while the root cause analysis is still in progress. Until the issue is fully understood and resolved, we cannot confidently re-enable automated lifecycle management processes.

A native safeguard mechanism would allow organizations to operate GLM with greater confidence by preventing abnormal expiration activities before they impact production environments.

Thank you for sharing this, and I’m sorry to hear about the mass expiration event and the disruption it caused. Having to switch GLM off entirely is exactly the outcome we want to help customers avoid.

The safeguards you describe make sense to me: a threshold on how many groups can expire in one run, pausing execution when it’s exceeded, alerts to admins, audit entries, and a review step before things resume. Together they would give you a chance to catch a problem before it reaches production, and that’s the kind of confidence people need to run lifecycle automation unattended.

I’ve captured your request and the details in our product backlog, and the product team will be using it as input when we look at GLM improvements. I can’t share timing or scope at this point, but your write-up is a useful and specific case for us and has our attention.

Thanks again for taking the time to write this up.