I have a function trying to access blob storage but giving error when trying to see in Azure

@Kaipa Venkata Sreedhar Reddy

It seems like you're facing a connectivity issue with your Azure Function trying to access Blob Storage, specifically the error message indicating "No such host is known." Here are a few troubleshooting steps you can take:

Check Connection String: Ensure that your connection string in the function's application settings is correct and includes the blob endpoint. You can verify this by going to the Azure portal, navigating to your storage account, and copying the connection string from the Access keys blade.

Configuring App Settings: Double-check the app settings for your function in the Azure portal. Make sure the connection string there references the correct storage account and that there are no typos.

Networking Issues: Make sure there are no networking issues or VNet restrictions that might prevent your function from reaching the Blob Storage.

Validate Environment: Since everything works in lower environments but fails in production, confirm that the production deployment has correctly inherited or set the required environment variables and connection strings.

Logs and Error Details: Check the function app logs for more detailed error messages. The logs can provide insight into whether the iss

I have checked all the settings and both are in same VNET and double verified the connection strings as well still same issue

@Kaipa Venkata Sreedhar Reddy

Thank you for the update.

Since you've confirmed that the Azure Function and the Storage Account are in the same VNet and the connection strings are correctly configured, the issue might be related to the VNet integration settings of the Function App.

To address this, please add the following application settings in your Function App (under Configuration > Application settings):

vnetRouteAllEnabled = 1  
vnetContentShareEnabled = 1

These settings ensure that all outbound traffic, including traffic to Azure services like Blob Storage, is correctly routed through the integrated VNet.

After adding these settings, please restart your Function App and check if the issue persists.