Skip to main content
Remove Mailbox Delegation takes away someone’s access to one or more mailboxes: full access to open them, or the right to send as or on behalf of them. Use it when someone no longer needs to work from a colleague’s mailbox, for example when cover ends. It’s the reverse of Mailbox Delegation, which gives that access. It needs Microsoft 365 connected, with Exchange access for the client.

Remove Mailbox Delegation in 48 seconds: what it asks, what it does and what you get.

​
What the form asks

​
What it does

  1. Creates a ticket in your PSA, if Ticketing is on.
  2. Waits for approval, if Approval is Internal or External, or a conditional override matches.
  3. Remove Mailbox Access: for each mailbox, in the client’s Exchange Online:
    • Full access removes the delegate’s permission to open the mailbox.
    • Send as removes their right to send mail that appears to come from the mailbox.
    • Send on behalf takes them off the list of people who can send on the owner’s behalf.
With Log actions to the ticket on, the ticket also gets a note when the run starts, after Remove Mailbox Access and when the run completes. Each run removes one access level. To remove full access and Send as, run it once for each.

​
Configure it

Go to Config, choose Mailboxes and click Remove Mailbox Delegation.

Configure Remove Mailbox Delegation: every option, step by step (1:25).

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.

​
Troubleshooting

Check User directory filters. By default the pickers leave out unlicensed users, users whose sign-in is blocked and guests. To remove a leaver’s access, override the filters for that client and untick Active users only. Shared mailboxes usually have no licence and blocked sign-in, so untick Licensed users only too, or use Shared Mailbox Access.
Outlook can take a while to pick up the change. Removing Full access doesn’t remove Send as or Send on behalf; run the workflow again for each.
The client has no Exchange connection in Triggr yet. See Exchange Online.