0

we configured Service Hooks notification with old version of Webhooks (starting with https://outlook.office.com/...) before to send notification to Microsoft Teams, which were working fine. However, the new format of Webhooks (starting with https://[hostname].webhook.office.com/...) in Teams is not working in Service Hooks anymore. I always get Bad Request error (400). Anyone has similar issue and get a solution here? I compared the request from both URLs and didn't find any difference rather than the IDs.

enter image description here

oicqhf
  • 1
  • 1
  • Could you please provide any repro steps or more details to check the issue? – Prasad-MSFT Feb 28 '22 at 12:09
  • I think I found the root cause from the detailed response with Postman. "Summary or Text is required" is the exact error message. When I added Summary or Text into the request, everything works fine. So it seems Azure Pipeline service hook event doesn't provide these values. Two questions are: 1. How can this be resolved? 2. Why the old webhook URL doesn't require these two values? – oicqhf Feb 28 '22 at 12:51
  • @Prasad-MSFT, does that mean there is no way to use Webhooks to push notification from Pipeline to Microsoft Teams? So we have to use Azure Pipeline app instead? – oicqhf Mar 01 '22 at 15:14
  • We have raised an ICM for the same, the team is looking into it. We will inform you once we have any update. – Meghana-MSFT Mar 03 '22 at 07:43
  • Could you please confirm whether the "Summary and Text" field is present when notification is sent to old webhook URL. These field seems to be a required field, and could you please compare payload in both scenario? – Prasad-MSFT Apr 04 '22 at 08:29

0 Answers0