■ Virtual machines with managed disks attached.

■ Retention is not supported in Azure.

■ Resizing of protected disks in Azure is not supported and recovery disks are not auto-resized. If you resize the protected disk from Azure, the VPG will be stuck in a Needs Configuration state until the resized disk, VM, or VPG is removed.

■ When Reverse Protection is configured, in the Recovery step of the wizard the VPG and VM default network settings are configured as if a new VPG to Azure was created. The original VM network settings of the on-premise VPG are not reproduced in the VPG network settings in reverse protection configuration.

■ When creating or editing a VPG from Azure to vSphere or Hyper-V, re-IP of the NIC configuration is supported only if VMware Tools (vSphere) or Microsoft Integration Services (Hyper-V) are available for each virtual machine in the VPG, in which case the IP address of the originally protected virtual machine is used.

■ Protection can be set up to enable recovery to a point in time, up to 30 days prior to a disaster.

■ Azure local SSD disks, which are created with the virtual machine but not provisioned to the virtual machine, are not protected.

■ Boot order configuration for virtual machines recovered from Azure to on-premise sites is supported.

■ When a VM is recovered to Azure, a temporary drive is automatically created in the drive letter following the OS drive. Due to this temp drive, the non-OS drives you had set up in your production site may be shifted when recovered to Azure.

■ Every block blob, page blob and Managed disks that are created by Zerto, are Encrypted at Rest on the Microsoft Azure platform, using the Microsoft-managed default key.