In short: A leaver workflow has two jobs: remove access at the authorised time, and keep records the business must retain. A disabled account is not proof that every app was closed, and deleting a mailbox is not a retention policy.
Someone leaving creates two jobs that are easy to collapse into one button. Remove access at the time HR has authorised. Keep the records the business is still required to hold. Deleting the account does neither job properly. The workflow needs an HR trigger, a system-by-system list and evidence that each action succeeded.
The joiner side of the same handoff is the onboarding checklist. What to keep, and for which regime, is the retention guide.
Confirm the person and the timing
The trigger is an authorised HR event: the person, the employing entity, the effective time and whether the path is ordinary notice or an urgent removal. A manager’s chat message is a prompt to HR, not the trigger. If the last day is later corrected, scheduled tasks move with the HR record. The acceptance test is a date changed after the checklist was created: disabling someone a week early is a real incident.
Urgent removal still follows the same evidence rules. It shortens the clock. It does not skip the record of what was done.
Inventory before you disable
Build the list from what the person can actually open, not from the single sign-on brochure:
- identity provider account;
- mailbox and any delegated access they hold on other mailboxes;
- business apps, including those with a local password;
- VPN, remote desktop and admin roles;
- shared credentials and team passwords they know;
- devices and mobile profiles;
- API tokens, automation connections and scheduled jobs they own.
A completed task is not evidence. Evidence is the application’s response, or a named person confirming the admin screen after a failed call. Microsoft’s tutorial on lifecycle workflows for offboarding shows how an authorised workflow can track user, run and task status. The page states that the feature requires Microsoft Entra ID Governance or Microsoft Entra Suite licences. The tutorial includes destructive user operations as examples. Do not run deletions from a blog. Read the effect in your tenant, with an admin who is allowed to perform them. Entra does not see a local account that never federated.
Revoke, record, and escalate the miss
Use the administration interface the vendor supports. Record the outcome against the system row: succeeded, failed, or not applicable, with the time and the actor. Failures go to a named person immediately. Do not mark the whole leaver “done” while a row is failed.
Shared admin passwords are not a control. The PDPC’s Key Concepts guidelines expect reasonable security arrangements against unauthorised access and similar risks. A checklist in a shared spreadsheet, edited with a former employee’s password, fails that idea even when every box is ticked.
Least privilege applies to the offboarding operators too. The account that can disable everyone should not be a daily user account, and its use should be attributable.
Move the work before you remove the owner
Production automations die quietly when their owner’s account is disabled. Before that disable:
- reassign documents and team ownership;
- move workflow connections to a service account the company owns;
- check scheduled jobs, mailbox rules and API tokens;
- confirm a second person can still run the failure path.
The acceptance test is a leaver who owns a production connection. Disabling them without a transfer is a failed test even if the identity provider returns success.
Records stay, logins do not
MOM’s employment records guidance applies to employees covered by the Employment Act: latest two years for current employees; for those who have left, the last two years kept for one year after they leave. It does not say “delete the mailbox on Friday”. GST and other business records can have a longer life; IRAS requires GST records to be kept for at least five years from the end of the accounting period. Put the copies you must keep in restricted storage that is not the leaver’s login. Then remove the login.
Do not paste NRIC numbers or full identity documents into the test data for this workflow.
Acceptance tests
- A connected application refuses the revocation call. The row stays open and a person is assigned.
- The leaver owns a production automation. Ownership is moved and the job still runs, or it is deliberately stopped and that stop is recorded.
- HR corrects the last day after tasks were scheduled. Actions follow the new time.
Illustrative scenario, not a client engagement: an SME disables the central identity account and federated apps close. A supplier portal still has a local user. The workflow opens a manual revocation task and will not report completion until IT confirms that portal. Employment files needed for MOM’s record duty are already in the HR system. The mailbox is converted or exported only where the business has decided the contents are still required, and then sign-in ends.
This is an operational design guide. It is not employment or data-protection advice, and FYAdvisers is not a law firm. To separate the apps you can close from the ones you cannot see, use the contact form or WhatsApp +65 9071 3976 (chat).
Frequently asked questions
How do you prove access was removed in each application?
By an outcome from that application: a disabled or deleted account id, a timestamp and the admin path used. A task ticked by a person is a claim. Where the API fails, the task stays open until someone verifies the screen that still grants access.
Which actions are hard to undo, and who should approve them?
Deleting a mailbox, wiping a device and removing a user object can destroy data you still need. Disable and transfer ownership first. Irreversible steps need a named approver and a check that the business records have a new home.
How do you keep required records without leaving a login active?
Export or reassign the business records to a restricted store or a shared mailbox that is not the leaver’s credential. Then remove the leaver’s sign-in. MOM employment-record duties and GST record duties are about the records, not about keeping a password alive.
Will Microsoft Entra offboard every SaaS tool?
No. Microsoft’s lifecycle-workflow tutorial covers tasks in that identity model and requires Microsoft Entra ID Governance or Microsoft Entra Suite licences. A local account in a supplier portal still needs its own revocation step.

