No tenant connection
The workflow itself never signs in to Active Directory or Microsoft 365. Any generated PowerShell runs only after you review and execute it locally.
Guide a controlled single-user offboarding process with discovery, handover checks and explicit change steps.
This guide is designed for a single administrative task rather than a broad tenant-wide assessment. It keeps discovery, preparation, any manual change and final verification separate so you can review each step before moving on.
Opselith does not execute these steps against your environment. Script steps open a reviewed Opselith template; change steps remain explicit so nothing is hidden behind a browser action.
Confirm the approved offboarding time, data owner and retention or legal requirements before touching the account.
Export the Teams the user belongs to so ownership or membership dependencies are visible before access is removed.
Open Export Teams for a user →Check existing forwarding before deciding on mailbox handover, conversion or new forwarding.
Open Export mailbox forwarding →Capture the current licensed-user state before licenses are removed or changed.
Open Export licensed Entra users →Use the OneDrive inventory to confirm the personal site and ownership context before handover decisions.
Open Export OneDrive site inventory →Use your approved Entra or identity administration process to block access and revoke sessions at the agreed time. Opselith does not execute this change.
Apply the approved handover, membership and licensing changes in the authoritative administration tools.
Use the Free disabled-user report as one verification signal after the access change.
Open Export disabled Entra users →Confirm access is blocked, handover is complete and the ticket records every retained or intentionally deferred item.
The workflow itself never signs in to Active Directory or Microsoft 365. Any generated PowerShell runs only after you review and execute it locally.
Completed workflow step IDs can be stored in your browser. Identity values, tickets, usernames, domains and generated output are not part of that progress record.
Where no suitable reviewed script exists, the guide labels the action as a manual change rather than pretending the website performed it.
Opselith separates metadata review, static QA, analyzer evidence and runtime evidence. A missing runtime result or a Pending analyzer state is shown as-is rather than converted into a pass claim.
Workflow catalog, ordered runbook, local-progress and manual-change boundary QA.
A guided workflow is not itself a PowerShell artifact.
No accepted runtime result is recorded for this workflow yet.
browser-guided-runbook · no website tenant connection · tenant output stays outside Opselith.
Trust metadata reviewed for the current 3.0 development contract.
5 referenced scripts · 5 analyzer Passed · 0 Pending
Pending and Not yet recorded are evidence states, not failures. Review the generated script or runbook and validate it in your own environment before production use.
Use the final verification step to confirm the resulting account, membership, licensing or service state in the relevant Microsoft administration portal or Active Directory tooling. Opselith is a runbook and script-generation layer, not the system of record.