Is there any plan to support manually‑instantiated recurring Teams meetings that preserve the same meeting chat without fixed cadence?

Hi @Turton,

Thank you for sharing this. It is a very thoughtful and well‑articulated idea.

I have also added my vote to your feedback, as I agree this would be a meaningful improvement. The concept of “share the chat” across a series of manually scheduled meetings strikes a strong balance between maintaining meeting‑level governance and providing continuity across related sessions. The comparison to recurring meetings with a regular cadence clearly highlights the value and makes the use case easy to understand.

You have taken the right step by submitting this through the Feedback Portal, and the link you shared is the appropriate channel for product suggestions of this nature. Feedback submitted there is reviewed and tracked by the product team and plays an important role in shaping future roadmap decisions, especially as it gains engagement from other customers.

In addition, you are also welcome to share this post within the community so that other users can more easily discover your idea. This helps surface the solution for those who may be searching for similar guidance, and your contribution not only supports fellow users in finding relevant information more quickly, but also helps foster a more resourceful and collaborative community overall.

You and your colleagues may submit suggestions directly through the Teams application by navigating to: Settings and more > Feedback > Suggest a feature. 

If this helps, please consider upvoting and accept the answer so others can find the guidance quickly.

Thank you again for taking the time to share your feedback. I truly hope it gains more visibility and helps bring attention to the topic.

Hi @Turton,

I hope you’re having a great day. 

Based on the information you provided, you are looking for a way to host a series of meetings without a fixed schedule while maintaining a single, continuous chat history, consistent participant list, and unified meeting settings across all sessions.

After reviewing your request, I’d like to clarify that Microsoft Teams does not currently support this scenario natively. Chat continuity can only be preserved through standard recurring meetings or meetings scheduled within a specific Teams channel. At this time, independently scheduled or ad-hoc meetings cannot be linked to share a common chat thread, as this capability is not supported by the platform’s underlying infrastructure.

I agree that this type of functionality would offer meaningful flexibility for advanced and dynamic workflows. For that reason, I encourage you to submit your feedback through the Microsoft Feedback Portal. This channel allows product and engineering teams to directly review customer suggestions and helps inform decisions on future feature development. Detailed use cases such as yours provide valuable context for evaluating potential enhancements.

Additionally, as other users have raised similar concerns and may not be aware of where to share their feedback, I hope this response helps clarify the situation and suggests a potential next step. Upvoting this information can make it more visible to others in the community who may be facing the same issue, making it easier for them to find guidance and contribute their feedback as well.

As a forum moderator, my role is limited to confirming current product behavior and offering technical clarification. Since this is a core product limitation, I’m unable to adjust the service or manually consolidate meeting data.

Thank you for taking the time to share your perspective. Your feedback is valuable, and I appreciate your proactive approach to advocating for improvements that support more complex organizational needs.

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.

No. Teams meetings do not currently support a manually instantiated “create next occurrence” model that keeps a single continuous chat thread without a fixed recurrence pattern.

From the available behavior:

• For standard recurring meetings with a defined cadence, all occurrences share the same meeting chat, and the chat continues from one meeting to the next for participants included in the series invite.
• If a participant is removed from the recurring meeting series, that participant loses access to the shared chat.
• People invited only to a single occurrence in a recurring series can participate in the chat for that occurrence but do not see prior chat history.
• Channel meetings use the channel’s Posts/Conversations thread as the meeting chat, which is persistent, but this is tied to the channel, not to an ad‑hoc, manually instantiated series identity.

There is no documented option to:

• Define a meeting “series identity” without a recurrence pattern, and
• Manually spawn new occurrences that all bind to the same non‑channel meeting chat container, while
• Keeping attendees and meeting options in sync automatically.

Meeting templates and organizer/admin options can control whether chat is available and whether it’s allowed before/after meetings, but they do not change the underlying model of how recurring vs. single-instance meeting chats are created and bound.

References:

• Chat in Microsoft Teams meetings
• Plan for Teams meetings
• Overview of custom meeting templates in Microsoft Teams
• Reduce or replace meetings with asynchronous methods in Microsoft Teams