I'm using PRTG version 18.3.44.2059.

I am getting "HTTP/1.1 400 Bad Request" when send notification to Microsoft Teams.

Under Execute HTTP Action URL: URL of Incoming Webhook (Generate using connector) SNI: Do Not Send SNI HTTP Method: POST Payload: { "@context": "http://schema.org/extensions", "@type": "MessageCard", "themeColor": "0072C6", "title": "%device %name %status %down", "text": "%message\n %commentssensor", }

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Hello,

thank you for the KB-Post. Can you send me screenshot of your settings? Just to make sure, you not using the native teams notifications? May I ask why specifically.

best regards


Oct, 2018 - Permalink

No specific reason. Last time when I tried it didn't work. But works now with native MS team notification.

Thanks, Ekta


Oct, 2018 - Permalink

I have the same exact issue. HTTP/1.1 400 Bad Request in the logs when I try to send my HTTP Execute payload to my Teams webhook. I want a custom, smaller notification. I dont need a 5-6 line notification even with only Status selected on the native Teams notifications from PRTG. Teams makes every notification too big and this just makes it worse. Will there ever be an HTTPS Execute Action?


Jul, 2020 - Permalink

Why doesn't the HTTP Execute Action allow json? This is needed for Teams messages.


Jul, 2020 - Permalink