> For the complete documentation index, see [llms.txt](https://helpdesk.augmentt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.augmentt.com/modules/engage/distribution-lists.md).

# Distribution Lists

From Engage, you can create, edit, and remove Microsoft distribution lists across all of your customer tenants without opening the Exchange admin center for each one. Membership and ownership changes you make through Engage are captured in Augmentt's audit log, the same as other Engage actions.

{% hint style="info" %}
Distribution lists are an Exchange object, so this feature is available for Microsoft 365 tenants only — there's no Google Workspace equivalent in Engage.
{% endhint %}

## Creating a distribution list

1. Go to **Engage > Distribution Lists**.
2. Click **Create**.
3. Enter the group details (name, alias, and similar settings).
4. Select the owners and members for the list, then click **Select**.
5. Review your choices and click **Create** to finish.

## Viewing, editing, and deleting a distribution list

1. Go to **Engage > Distribution Lists**.
2. Click the three-dot menu on the right side of the list you want to change.
3. Choose the action you need — edit membership/ownership, or delete the list.

{% hint style="warning" %}
Not yet re-verified against the codebase — flagged for fact-check: the exact set of properties you can edit after creation (for example, whether you can rename a list or change its alias post-creation, versus only membership and ownership) hasn't been confirmed against current product behavior. Verify before stating specifics to a customer.
{% endhint %}

## Gotchas from real support cases

* **Membership changes that appear to succeed but don't stick.** At least one customer reported that removing or adding users to a distribution list through Augmentt showed a success confirmation, but the change wasn't actually reflected when they went back to check — membership stayed unchanged, and they had to fall back to making the edit directly in the Microsoft 365 admin center. If you see a distribution list change that "saved" but doesn't show up on a refresh, don't assume it's applied — re-check the list in Engage after a short wait, and if it's still wrong, verify directly in the Exchange admin center and consider retrying the change from Engage rather than assuming it's permanently stuck.
* **General "removing someone from a distribution list" questions tend to be navigation questions, not bugs.** A common support contact is simply "how do I remove this person from a distribution list", usually resolved by pointing the customer at **Engage > Distribution Lists > (three-dot menu) > Edit membership**, rather than anything being broken.

{% hint style="info" %}
If a customer reports that a distribution list change isn't sticking, it's worth checking whether they're also managing that same list directly in the Exchange admin center in parallel — conflicting edits from two places around the same time are a plausible explanation, though this hasn't been confirmed as the root cause of the reported case.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helpdesk.augmentt.com/modules/engage/distribution-lists.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.