New Members Added to a Distribution List Are Not Receiving Existing Recurring Teams Meeting Invitations

Hi @Atmajeet Mohapatra,

You're correct that what you're seeing is expected behavior and not a bug.

When a meeting invitation is sent to a Distribution List (DL), Exchange Online expands the DL into its individual members at the time the invitation is sent. After that, the meeting exists independently in each recipient's mailbox and calendar. There is no ongoing link between the meeting and the DL membership. As a result, users added to the DL later will not automatically receive the existing recurring meeting invitation, and users removed from the DL will not automatically have the meeting removed from their calendars. 

Below are answers to each of your questions:

1/Is there any Microsoft-supported way to automatically send existing recurring meeting invitations to users who are added later to a Distribution List?

Unfortunately, no. Microsoft 365, Outlook, and Teams do not currently provide a native feature that automatically resends an already-created recurring meeting series to new members added to a Distribution List. In these scenarios, new users must typically be added manually by the meeting organizer, or the process must be handled through custom automation. 

2/ Are there any recommended best practices for organizations where team membership changes frequently?

If attendee membership changes regularly, using a Distribution List as the sole mechanism for managing attendees of a long-running recurring meeting is generally not ideal.

Some common approaches include:

• Adding new attendees directly to the meeting series when required and sending updates only to affected recipients.
• Creating recurring meetings for shorter periods (for example, quarterly or every six months) so attendee lists can be reviewed and refreshed regularly.
• For large audiences or announcement-style events, considering a Teams Webinar or Teams Town Hall instead of a traditional recurring meeting.

3/Is using a Distribution List the recommended approach for recurring Teams meetings, or should we instead use a Microsoft 365 Group, Teams channel meeting, or another solution?

That largely depends on your requirements, but for recurring meetings with changing membership, a Distribution List is usually not the best fit.

You may want to consider the following options:

• Distribution List: Good for static membership. New members added later won't automatically receive existing meeting invitations.
• Microsoft 365 Group: Provides a shared mailbox and shared calendar, making it easier to manage ongoing collaboration and group events.
• Teams Channel Meeting: Often the most practical option when the meeting belongs to a team. Current team members can access the meeting through the channel, and visibility naturally follows team membership changes. 

A Microsoft 365 Group is essentially "a distribution list plus more", it adds a shared mailbox, SharePoint library, and a shared calendar where each subscribed member is automatically invited to posted events, so those events appear on their personal calendars. For a recurring Teams meeting tied to a team, a channel meeting is often the cleanest, because visibility follows team membership automatically. Note, however, that even for M365 Groups, invites already sent to individual mailboxes still behave independently, the shared group calendar is what provides the ongoing visibility.

4/Are there any native Microsoft 365 features or supported automation options (such as Microsoft Graph or Power Automate) that can keep recurring meeting attendees synchronized with Distribution List membership?

Based on my experience, this may be achievable through custom automation using tools such as Microsoft Graph or Power Automate. However, because your post is currently under the Teams category, my knowledge is primarily focused on the out-of-the-box capabilities of Teams and Microsoft 365.

For a requirement like this, I would recommend opening a support ticket with Microsoft if possible. If you are an end-user, please kindly reach out to your Microsoft 365 administrator to perform these steps on your behalf.

A Microsoft support engineer can review your specific business requirements and advise on the most appropriate approach for designing and implementing such a solution. This is often the fastest and most reliable path, especially when you're looking for something scalable, supported, and tailored to your organization's needs.

Please note that this is a user-to-user support forum. I don't have access to Microsoft's internal diagnostic tools, backend systems, or your organization's environment, so my ability to validate or test a custom automation scenario is quite limited. I'm simply a fellow community member sharing information and suggestions based on available documentation and similar situations I've come across.

Thank you very much for your understanding, and I appreciate you taking the time to raise such a thoughtful question. I hope this information helps point you in the right direction.

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.