Cloning a VPG to Azure : The Clone Process
  
The Clone Process
Use the Clone operation to create a copy of virtual machines on the recovery site. The virtual machines on the protected site remain protected and live.
The Clone operation has the following basic steps:
Creating the cloned disks at the recovery site with the data from the journal to the specified checkpoint.
Creating the virtual machines at the recovery site in the move/failover network and attaching each virtual machine to its relevant cloned disks, configured to the checkpoint specified for the clone.
Note: The virtual machines are created without CD-ROM or DVD drives, even if the protected virtual machines have CD-ROM or DVD drives.
The cloned machines are named with the names of the protected machines, with the timestamp of the checkpoint used to create the clone. The cloned virtual machines are not powered on and are not protected by Zerto Virtual Replication.
When you create a virtual machine in Azure you are provided with a temporary volume automatically. This temporary storage is D: on a Windows virtual machine and it is /dev/sdb1 on a Linux virtual machine.
Temporary volume size varies according to the instance size you have selected.
On Windows, the temporary volume will be using the next available drive letter.
For example: If you have two volumes connected to the protected virtual machine, Azure will use C and D, and allocate E for the temporary volume drive.