HTTPS NameResolutionFailure

Diego Juanes 21 Reputation points
2022-04-18T18:07:25.273+00:00

Hi. I'm testing Logic Apps and I'm getting this error:
UnresolvableHostName. Http request failed with status code 'NameResolutionFailure' and status message: 'The remote name could not be resolved: ...
The scenario is as follows:
When a blob is added to a certain container, it triggers an http. The https address is from a web app deployed in a container

Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
2,949 questions
{count} votes

Accepted answer
  1. Takahito Iwasa 4,841 Reputation points MVP
    2022-04-19T20:32:11.25+00:00

    Hi, @Diego Juanes

    I understand that you want to act on the HTTPS endpoint (self-signed) of a private container with the trigger that Blog was added to Logc Apps, but it is failing.

    The following pages mention scenarios where you can use self-signing when making outbound calls in Logic Apps.

    https://learn.microsoft.com/en-us/azure/logic-apps/logic-apps-securing-a-logic-app?tabs=azure-portal#access-for-outbound-calls-to-other- services-and-systems

    • For Consumption logic apps in the multi-tenant Azure Logic Apps environment, HTTP operations don't permit self-signed TLS / SSL certificates.
    • For Standard logic apps in the single-tenant Azure Logic Apps environment, HTTP operations support self-signed TLS / SSL certificates. However, you have to complete a few extra steps for this authentication type.

    If you are Standard logic apps (single-tenant), please refer to the following and double check if the settings are correct.

    https://learn.microsoft.com/en-us/azure/connectors/connectors-native-http#tlsssl-certificate-authentication

    0 comments No comments

0 additional answers

Sort by: Most helpful