This is still under review. It looks like ensuring merging would work as you would expect, has a lot of underlying parts. The team is working to under the full impact of taking this request.
I hope to have more feedback soon.
-Warren

I came on here to as for exactly this, thank you to the person that already raised it.

This is definitely a problem - I often see people starting new conversations when they should be replying to existing ones. Its clearly an accident on their part but given it happens so often (and believe me, it does) I'm led to believe that the UI is somewhat to blame. Its not just novice users that do it either, I've seen extremely IT-literate people that are experienced in using Teams making the same mistake.

I find the problem occurs more often when people are replying via a phone app, the distinction there between replying to a new conversation starting a new one is less pronounced.

I think the ability to merge conversations together would be really useful. I suggest the following rules around it:
- 2 conversations can only be merged if they are in the same channel
- Conversation merging can only be done either by the person that started the conversation that is going to be merged, or by a team owner
-If the two conversations each have many messages then the resulting merged conversation might be even messier than when they were separate (due to messages from both conversations being mixed together). The person doing the merge should have the opportunity to preview what the merged conversation would look like.

Another need for this arose today. I'm having a discussion on a pull request in a gitlab repo. There was a conversation in Teams a few weeks ago that pertains to the discussion being had in gitlab but there's no way of referencing that Teams conversation. All I need is URL (aka a permalink) to that conversation which I can include in the gitlab pull request.

Please...we need URLs (aka permalinks) for conversations and messages permalinks. URLs for deeplinking are the currency of the web, they make the web what it is...its so disappointing that Teams does not support them.

This happens for me also. I think (but can't be certain) that I only receive such notifications on my phone (with is an iOS device). In other words, in the desktop app I am not receiving notifications for Teams that I used to be a member of, but I *am* receiving those notifications in iOS.

I like this idea a lot. When I'm using the mobile app I want to share my location with my colleagues - would be invaluable for a mobile workforce. My iphone allows me to share my location with anyone I want and I use that to share my location with my family. I don't want to share my lcoation with my colleagues all the time though, so make it a feature of Microsoft Teams and allow me to specify which times of the day my location should be shared.

It might even be a way for a company to passively monitor the location and travel history of their workforce. Make it mandatory for members of a Team to share their location (or perhaps make it a condition of joining a Team). Of course, a company should only be able to monitor their employees' location during work hours, and this feature should reflect that.

I suspect there are loads of scenarios where this would be valuable. For example, a logistics company could know where all its delivery drivers are at any one time by plotting their locations in a Microsoft Teams tab.