Add guidance for setting up AUTOMATED_REGISTER in HANA scale-up docs

Author: rdeltcheva

articles/virtual-machines/workloads/sap/sap-hana-high-availability.md

@@ -10,7 +10,7 @@ ms.service: virtual-machines-sap
 ms.topic: article
 ms.tgt_pltfrm: vm-linux
 ms.workload: infrastructure
-ms.date: 03/24/2022
+ms.date: 10/17/2022
 ms.author: radeltch
 
 ---
@@ -630,6 +630,9 @@ sudo crm configure rsc_defaults resource-stickiness=1000
 sudo crm configure rsc_defaults migration-threshold=5000
 </code></pre>
 
+> [!IMPORTANT]
+> We recommend as a best practice that you only set AUTOMATED_REGISTER to **no**, while performing thorough fail-over tests, to prevent failed primary instance to automatically register as secondary. Once the fail-over tests have completed successfully, set AUTOMATED_REGISTER to **yes**, so that after takeover system replication can resume automatically.
+
 Make sure that the cluster status is ok and that all of the resources are started. It's not important on which node the resources are running.
 
 <pre><code>sudo crm_mon -r