What is a one sentence summary of your feature request?
Introduce separate priorities and dependency-aware scheduling for provisioning and deprovisioning tasks to prevent operational blocking and improve efficiency.
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
Currently, provisioning and deprovisioning tasks are processed with the same priority and share the same limited task scheduler capacity. In practice, individual actions are often logically dependent on each other (e.g. managed accounts requiring enable/disable operations in a specific order).
When a large number of deprovisioning tasks are triggered (for example during mass offboarding), the task scheduler can become saturated. As a result, new provisioning tasks cannot be executed in a timely manner, even though they are critical for ongoing business operations.
Introducing priority separation between provisioning and deprovisioning, combined with dependency-aware execution (e.g. respecting relationships between managed accounts and enable/disable actions), would ensure that critical provisioning processes are not blocked by bulk deprovisioning activities. This would significantly improve reliability, predictability, and operational efficiency.
How do you currently solve the challenges you have by not having this feature?
At the moment, the issue can only be mitigated manually by delaying or throttling deprovisioning activities, scheduling them outside of peak hours, or closely monitoring the task queue. These workarounds are error-prone, require manual intervention, and negatively impact efficiency and user experience.