Hi @NataliaYunusov,
Thanks for sharing this update - this is a great addition to OOTB capabilities! The ability to delete accounts (both human and machine) with configurable approvals directly in ISC addresses a long-standing gap that previously required custom BeforeProvisioning rules.
What I like:
- True end-to-end lifecycle management without custom code
- Configurable single/multi-step approvals at source level
- Full audit trail and email notifications
- Workflow support for real deletions (not just Flat File sources)
- API support for automation use cases
One consideration for the community:
Since approval is enabled by default with source owner as approver, organizations that don’t intend to use this feature immediately may need to:
- Review and update approval settings across all sources, OR
- Ensure source owners are correctly assigned across their environment
For large implementations with 100+ sources, this could require some initial effort to align with existing governance policies - especially if source ownership hasn’t been consistently maintained.
Suggestion: It may be helpful to have a bulk update option via API or SPConfig to configure approval settings across multiple sources efficiently. Or not enable it by default to avoid this situation.
Questions:
For the workflow Manage Account > Delete Account action - does it now respect the source-level approval settings, or does it bypass approval when triggered programmatically?
Similar question on LCS, if a Source is listed on delete accounts during an Lifecycle State, will approval on source level apply or be skipped?
Thanks again for this enhancement!
Amar