Hello,
We're trying to setup the Azure Storage account from the add-on and we're getting authentication failure. Credential is working fine when test using Azure Storage Explorer. Only difference is client environment has certain policy. It started to work when they add the respective VNET/Subnet in storage firewall while failing with authentication error over storage account private endpoint.
Does app can support storage account connectivity through specific storage services private endpoint? from configuration perspective, we can only define the storage account name and access key.
Thanks.
Even i do have the same requirement.
Connect to Storage Account via private endpoint dns name rather than storage account name.
Found a fix after going through the Microsoft Docs
Answer is hidden in this - 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