Static IP

Author: Ankita Dutta

articles/site-recovery/azure-to-azure-how-to-enable-zone-to-zone-disaster-recovery.md

@@ -64,7 +64,9 @@ As mentioned before, zone-to-zone disaster recovery uses redundant networking co
 
 - **Virtual network**: You can use the same virtual network as the source network for actual failovers. For test failovers, use a virtual network that's different from the source virtual network.
 - **Subnet**: Failover into the same subnet is supported.
-- **Private IP address**: If you're using static IP addresses, you cannot retain the same IP address in zone to zone failover.
+- **Private IP address**: If you're using static IPs, you can use the same static IPs for the failed over VM once failover completes. Ensure the source VM’s private IP is static before enabling Site Recovery. You must have a free IP in the same subnet (different from the source IP). When failover is triggered, Site Recovery assigns the free IP to the source VM, freeing the source IP for use. 
+    > [!NOTE]
+    > You can use the same source IP for the target VM only if you choose to shut down the source VM during failover. Shutting down the VM helps to dissociate the original IP.
 - **Accelerated networking**: Similar to Azure-to-Azure disaster recovery, you can enable accelerated networking if the VM type supports it.
 - **Public IP address**: You can attach a previously created standard public IP address in the same region to the target VM. Basic public IP addresses don't support scenarios related to availability zones.
 - **Load balancer**: A standard load balancer is a regional resource, so the target VM can be attached to the back-end pool of the same load balancer. A new load balancer isn't required.