Imagine when you receive millions of events per day -- the ones that arrive out of order, the days when delivery time goes up and up again, the days when oauth fails renewing keys... it's meant to be a lot of fun.

Compare to a sad websocket that just stays connected, you receive everything in order and you don't need an harness with tunnels every time you want to test something in dev.

> Why do I have to create a weird "workflow" to receive webhooks in a chat channel?

Create the webhook in Microsoft Flow and connect it to Teams. You get observability and monitoring out-of-the-box.

Well, if you are stuck with M365, that may be the explanation. There's little market pressue on Teams.