I have a Data Factory (v1) pipeline, Runbook, Integration Runtime and Automation triggered from my client's site by a webhook that has been working well for three years. The webhook is in date. Yesterday morning the webhook stopped triggering or even registering at the Azure end when triggered from the Client. When triggered via the same webhook from outside of the client, the whole process works fine, moving data to and from the client successfully.
To me this means that the IR is working correctly but something either on the client's network or on Azure services is now preventing the comms to Azure from the client but not from our network.
The webook is triggered by a single line of Powershell 'Invoke-RestMethod -Method Post -Uri "https://s9events.azure-automation.net/webhooks?token=<token>;"'
I have checked TLS settings on Internet options and 1.0, 1.1 and 1.2 are all ticked.
Your help in this is greatly appreciated and I am hoping that I am not the only person this has happened to.
Thanks and regards,
I should have added that the error message received is
"The error information returned by PowerShell is: 'The underlying connection was closed: An unexpected error occurred on a send. Authentication failed because the remote party has closed the transport stream."