Hi Alekhya
Thanks for reaching out on Microsoft Q&A!
Inbound and outbound differ in such a way that inbound traffic is triggered from the source and outbound is triggered from the logic app. The receiving party determines the protocol to be used, like TLS. Maybe the TLS version on the outbound is 1.2, supported by the destination, but inbound is set to 1.3, not supported by the source.
Here are a few possibilities to check:
- Even though you've uploaded all required certs, make sure the inbound flow is correctly referencing them and that no intermediate certificates are missing. Sometimes, SSL errors arise due to an incomplete chain.
- Confirm the TLS version being used in your inbound logic app matches what the external system expects. Azure Logic Apps typically use TLS 1.2 by default, but check if there's a mismatch.
- Even with IP whitelisting, some network security policies might block SSL connections for specific inbound scenarios.
If you're still stuck, you might want to test using a tool like OpenSSL or Postman to see if a direct request to the external system encounters the same SSL issue outside of Logic Apps. This could help pinpoint whether it's an Azure-specific configuration issue or something on the external system’s side.
Please click ‘Accept answer’ if you think my answer is helpful. Feel free to drop additional queries in the comments below!
Kind regards,
Sonny