Merge pull request #289303 from ankitaduttaMSFT/asrdoc

asr eee

Author: prmerger-automator[bot]

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

@@ -5,7 +5,7 @@ author: ankitaduttaMSFT
 manager: aravindang
 ms.service: azure-site-recovery
 ms.topic: tutorial
-ms.date: 05/06/2024
+ms.date: 10/28/2024
 ms.author: ankitadutta
 ms.custom: references_regions
 ---
@@ -65,9 +65,7 @@ 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 can use the same IP addresses in the target zone if you choose to configure them that way.
-
-    When you use Azure Site Recovery, you must have a free IP address available in the subnet for each VM for which you want to use the same IP address in the target zone. During failover, Azure Site Recovery allocates this free IP address to the source VM to free up the target IP address. Azure Site Recovery then allocates the target IP address to the target VM.
+- **Private IP address**: If you're using static IP addresses, you cannot retain the same IP address in zone to zone failover.
 - **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.

articles/site-recovery/configure-mobility-service-proxy-settings.md

@@ -45,7 +45,8 @@ Mobility Service auto detects the proxy settings from environment settings or In
 
 ### Method 2: Provide custom application proxy settings
 
-In this case, the customer provides custom application proxy settings in Mobility Service config file ProxyInfo.conf. This method allows customers to provide proxy only for Mobility Service or a different proxy for Azure Site Recovery Mobility Service than a proxy (or no proxy) for rest of the applications on the machine.
+In this case, the customer provides custom application proxy settings in Mobility Service config file ProxyInfo.conf. This method allows customers to provide proxy only for Mobility Service or a different proxy for Azure Site Recovery Mobility Service than a proxy (or no proxy) for rest of the applications on the machine. Check whether the file `C:\ProgramData\Microsoft Azure Site Recovery\Config\ProxyInfo.conf` has any proxy entry. In case the file doesn't exist, create one.
+
 
 ## Proxy template
 

articles/site-recovery/hyper-v-azure-support-matrix.md

@@ -3,7 +3,7 @@ title: Support for disaster recovery of Hyper-V VMs to Azure with Azure Site Rec
 description: Summarizes the supported components and requirements for Hyper-V VM disaster recovery to Azure with Azure Site Recovery
 ms.service: azure-site-recovery
 ms.topic: concept-article
-ms.date: 09/18/2024
+ms.date: 10/28/2024
 author: ankitaduttaMSFT
 ms.author: ankitadutta
 ---
@@ -67,13 +67,14 @@ Guest VM network: NIC Teaming | No | No
 Guest VM network: IPv4 | Yes | Yes
 Guest VM network: IPv6 | No | Yes
 Guest VM network: Static IP (Windows) | Yes | Yes
-Guest VM network: Static IP (Linux) | No | No
+Guest VM network: Static IP (Linux) | Yes | Yes
 Guest VM network: Multi-NIC | Yes | Yes
 Https Proxy | No | No
 Automatic Private IP Addressing (APIPA) | No | No
 Private link access to Site Recovery service | Yes. [Learn more](hybrid-how-to-enable-replication-private-endpoints.md). | Yes. [Learn more](hybrid-how-to-enable-replication-private-endpoints.md).
 
-
+> [!NOTE]
+> For Guest VM network, static IP (Linux), Static IP from source OS's NIC is not used on Azure. The vNIC on Azure VM is configured with a new Azure IP of selected virtual network. 
 
 
 ## Azure VM network configuration (after failover)

articles/site-recovery/transport-layer-security.md

@@ -48,13 +48,11 @@ Use the following registry keys to configure .NET Framework that supports strong
 ```reg
 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
     "SystemDefaultTlsVersions"=dword:00000001
-    "SchUseStrongCrypto" = dword:00000001
-
-[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]
-    "SystemDefaultTlsVersions"=dword:00000001
-    "SchUseStrongCrypto" = dword:00000001
 ```
 
+> [!NOTE]
+> If the registry keys are absent, you don't need to create them for Windows Server 2012 R2 or later versions if TLS 1.2 is enabled in SChannel protocols.
+
 ## Frequently asked questions
 
 ### Why enable TLS 1.2?

articles/site-recovery/vmware-physical-azure-support-matrix.md

@@ -321,9 +321,10 @@ Azure virtual network service endpoints<br/> | Yes
 Accelerated networking | No
 
 ## Storage
+
 **Component** | **Supported**
 --- | ---
-Dynamic disk | OS disk must be a basic disk. <br/><br/>Data disks can be dynamic disks
+Dynamic disk | OS disk must be a basic disk. <br/><br/>Data disks can be dynamic disks. <br><br> Data disks can be spanned volumes.
 Docker disk configuration | No
 Host NFS | Yes for VMware<br/><br/> No for physical servers
 Host SAN (iSCSI/FC) | Yes