Found a fix after going through the Microsoft Docs 1. https://learn.microsoft.com/en-gb/azure/storage/common/storage-private-endpoints?toc=%2Fazure%2Fstorage%2Fblobs%2Ftoc.json&bc=%2Fazure%2Fstorage%2Fblobs%2Fbreadcrumb%2Ftoc.json Answer is hidden in this - dns-changes-for-private-endpoints https://learn.microsoft.com/en-gb/azure/storage/common/storage-private-endpoints?toc=%2Fazure%2Fstorage%2Fblobs%2Ftoc.json&bc=%2Fazure%2Fstorage%2Fblobs%2Fbreadcrumb%2Ftoc.json#dns-changes-for-private-endpoints Once you create a private end point for the storage account. You should be able to resolve the private ip with a DNS Name. For Example Storage Account Name - StorageAccountA Private IP - 10.1.1.2 Storage Account DNS Name would be: StorageAccountA.blob.core.windows.net Now the trick is where ever you are configuring the addon, let say from your onprem server - 1. you should be able to resolve the DNS name to the Private IP from that server. 2. you should have the connectivity to the Private IP on port 443. 3. access keys to storage account Thats it, you can configure it on the addon and the connections will go through the private end point
... View more
