Object Repository using Private Link

[collinp]

When creating a ScaleOut Repository and adding a Capacity Tier pointing to an Azure Storage Account, is there an option to point to a privatelink dns zone - StorageAccountName.privatelink.blob.core.windows.net? The only configuration options I see for a new Object Storage Account are Storage Account Name/Shared Key which defaults to StorageACcountName.blob.core.windows.net.

[Mildur]

Hi Collin

Moved your topic to object storage sub forum.
Private Link requires special configuration. Please have a look at this kb:
https://www.veeam.com/kb4373

Best,
Fabian

[collinp]

I read the article prior but it doesn't seem to address my question. My question was is veeam compatible with Azure private DNS zones? It looks like there is no place in the Veeam software to input the private dns zone StorageAccountName.privatelink.blob.core.windows.net. It looks like there is a workaround to modify the hosts file on the gateway server. Will there be direct integration between Veeam and Azure private dns zones in the future? I'm not a huge fan of host entries but it will work for now.

[Mildur]

DNS resolution must configured outside of Veeam.
I believe you can work with creating a copy of the DNS zone on your own managed DNS server for the local machines, instead of using host files.

Or maybe this service from Azure can help:
https://learn.microsoft.com/en-us/azure ... r-overview

Azure DNS Private Resolver is a new service that enables you to query Azure DNS private zones from an on-premises environment and vice versa without deploying VM based DNS servers.

Best,
Fabian