Merge pull request #225317 from Sharmistha-Rai/main

cred-less and doc bugs

Author: American-Dipper

articles/site-recovery/failover-failback-overview-modernized.md

@@ -90,6 +90,7 @@ After failover to Azure, the replicated Azure VMs are in an unprotected state.
 - As a first step to failing back to your on-premises site, you need to start the Azure VMs replicating to on-premises. The reprotection process depends on the type of machines you failed over.
 - After machines are replicating from Azure to on-premises, you can run a failover from Azure to your on-premises site.
 - After machines are running on-premises again, you can enable replication so that they replicate to Azure for disaster recovery.
+- Only disks replicated from on-premises to Azure will be replicated back from Azure during re-protect operation. Newly added disks to failed over Azure VM will not be replicated to on-premises machine. 
 
 **Planned failover works as follows**:
 

articles/site-recovery/media/vmware-physical-mobility-service-overview-modernized/credential-less-discovery.png

@@ -112,7 +112,7 @@ Follow these steps to enable replication:
 
 4.	Search the source machine name to protect it. To review the selected machines, select **Selected resources**.
 
-5. After you select the list of VMs, select **Next** to proceed to source settings. Here, select the replication appliance and VM credentials. These credentials will be used to push mobility agent on the machine by Azure Site Recovery replication appliance to complete enabling Azure Site Recovery. Ensure accurate credentials are chosen.
+5. After you select the list of VMs, select **Next** to proceed to source settings. Here, select the [replication appliance](#appliance-selection) and VM credentials. These credentials will be used to push mobility agent on the machine by Azure Site Recovery replication appliance to complete enabling Azure Site Recovery. Ensure accurate credentials are chosen.
 
    >[!NOTE]
    >For Linux OS, ensure to provide the root credentials. For Windows OS, a user account with admin privileges should be added. These credentials will be used to push Mobility Service on to the source machine during enable replication operation.
@@ -165,6 +165,10 @@ Follow these steps to enable replication:
 
     A job is created to enable replication of the selected machines. To track the progress, navigate to Site Recovery jobs in the recovery services vault.
 
+## Appliance selection
+
+- You can select any of the Azure Site Recovery replication appliances registered under a vault to protect a machine.
+- Same replication appliance can be used both for forward and backward protection operations, if it is in a non-critical state. It should not impact the performance of the replications.
 
 ## Next steps
 After enabling replication, run a drill to make sure everything's working as expected.

articles/site-recovery/vmware-azure-set-up-replication-tutorial-modernized.md

@@ -318,9 +318,9 @@ Locate the installer files for the server’s operating system using the followi
 
 5. Copy the string present in the field  **Machine Details**.
 
-   This field includes information unique to the source machine. This information is required to [generate the Mobility Service configuration file](#generate-mobility-service-configuration-file).
+   This field includes information unique to the source machine. This information is required to [generate the Mobility Service configuration file](#generate-mobility-service-configuration-file). Learn more about [credential less discovery](#credential-less-discovery-in-modernized-architecture).
 
-   ![Image showing source machine string](./media/vmware-physical-mobility-service-overview-modernized/source-machine-string.png)
+   ![Screenshot showing source machine string.](./media/vmware-physical-mobility-service-overview-modernized/source-machine-string.png)
 
 6.	Provide the path of **Mobility Service configuration file** in the Unified Agent configurator.
 7.	Click **Register**.
@@ -414,10 +414,17 @@ Syntax | `"<InstallLocation>\UnifiedAgentConfigurator.exe" /SourceConfigFilePath
 
   Setting | Details
   --- | ---
-    Syntax | `<InstallLocation>/Vx/bin/UnifiedAgentConfigurator.sh -c CSPrime -S config.json -q`  
-    `-S` | Mandatory. Full file path of the Mobility Service configuration file. Use any valid folder.
+    Syntax | `<InstallLocation>/Vx/bin/UnifiedAgentConfigurator.sh -c CSPrime -S config.json -q -D true`  
+    `-S` |  Mandatory. Full file path of the Mobility Service configuration file. Use any valid folder.
     `-c` |  Mandatory. Used to define modernized and legacy architecture. (CSPrime or CSLegacy).
     `-q` |  Optional. Specifies whether to run the installer in silent mode.
+    `-D` |  Optional. Specifies whether credential-less discovery will be performed or not. 
+
+## Credential-less discovery in modernized architecture
+
+When providing both the machine credentials and the vCenter server or vSphere ESXi host credentials is not possible, then you should opt for credential-less discovery. When performing credential-less discovery, mobility service is installed manually on the source machine and during the installation, the check box for credential-less discovery should be set to true, so that when replication is enabled, no credentials will be required. 
+
+![Screenshot showing credential-less-discovery-check-box.](./media/vmware-physical-mobility-service-overview-modernized/credential-less-discovery.png)
 
 ## Generate Mobility Service configuration file