How To Prevent Enter Key From Sending Chat Message

I just came here almost 2.5 years after this original question was posted because this is still a problem. It drives me crazy that huge tech corporations say that they listen to their customers - evidence in point that they absolutely do not listen to us at all. It is ridiculous to have the return key send the message - it leads to rework and frustration.

This is one of the only comments here that makes any sense. Workarounds do not solve this issue and most definitely avoid addressing the elephant in the room. This is a catastrophic feature deletion. We used to be able to disable "Enter as send". Some employee has actively made a decision to completely wreck the product by making Enter trigger the send button. It is way beyond bad, it's quite sinister. You don't do this by accident; you definitely don't do this if you have a level of rational intelligence. You only do this deliberately and vindictively. It's deeply concerning because this is not a joke; it's a serious tool being used as someone's idea of a prank, possibly quite high up to get this signed off. I think we need a deeper investigation into those responsible for this, and they need to be named and investigated.

I found the flaw in the simple script above. There is a side-effect that bullet and number lists no longer work like you would think.

In those formatting modes, enter means new bullet, shift enter means a break in the current bullet.

I haven't been able to find a programmatic way to know which of the two entry modes teams is using to fix this. I choose to workaround by typing the list, then adding the formatting afterwards, because for me that is a rare event, but sending an incomplete message wasn't.

Thanks to the comment by Adam Lemmon above, this autohotkey 4-liner fragment has been saving my sanity for a couple weeks now. My fingers are learning to remember ctrl-enter is send. Wrap it in proper ahk script and be happy.

Note that although the window class is TeamsWebView, I am using the desktop client. As written it won't do anything for Teams in a web browser.

;Teams Chat cursed enter key workaround using autohotkey v1.1 
;Teams behaviour:

;  ctrl-enter always sends 

;  shift-enter always line feeds 

;  enter is _cursed_ because it changes functions depending on text entry decoration
;

;Solution: map enter -> shift-enter 

;            leave shift-enter 

;            use ctrl-enter to send 
;            spend more time & bytes writing comments rather than script commands

;
;originally this script checked for 'Chat' to be in the title, but that test breaks 

;when I 'Open chat in new window'.  So far, it seems that shift+enter and enter have the same  

;function in every other Teams window I use regularly. 

#IfWinActive ahk_class TeamsWebView 

enter:: 

  send +{enter} 

  return

It's been over two years since this question was asked and Microsoft still hasn't implemented a default setting. No wonder everyone hates Teams.