Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
3,388 questions
Issue with Azure Logic Apps Custom Connector - SSL Connection Issues
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(217.60000000000002, 5%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
Abhishek Mittal
0
Reputation points
Creating Logic Apps workflows and a Custom Connector in the same subscription and VNET where inbound and outbound rules are enabled for connectivity.
Facing an SSL connection issue using the Azure Logic Apps Custom Connector created based on the Open API 3.0 Swagger file while trying to connect to the Apigee environment and its proxy services.
When using the Custom Connector to call an Apigee API from the Logic Apps workflow, the following error occurs:
"BadRequest
Http request failed as there is an error: 'The SSL connection could not be established, see inner exception.'"
However, when using the in-app HTTP adapter to call the same Apigee API from the same Logic Apps workflow, the connection works and the expected response is received.
Seeking advice on why the in-app HTTP adapter works, but the Custom Connector does not, despite both being in the same Azure subscription, resource, and VNET. Any resolution would be appreciated.
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 39%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELM%3C/text%3E%3C/svg%3E)
Loknathsatyasaivarma Mahali 710 Reputation points Microsoft External Staff2025-03-07T00:12:12.8566667+00:00 Hello Abhishek Mittal,
Thanks for posting your concern in Microsoft Q&A platform.
To gain a better understanding of the issue and investigate it further, could you please confirm on the following details?- Have you verified the SSL certificate used by the Apigee API, including its validity and whether it is trusted by the Logic Apps environment?
- Have you tested the Custom Connector with any specific configurations (such as authentication methods, headers, or query parameters), and can you provide details on those configurations?
-
Abhishek Mittal 0 Reputation points
2025-03-07T07:28:23.3466667+00:00 Hello,
Certificates are valid and trusted between Azure and Apigee environments. That is the reason how HTTP in-app adapter for Apigee call.
Even I have imported Trusted certificates of Apigee in Logic Apps environment but same issue.
We have tested the Authentication but failed.
One more strange behavior observed. We created a dummy workflow in same subscription and exposed as REST. We configured this dummy workflow REST in Custom Connector and guess what, same issue.
Even Custom Connector is not working for workflows exposed as REST with the same Azure Logic Apps environment. Definitely, some configuration missing to make Custom Connectors work.
-
VenkateshDodda-MSFT 24,056 Reputation points Microsoft Employee2025-03-07T09:12:26.91+00:00 @Abhishek Mittal thanks for posting your question in Microsoft Q&A, apologize for any inconvenience caused on this.
Could you please check the certificate thumbprint is correct or if not try adding the certificate to logic app by following the documented steps here : https://docs.azure.cn/en-us/connectors/connectors-native-http?tabs=consumption#authentication-for-single-tenant-environment
load private certificate : https://docs.azure.cn/en-us/app-service/environment/certificates#tls-settings
-
Sonny Gillissen 3,591 Reputation points2025-03-09T21:02:23.62+00:00 Hi Abhishek Mittal,
Thanks for reaching out on Microsoft Q&A!
I think this issue occurs because of the fact that Custom Connector traffic is proxied through an other service endpoint which may not accept the trust, whereas your in-app HTTP action performs an actual direct call (thus work properly).
My advise would be to add in an API Management Service in between for the connection to Apigee, and create the trust between those two. The create your Custom Connector based on the OpenAPI spec that you can download from the API Management Service.
With that said: having an API Management Service in place is the best-practice from Microsoft, which can handle these sort of tasks and solve issues with (offloading) SSL and such.
Please click ‘Accept answer’ if you think my answer is helpful. Feel free to drop additional queries in the comments below!
Kind regards,
Sonny
Sign in to comment
Sign in to answer