Avoid public IP on worker VMs

[ortec-RW]

Hi

As we know, Veeam4Azure deploys 1 one more worker VMs to help with creating backups of Azure VMs. These worker VMs get assigned a region, VNet and Subnet. But they're also configured with a public-IP address.

How can I avoid this ?

During a FLR restore session, workers are also used to mount the data and extract the files for you via a Websession. There is an option to have this Websession not use public IP space, but private IP's within your Azure IaaS. Works fine. But that option is only for FLR restore.
The 'normal' worker VMs get deployed and removed automatically based on how many you need, in which region/Vnet/Subnet. But they all have a public IP address assigned. I don't think they even need this IP. Veeam doesn't communicate with it. It uses your IaaS networking or the VM Bus.
So I assume I can remove the Public IP from the workers, but new ones get deployed when needed and then get configured with public IPs again.

Is there any method to avoid workers to ever use any public IPs ?

Greetings,
Richard

[johan.h]

Private networking will be supported in v4 of Veeam Backup for Azure.

[Vitaliy S.]

Yes, v4 will allow you to achieve what you want. Currently, you cannot avoid that.