The "Bad request for url..." verbiage typically points to an invalid webhook address. Make sure the URL of the webhook is publically accessible, is addressable with HTTPS, and doesn't contain any pr...
See more...
The "Bad request for url..." verbiage typically points to an invalid webhook address. Make sure the URL of the webhook is publically accessible, is addressable with HTTPS, and doesn't contain any private certificates in the chain. This Lantern article (with a video walkthrough) may be helpful => https://lantern.splunk.com/Data_Descriptors/Microsoft/Getting_started_with_the_Microsoft_Teams_Add-on_for_Splunk As, an alternative, you can use Azure Functions to get the same call record data. This way, you don't have to have the webhook on your forwarder. Instead, all the plumbing happens in Azure and the data is pushed to Splunk via HEC. Here is a Lantern article on that => https://lantern.splunk.com/Data_Descriptors/Microsoft/Getting_started_with_Microsoft_Teams_call_record_data_and_Azure_Functions