ADF linked service - unable to create connection with Azure function with approved managed Private Endpoint - An error occurred while sending the request. The remote name could not be resolved -

Venkatesan, Ashokkumar 0

User's image

The approved Managed PE should be displayed as soon as the function app i selected. it doesn't shows down or using the Managed PE in this linked service.

Venkatesan, Ashokkumar 0 Reputation points

2023-09-09T04:42:51.53+00:00

The managed private endpoint is approved and the function app is setup with Isolated V2 with ASE (appln service env).

While i perform the Resolve-DnsName yourfunctionapp.azurewebsites.net it gives back the host name.

I also tried with managed Identity. for all this connection, the final exception is The remote function name could not be resolved.
BhargavaGunnam-MSFT 26,226 Reputation points Microsoft Employee

2023-09-11T19:11:12.7533333+00:00

Hello Venkatesan, Ashokkumar,

Do you see the hostname with "Privatelink"(privatelink.azurewebsites.net)?

As you mentioned, the managed private endpoint is approved, and the function app is set up with Isolated V2 with ASE. The issue might be related to DNS resolution. The error message "The remote function name could not be resolved" indicates that the function app's DNS name could not be resolved. Please check the client is configured to use the correct private DNS zone and the private IP address assigned to the private endpoint.

Can you check if the function app is configured to use the correct VNet and subnet?

Please ensure the function app is configured to use the same VNet and subnet as the ADF Azure Functions linked service.

The document below provides a tutorial on creating a function app with VNet integration and private endpoints. It explains how to configure the function app to use the correct virtual network and subnet and ensure that the function app uses the correct private IP address assigned to the private endpoint.

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-functions/functions-create-vnet.md

To narrow down the issue, please try accessing the function app from a virtual machine connected to the same virtual network as the function app.

also please check if there are any permission issues to access the private endpoints.
BhargavaGunnam-MSFT 26,226 Reputation points Microsoft Employee

2023-09-12T16:09:18.5266667+00:00

Hello Venkatesan, Ashokkumar,

I am checking to see if you got a chance to look into my above response.
YANZHONG LIANG 0 Reputation points Microsoft Employee

2023-09-13T02:05:41.72+00:00

It might be a design issue, product team is investigating it.
Shukla, Vivek (SG/ITS-EA&E) 0 Reputation points

2024-04-14T15:08:07.2166667+00:00

is there any solution for this issue, I am also getting issue with App Service Environment hosted v3 hosted Logic App? Looking forwarded to know about workable solution. Thanks!

2 answers

BhargavaGunnam-MSFT 26,226 Reputation points Microsoft Employee

2023-09-08T20:43:45.0733333+00:00

Hello Venkatesan, Ashokkumar,

Welcome to the Microsoft Q&A forum.

It seems like the managed private endpoint has not been created, or It is not approved yet.

As a troubleshooting step, please run the below PS command to check the DNS resolution.

Resolve-DnsName yourfunctionapp.azurewebsites.net

If the PE is created and approved, you will see "Privatelink"(privatelink.azurewebsites.net) in the NameHost section.

Example screenshot for blob storage.

You will see "Privatelink" in the NameHost section for the function app.

Please see this reference document.

Understand private DNS zones:
https://learn.microsoft.com/en-us/azure/azure-functions/functions-create-vnet#understand-private-dns-zones

I hope this helps.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
LULAMA MBALI DLAMINI 0 Reputation points

2023-09-09T17:14:21.9033333+00:00

This site is really cool and thanks for the above comment which is assisting with the issues of troubleshooting
Please sign in to rate this answer.

0 comments No comments
Sign in to comment