> ## Documentation Index
> Fetch the complete documentation index at: https://university.triggr-app.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Bulk Staff Offboarding

> Disables several leavers' Microsoft 365 accounts in your client's tenant in one run, signs them out and can convert their mailboxes to shared.

Bulk Staff Offboarding closes down several leavers at once: it blocks their sign-in, signs them out everywhere and, if you choose, converts their mailboxes to shared mailboxes. It runs as soon as it's submitted, or approved, as one run for everyone. Use [User Offboarding](/core/workflows/user-offboarding) instead when a leaver needs a set time, a mailbox handover, or their licences and groups removed: it offboards one person with the settings on its Offboarding card. Bulk Staff Offboarding needs [Microsoft 365 connected](/core/get-started/connect-microsoft-365) with a GDAP role that can disable users, such as [User Administrator](/integrations/microsoft-graph/recommended-roles), [Exchange access](/core/reference/microsoft-faq#exchange-online) to convert mailboxes, and the [desktop agent](/desktop-agent/overview) for a client that syncs on-premises Active Directory.

<Frame caption="Bulk Staff Offboarding in 49 seconds: what it asks, what it does and what you get.">
  <video controls preload="none" playsInline className="w-full aspect-video rounded-xl" poster="/images/videos/wf-bulk-staff-offboarding-overview.jpg" src="https://mintcdn.com/triggr/rFRD51HB_88hTzdJ/images/videos/wf-bulk-staff-offboarding-overview.mp4?fit=max&auto=format&n=rFRD51HB_88hTzdJ&q=85&s=bcced513bbd18be87a76a402cbe857da" data-path="images/videos/wf-bulk-staff-offboarding-overview.mp4" />
</Frame>

## What the form asks

| Field | |
| - | - |
| Leavers | Required by default. Add each person from the client's users, filtered by User directory filters |
| Last working day | Optional by default. For your records and the ticket; the run doesn't wait for it |
| Convert mailboxes to shared? | Optional by default, and starts on No. Yes converts every leaver's mailbox |
| Reason / ticket reference | Optional by default. For your records and the approver; not sent to Microsoft |

## What it does

1. Creates one PSA ticket for the run, if Ticketing is on.
2. Waits for approval, if Approval is Internal or External, or a conditional override matches.
3. Disable Account, for each leaver. For a client that syncs on-premises AD, synced accounts are disabled in AD through the desktop agent in one go, then synced; cloud-only accounts are disabled in Microsoft 365.
4. Revoke Sessions, for each leaver.
5. Convert To Shared, for each leaver's mailbox, if Convert mailboxes to shared? is Yes.

With Log actions to the ticket on, each action adds a note to the ticket, for each leaver.

The steps run in order in one run, one leaver at a time. If an action fails for a leaver, the run stops there, so the leavers after them and the later steps aren't done; Executions shows where it stopped.

## Configure it

Go to **Config** and click Bulk Staff Offboarding, under Lifecycle. It has no Offboarding card, and User Offboarding's settings don't apply to it.

<Frame caption="Configure Bulk Staff Offboarding: every option, step by step (1:25).">
  <video controls preload="none" playsInline className="w-full aspect-video rounded-xl" poster="/images/videos/wf-bulk-staff-offboarding-configure.jpg" src="https://mintcdn.com/triggr/rFRD51HB_88hTzdJ/images/videos/wf-bulk-staff-offboarding-configure.mp4?fit=max&auto=format&n=rFRD51HB_88hTzdJ&q=85&s=2f6e0dce774f22082bac97829c7d49fb" data-path="images/videos/wf-bulk-staff-offboarding-configure.mp4" />
</Frame>

| Setting | Where | What it does |
| - | - | - |
| Availability | Header | Internal only, Public form only, Internal + public or Disabled. List on homepage needs a public form. Base config only |
| Leavers, Last working day, Convert mailboxes to shared?, Reason / ticket reference | Form config | Hidden, Optional or Required for each. Keep Leavers required. Hide Convert mailboxes to shared? and mailboxes are never converted. Can differ per client |
| Add field, Add section | Form config | Your own questions. They're saved with the request and can go in ticket templates, but aren't sent to Microsoft. Add client section asks one client only |
| Approval | Approval | None runs on submit. Internal waits for a teammate or group; External waits for the client's approver, set on each client. Conditional overrides use a different approval when the answers match. Let the approver edit the request lets them correct the answers first |
| Ticketing | Ticketing | Create one PSA ticket for each run, with its type, priority, status, subject and body. Log actions to the ticket adds an internal or public note as each action completes |
| User directory filters | User directory filters | Which users the Leavers picker lists: licensed, active, no guests, and not in the Entra roles you exclude. Exclude specific users at a client's scope |

Approval, Ticketing and User directory filters are set on Base config and apply to every client unless you override them for one. For how Base config and client overrides work, see [How configuration works](/core/get-started/configure-user-onboarding#settings-for-each-client).

## Troubleshooting

<AccordionGroup>
  <Accordion title="Someone isn't in the Leavers list">
    Check User directory filters. Active users only hides accounts whose sign-in is already blocked, and Licensed users only hides people with no licence; untick them on Base config or for that client.
  </Accordion>

  <Accordion title="“… is AD-synced but Microsoft 365 reports no user principal name for it, so the on-prem change can't be targeted”">
    A synced leaver has no on-premises user principal name in Microsoft 365, so nothing was submitted. Check the account's UPN in AD and that it has synced, then submit again.
  </Accordion>

  <Accordion title="The ticket says “Disable On-Prem Accounts — needs manual attention”">
    AD couldn't disable the synced accounts the note names, and the run stopped before anything else ran for any leaver. Disable those accounts in AD, then run it again for all the leavers.
  </Accordion>
</AccordionGroup>

## Related

* [Workflow catalogue](/core/reference/workflow-catalogue)
* [Run a workflow](/core/use/run-a-workflow)
* [Executions](/core/use/executions)
* [User Offboarding](/core/workflows/user-offboarding), for one leaver with a set time and handover
* [Re-enable Terminated Account](/core/workflows/re-enable-terminated-account), to bring someone back


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.