Azure Function: No such host is known Storage Account

Jesus Orlando Aguilar Contreras 40 Reputation points
2023-05-26T00:06:27.7533333+00:00

Hi everyone,

I have 2 Azure functions with VNet integration, and each of them has its own storage account. The first function is fine, but the second one generates this error when integrated into a network: Azure.Core: No such host is known. ([MyStorage].blob.core.windows.net:443). System.Net.Http: No such host is known. ([MyStorage].blob.core.windows.net:443). System.Net.Sockets: No such host is known.

I have no idea why, when integrating the function into a virtual network, it suddenly doesn't recognize the storage host, even though the storage has public access.

User's image

Has this happened to you? I would appreciate if you could provide guidance.

Thank you

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
3,018 questions
Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
1,834 questions
{count} votes

1 answer

Sort by: Most helpful
  1. VenkateshDodda-MSFT 9,376 Reputation points Microsoft Employee
    2023-05-26T11:24:41.6666667+00:00

    @Jesus Orlando Aguilar Contreras Thank you for reaching out to Microsoft Q&A, apologize for any inconvenience caused on this.

    As per the error message "Azure.Core: No such host is known. ([MyStorage].blob.core.windows.net:443). System.Net.Http: No such host is known." it looks like you function is communicating with storage account and not able to communicate.

    I have looked into the backend logs and I can see the same behavior that your function is not able to communicate with storage account I have further looked into the latest logs and I could see that your function is able to communicate with the storage account.

    I believe you storage account might be in virtual network or there might be any access restriction configured and which would have caused this issue. Do let me know if you are still facing the issue.

    Feel free to reach back to me if you have any further questions on this.

    0 comments No comments