Automate employee offboarding across Active Directory, Entra ID, and Okta

Starting promptUse this prompt as a starting point to build your workflow.

Build a workflow triggered by an offboarding request (form, webhook, or HRIS event) carrying the departing user's email and username. Look the user up and disable/suspend the account in on-prem Active Directory using a CoHTTP request, in Microsoft Entra ID, and in Okta, revoking active sessions in each. Capture the per-system result; if the user is absent in a system, log that and continue rather than failing the run. Retry transient API errors with backoff, and post a consolidated success/failure summary to a Slack or Teams channel and an audit ticket. Output a structured record of every account actioned.

New to Tines?Sign up free for Tines 3B Explore Edition

What this prompt builds

Disable a departing employee's accounts across on-prem Active Directory, Microsoft Entra ID, and Okta from a single coordinated workflow.

The problem

When an employee leaves, their accounts frequently linger across on-prem Active Directory, Entra ID, and Okta because each directory is owned by a different admin and disabled by hand. Those orphaned identities are a top audit finding and a genuine path to compromised access.

Solution and impact

A single offboarding workflow fans out to Active Directory (via a CoHTTP request), Entra ID, and Okta to disable the user everywhere at once and confirm each action. IT closes offboarding in minutes instead of chasing three consoles, with a consistent, auditable trail every time.

Automate employee offboarding across Active Directory, Entra ID, and Okta | Tines 3B examples | Tines