> ## 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.
# Delete Mail Contact
> Deletes one external mail contact from your client's Exchange Online, by its email address.
Delete Mail Contact removes one of the client's external mail contacts when they no longer need it. You type the contact's email address; it isn't picked from a list. It needs [Microsoft 365 connected](/core/get-started/connect-microsoft-365), with [Exchange access](/core/reference/microsoft-faq#exchange-online) for the client.
## What the form asks
| Field | |
| - | - |
| Contact email address | Required by default. The contact's full email address, for example `jo.bloggs@partner.example`. Core doesn't look it up, so check it before you submit |
| Reason / ticket reference | Optional by default. For your records and the approver; not sent to Microsoft |
## 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. Delete Mail Contact: runs `Remove-MailContact` for that address in the client's Exchange Online, without a confirmation prompt.
Each run deletes one contact. Triggr has no undo: to add the contact again, run [Create Mail Contact](/core/workflows/create-mail-contact) with its name and address.
With Log actions to the ticket on, the ticket also gets a note when the run starts, after Delete Mail Contact and when the run completes.
## Configure it
Go to **Config**, choose Mailboxes and click Delete Mail Contact.
| 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 |
| Contact email address | Form config | Required by default. Keep it Required: it's the contact the run deletes |
| Reason / ticket reference | Form config | Hidden, Optional or Required. 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 | Execution config | None runs on submit. Internal waits for a teammate or group. External waits for the client's approver, whose name and email you enter at that client's scope. Conditional overrides use a different approval when the answers match |
| Ticketing | Execution config | Create a 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 |
Approval and Ticketing 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
Core checks the address looks like `name@domain.tld`. Type the contact's full email address, with no spaces.
Exchange returned an error. Open the step in [Executions](/core/use/executions) to see Exchange's message, and check the address you typed.
The client has no Exchange connection in Triggr yet. See [Exchange Online](/core/reference/microsoft-faq#exchange-online).
## Related
* [Workflow catalogue](/core/reference/workflow-catalogue)
* [Run a workflow](/core/use/run-a-workflow)
* [Executions](/core/use/executions)
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.