Hi @Thakkar, Bunty ,
Welcome to Microsoft Q&A Platform. Thank you for the question.
It seems HTTP connectors do not use gateway so you cannot establish connection & custom connectors do not support Cookies. So I would suggest you to explore the Azure Function App to make the HTTP request with Cookies.
Also, you can check the similar discussion in below thread, and highlighting the points for your reference,
- HTTP action does not support on-premise data gateway, so the hostname or ip could not be resolved because the HTTP action always talks to public network.
- If you could use custom connector to connect to on-premise data gateway, you should not get the unresolvedhostname issue. However, the custom connector does not support Cookie authentication, that’s why you could not get it through.
- One workaround is using application gateway to reverse proxy services and publish your on-premise server to public. It would act like an VPN and you could use HTTP action in logic app to establish connection.
- Another workaround is trying to use Function App to make the HTTP request with Cookies
Regards,
Kamlesh Kumar
Please don't forget to click on or upvote button whenever the information provided helps you. Original posters help the community find answers faster by identifying the correct answer. Here is How
Want a reminder to come back and check responses? Here is how to subscribe to a Notification
If you are interested in joining the VM program and help shape the future of Q&A: Here is how you can be part of Q&A Volunteer Moderators