Active Directory Distribution Group Message Approval Setting

How to require approval for emails sent to an Active Directory distribution group: the two AD attributes behind it, plus the supported Exchange method in 2026.

Active Directory Distribution Group Message Approval Setting

A common request from management is simple: nobody should be able to email the whole staff list without someone approving it first. In Exchange this is called moderation, or distribution group message approval. When I first set it up in 2019, I did it straight in Active Directory, and the approach still explains what is happening underneath.

The cause: moderation lives in two attributes

A distribution group does not hold messages for approval by default. Anyone allowed to send to it can do so, and the message goes straight out to every member.

Moderation is switched on by two Exchange attributes stored on the group object in Active Directory. Microsoft's Exchange team maps them directly in its Demystifying Moderation article:

Exchange setting AD attribute
ModerationEnabled msExchEnableModeration
ModeratedBy msExchModeratedByLink

My original 2019 fix

This is what I wrote back then, and it worked:

  1. Open the distribution group in Active Directory (Attribute Editor or ADSI Edit).
  2. Set msExchEnableModeration to True.
  3. In msExchModeratedByLink, add the people who can approve messages.

One correction to my old note: I wrote "add the CN" of each approver. In practice msExchModeratedByLink is a linked attribute, so it stores the full distinguished name (DN) of each moderator, for example CN=Approver One,OU=Staff,DC=contoso,DC=com, not just the CN.

Update 2026: set distribution group message approval with Exchange tools

The attributes are still the right ones, but I no longer recommend editing them by hand. The Exchange cmdlets and the admin center validate what you enter, while a raw attribute edit can leave a bad value behind that is hard to trace later. Microsoft does not say direct editing is unsupported; this is my advice from experience.

Steps (Exchange Server SE or Exchange Online PowerShell)

  1. Record the current settings first, so you can roll back:
Get-DistributionGroup "[email protected]" |
  Format-List Name,ModerationEnabled,ModeratedBy,ManagedBy,BypassModerationFromSendersOrMembers
  1. Enable moderation and name the approvers using Set-DistributionGroup:
Set-DistributionGroup "[email protected]" -ModerationEnabled $true `
  -ModeratedBy "[email protected]","[email protected]"
  1. Optionally let trusted senders skip approval, such as the HR or communications team:
Set-DistributionGroup "[email protected]" `
  -BypassModerationFromSendersOrMembers "[email protected]"

Note that this replaces the existing list. Check the values from step 1 before overwriting them.

  1. Prefer a graphical route? In the Exchange admin center go to Recipients > Groups, edit the distribution group, and select Message approval.

Rules worth knowing

  • A moderator must be a mailbox, mail user or mail contact in your organisation.
  • If you enable moderation on a distribution group but name no moderators, the group owners (set by ManagedBy) approve messages instead.
  • Mail-enabled security groups are different: you must name at least one moderator.
  • In Exchange Online you can assign up to 10 moderators, according to Microsoft's guidance on moderated recipients.
  • If the group is synchronised from on-premises AD, my understanding is that you still make the change on-premises, as the cloud copy is managed from there.
  • If you tried a mail flow (transport) rule instead, note that it does not let you choose a distribution group as the moderator. For a whole group, the group's own message approval setting is cleaner.

How to check it worked

  1. Run the Get-DistributionGroup command from step 1 again. ModerationEnabled should be True and ModeratedBy should list your approvers.
  2. Send a test message to the group from an account that is not on the bypass list.
  3. Confirm the moderator receives an approval request, and that members only get the message after it is approved.
  4. Send from a bypass sender and confirm it is delivered directly.

Cautions

  • Back up first. Save the output of the Get-DistributionGroup command before changing anything. Parameters such as ModeratedBy and BypassModerationFromSendersOrMembers replace values rather than add to them.
  • Test on a small group before applying it to your all-staff list, so nobody important is blocked during a busy day.
  • Have at least two moderators, so messages are not stuck when one approver is on leave.
  • Check your Exchange version. Exchange Server 2016 and 2019 reached end of support on 14 October 2025. Microsoft recommends moving to Exchange Online or upgrading to Exchange Server Subscription Edition (SE), as covered in the Exchange Team's end of support notice. If Exchange 2013 or earlier is still in your organisation, it must be removed before you can install Exchange 2019 CU15 or upgrade to SE.

Quick checklist

  • [ ] Current group settings exported
  • [ ] Supported Exchange version (SE or Exchange Online)
  • [ ] Moderation enabled with Set-DistributionGroup or the admin center
  • [ ] At least two moderators, each a mailbox, mail user or mail contact
  • [ ] Bypass list set for trusted senders, if needed
  • [ ] Test message approved and delivered

The takeaway: the two AD attributes from my 2019 note still drive message approval, but set them through Exchange, on a supported version, and let the tools do the validation for you.

Sources & further reading

  1. Set-DistributionGroup (Microsoft Learn)learn.microsoft.com
  2. Moderated recipients in Exchange Online (Microsoft Learn)learn.microsoft.com
  3. Exchange Server supportability matrix (Microsoft Learn)learn.microsoft.com
  4. Demystifying Moderation (Exchange Team blog)techcommunity.microsoft.com
  5. T-1 month: Exchange Server 2016 and 2019 end of support (Exchange Team blog)techcommunity.microsoft.com

📝 First written from my own work in 2019; updated and expanded in November 2026 with AI assistance, keeping my original fix. Spotted something wrong? Tell me.

Akam Omer
Written by

Akam Omer

IT leader, engineer and security specialist from Erbil with 20+ years across higher education, telecoms, healthcare and government. Founder of BulkSMSIraq, VerifyWay and Kurd.ai.