267

Author: Ankita Dutta

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

@@ -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

@@ -55,6 +55,9 @@ Use the following registry keys to configure .NET Framework that supports strong
     "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?