Power Platform Community Forum Thread Details

New URL causing request from Azure function to HTTP triggered flow to fail

I have a HTTP triggered power automate flow that is set to allow requests from anyone in my tenant. I trigger the flow from an azure function, which has worked fine, until I updated the URL to the new URL that has been announced by Microsoft.

Now I am no longer able to trigger it, and get these errors:

2025-10-15 14:20:59

Error sending data to Power Automate flow: The SSL connection could not be established, see inner exception.

2025-10-15 14:20:59

An existing connection was forcibly closed by the remote host.

2025-10-15 14:20:59

Result: Failure Exception: System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception. --- System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.. --- System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host. --- End of inner exception stack trace ---

------------------------------------

If i switch back to the old URL it still works, so there must be some change that Microsoft has made in the background that is causing these errors. I am using .NET 8 in my Azure function.

How can I get around it?

Categories:

Process Advisor

Quick Links