@Heeralal paliwal You need to allow both outboundIpAddresses
and possibleOutboundIpAddresses
as mentioned in this document if your storage and function app is in different region.
Please note that IP addresses can be changed in some scenarios as mentioned in the document.
To troubleshoot the error: "Azure Functions Runtime is unreachable" I will suggest reviewing this document which can help you in resolving the issue.
If you are still facing the issue then please let me know so we can connect offline to assist you further.
Update:
In case if the storage account and function app are in the same region then setting up function apps with restricted networks requires additional setup due to the way communication to storage irrespective of the subscription as mentioned in storage documentation.
To restrict access to Azure services deployed in the same region as the storage account.
Services deployed in the same region as the storage account use private Azure IP addresses for communication. Thus, you can't restrict access to specific Azure services based on their public outbound IP address range.
You can refer to Restrict your storage account to a virtual network for more details on how you can set up it. Please refer to the Note section that the consumption plan is not supported with this configuration.
This feature currently works for all Windows virtual network-supported SKUs in the Dedicated (App Service) plan and for Windows Elastic Premium plans. ASEv3 is not supported yet. It is also supported with private DNS for Linux virtual network-supported SKUs. Consumption and custom DNS for Linux plans aren't supported.