Automated Offboarding Orchestration
Introduction
Using Stephen's Stale-Account-Report runbook, with specific parameters, we're able to automatically begin the offboarding process for any stale accounts.
To see how the permissions for each tenant/etc. are configured, go to this article: https://soteria365.freshservice.com/a/solutions/articles/52000073141
How it Works
- The Stale-Account-Report runbook is run on a schedule. Currently, it's every Wednesday at 7am EST.
- The runbook is set to have the Alert Managers switch set to TRUE.
- With this switch enabled, the runbook will do additional activities beyond just the stale report.
- function Notify-Or-Offboard
- This function uses the offboardDate day threshbhold to determine what constitutes "stale" - default value for purposes of offboarding is 21 (days).
- It will split the users up into 2 groups - those who are only stale for 21 - 30 days and those who are stale for over 30 days.
- The ones who are stale for 21 - 30 will have their managers notified in an email that they should have the user login if still active or submit an offboarding ticket.
- Example email:
- The ones who are stale for 30+ days will automatically have an offboarding ticket generated in Fresh.
- Any/all users who fall within the 21 day (default) inactivity margin will be reported in an email sent to Matt Jones (or equivalent for other tenants).
- Any/all errors encountered during the run will be added to an email and sent to Stephen.