Can a Microsoft 365 Group be used as an authorized sender on a Dynamic Distribution List?

Federico Ciampi 40 Reputation points
2026-07-28T12:29:55.1066667+00:00

Environment: Exchange Online (cloud-only), Exchange admin center.

What I'm trying to do

On a Dynamic Distribution List (DDL), under Delivery management → Specified senders, I want to restrict who can send to the group. I need to add a Microsoft 365 Group ([Moderator note: Personally Identifiable Information removed]@contoso.com, which is also connected to a Team) to the list of authorized senders.

What happens

The Microsoft 365 Group is not accepted / does not appear as a valid choice when I type its address. Other objects (a distribution group and mail-enabled security groups) are accepted without any problem, so the field itself works.

My understanding

This maps to the AcceptMessagesOnlyFromSendersOrMembers parameter, whose valid values are individual senders (mailboxes, mail users, mail contacts) and groups (distribution groups, mail-enabled security groups, dynamic distribution groups). Microsoft 365 (Unified) Groups do not seem to be in that list.

Questions

  1. Is it by design that a Microsoft 365 Group cannot be used as an authorized sender on a Dynamic Distribution List?
  2. Is there any supported way (UI or PowerShell via Set-DynamicDistributionGroup) to make it work with a Microsoft 365 Group directly?
  3. If not, is a mail-enabled security group mirroring the M365 Group membership the recommended approach?

Thanks in advance.

[Moderator note: Personally Identifiable Information removed]  

Microsoft 365 and Office | Install, redeem, activate | For business | Other
0 comments No comments

Answer accepted by question author
Anonymous
2026-07-28T13:49:17.8766667+00:00

Hi @Federico Ciampi,

Thank you so much for sharing such a detailed and well-researched question. I'm happy to answer based on my understanding of the Exchange Online behavior and the information currently documented by Microsoft.

1/Is it by design that a Microsoft 365 Group cannot be used as an authorized sender on a Dynamic Distribution List?

Yes, this is by design. For the AcceptMessagesOnlyFromSendersOrMembers parameter, the supported values are:

  • Individual senders: mailboxes, mail users, and mail contacts.
  • Groups: distribution groups, mail-enabled security groups, and dynamic distribution groups.

A Microsoft 365 Group, also known as a Unified Group, is not included in the supported group types. Therefore, it will not appear as a valid selection under Delivery management > Specified senders.

2/ Is there any supported way (UI or PowerShell via Set-DynamicDistributionGroup) to make it work with a Microsoft 365 Group directly?

At this time, I am not aware of any supported method to use a Microsoft 365 (Unified) Group directly as an authorized sender for a Dynamic Distribution Group.

While Set-DynamicDistributionGroup does expose the AcceptMessagesOnlyFromSendersOrMembers parameter, Microsoft documentation does not identify Unified Groups as a supported object type for this setting. Additionally, the fact that the Microsoft 365 Group cannot be selected in the Exchange admin center is consistent with that limitation and suggests that this scenario is not currently supported.

3/If not, is a mail-enabled security group mirroring the M365 Group membership the recommended approach?

Yes. In my opinion, a mail-enabled security group would be the most practical and fully supported workaround in this scenario. A standard distribution group could also be used if security-based permissions are not required.

You can add the users who should have sending rights to the mail-enabled security group and then configure that group as an authorized sender under the Dynamic Distribution List's Specified senders setting. When a supported group is granted permission, all members of that group are allowed to send messages to the Dynamic Distribution List.

Please note that Exchange Online does not automatically synchronize membership between a Microsoft 365 Group and a separate mail-enabled security group. The membership must therefore be maintained manually or synchronized through administrative automation. If only a small number of users require permission, you may alternatively add their individual mailboxes directly rather than maintaining another group. 

I sincerely appreciate your time in reviewing the information I've shared and your willingness to consider the available options!

Thank you again for bringing this question to the community. I hope the explanation helps clarify the current behavior and provides a useful direction for your implementation and future reference.


If the answer is helpful, please kindly click "Yes". If you have extra questions about this answer, please click "Comment". 

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.  

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Newest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.