Webhook payload runon Azure vs Hybrid worker

Thanks for the suggestion; that's actually exactly the example I followed for my testing. I've added two webhooks, one running on Azure, the other one on a Hybrid Worker.

Sending the same JSON payload. Result is wildly different.

The Hybrid Worker one outputs the webhookdata as a System.String; which (obviously) won't work when doing the ConvertFrom-JSON

$Names  = @(
            @{ Name="Hawaii"},
            @{ Name="Seattle"},
            @{ Name="Florida"}
        )

$body = ConvertTo-Json -InputObject $Names

$testwebhookuriAZURE = "https://xxx.azure-automation.net/webhooks?token=xxx"
$testwebhookuriHW = "https://xxx.azure-automation.net/webhooks?token=xxxx"

Invoke-RestMethod -Method POST -Uri $testwebhookuriAZURE -Body $body
Invoke-RestMethod -Method POST -Uri $testwebhookuriHW -Body $body

Running on Azure outputs as PSCustomobject, and everything works as expected

ok. As I have mentioned I do not know why there is a difference as I do not use it but shouldn't converting it from JSON to PS object workaround the issue for hybrid workers?

The data is when using the Hybrid Works is not valid a JSON; hence nothing to (easily) convert.

I am now experimenting with regex removing the parts I do not need, leaving only the requestbody in a format which I can do a ConvertFrom-Json

Main point still remains why the data becomes a string on the HW instead of staying a psobject

Anyways, thanks for thinking along!

{WebhookName:onpremhook,RequestBody:[\r\n {\r\n "Name": "Hawaii"\r\n },\r\n {\r\n "Name": "Seattle"\r\n },\r\n {\r\n "Name": "Florida"\r\n }\r\n],RequestHeader:{Accept-Encoding:gzip,Host:1f7b5302-3e30-4141-972a-91d03321e62d.webhook.eus.azure-automation.net,User-Agent:Mozilla/5.0,x-ms-request-id:7cadfc0f-5b36-47fd-bca4-470a3aad2567}}

Hi!

I have excatly the same problem.

Have you found an easy solution for this bug?

Thanks, Jan