"Create a Meeting" to a Teams channel creates two separate chats

[ChristopherP]

Hello,

My team is very synchronous in nature and covid has forced us to adapt.  With Teams, we actually have a 24/7 meeting which we "refresh" at the start of each month via Power Automate.  The Power Automate flow and steps work just fine.  The meeting is created, an invite goes out to our team distribution list and an adaptive card with the "joinURL" is posted to our internal Teams channel.  However, I recently learned the "chat" within the conference meeting is not at all the same chat that gets created below the "adaptive card" that I am using to post the new meeting in our Teams chat.  Does anyone know how I can make these chats one in the same? 

My desired outcome is if someone on the voice call types within the meeting's chat, their messages show up in the same thread in our Teams channel underneath the adaptive card which has the link to the meeting.  Today, if someone types within the meeting chat, the messages are not visible from the Teams thread.  The opposite is also true.  If someone types into the Teams thread, you cannot see those messages within the conference meeting.  This is resulting in more context switching than is necessary.

Screenshot of the current flow:

[AnthonyAmador]

Hi @ChristopherP 

I understand what you are trying to achieve, however the thing is that there is no way to sync a meeting chat with a group channel, I was looking also if there is a trigger for when someone posts a message in a meeting chat, though it seems that there is no something like that, anyway if it were possible from my point of view I believe it can be unproductive because you are going to create a thread for each message published in the meeting chat, which could be many threads that end up as spam on the team channel. 

My recommendation in this case is to create a new flow using the "For a selected message" trigger, so if there is a message in the meeting chat important enough to create a thread, you can create it just by clicking on that message. 

For example something like this.

Here is also a link about how to use this action. 

Trigger flows from any message in Microsoft Teams | Power Automate Blog

Hope this helps.

Kind regards. 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[ChristopherP]

Thanks for the response @AnthonyAmador!  The ask is not to create a net new post each time someone responds in the meeting chat.  The goal would be to have the messages show up in-line under the same top-level post.  This is preferred because message leap-frogging is a nightmare when there's a requirement to have a synchronous chat with easy to comprehend timestamps of who said what and when.

So, the result would be something like this.  Except, instead of me talking to myself, there'd be a full team of people responding and interacting via the chat.  Ultimately, I want to eliminate the need to context switch.  Since everyone is already in the meeting, asking them to use a second window to send screenshots, links, code blocks, etc. is less than ideal.  Having a "meet now" capability via power automate would solve this problem well, I think.

[AnthonyAmador]

Now I understand, well, we still have the same issue with the trigger, there are no triggers for MS Teams that might be useful here, the only one I see more accurate is the one I mentioned before, and it should be triggered manually for each message. 

To reply to the message in a channel, you can use the action "Reply with a message in a channel", what happens is that you need the message ID, so every time you create a thread you should save the message ID somewhere to use it. 

I think that the functionality you mention could be very useful not only for you but also for other users, so I encourage you to submit your idea in the ideas forum.

 Power Automate Ideas - Power Platform Community (microsoft.com) 

That way the product team could know your requirements and why it's useful, also get voted on for other users in the community, we love hearing feedback from our customers on how we can improve our tools. 

Take care. 

Kind regards.