Merge pull request #251591 from kalyaninamuduri/patch-66

Update register-existing-system.md

Author: prmerger-automator[bot]

articles/sap/center-sap-solutions/register-existing-system.md

@@ -5,8 +5,8 @@ ms.service: sap-on-azure
 ms.subservice: center-sap-solutions
 ms.topic: how-to
 ms.date: 02/03/2023
-ms.author: sagarkeswani
-author: sagarkeswani
+ms.author: kalyaninamuduri
+author: kalyaninamuduri
 #Customer intent: As a developer, I want to register my existing SAP system so that I can use the system with Azure Center for SAP solutions.
 ---
 
@@ -31,16 +31,21 @@ When you register a system with Azure Center for SAP solutions, the following re
 
 ## Prerequisites
 
+### Azure infrastructure level pre-requisites
+
 - Check that you're trying to register a [supported SAP system configuration](#supported-systems)
-- Grant access to your Azure Storage accounts from the virtual network where the SAP system exists. Use one of these options:
+- Grant access to Azure Storage accounts, Azure resource manager (ARM) and Microsoft Entra ID services from the virtual network where the SAP system exists. Use one of these options:
     - Allow outbound internet connectivity for the VMs.
-    - Use a [**Storage** service tag](../../virtual-network/service-tags-overview.md) to allow connectivity to any Azure storage account from the VMs.
-    - Use a [**Storage** service tag with regional scope](../../virtual-network/service-tags-overview.md) to allow storage account connectivity to the Azure storage accounts in the same region as the VMs.
-    - Allowlist the region-specific IP addresses for Azure Storage.
+    - Use a [**Service tags**](../../virtual-network/service-tags-overview.md) to allow connectivity
+    - Use a [Service tags with regional scope](../../virtual-network/service-tags-overview.md) to allow connectivity to resources in the same region as the VMs.
+    - Allowlist the region-specific IP addresses for Azure Storage, ARM and Microsoft Entra ID.
 - Register the **Microsoft.Workloads** Resource Provider in the subscription where you have the SAP system.
 - Check that your Azure account has **Azure Center for SAP solutions administrator** and **Managed Identity Operator** or equivalent role access on the subscription or resource groups where you have the SAP system resources.
 - A **User-assigned managed identity** which has **Azure Center for SAP solutions service role** access on the Compute resource group and **Reader** role access on the Virtual Network resource group of the SAP system. Azure Center for SAP solutions service uses this identity to discover your SAP system resources and register the system as a VIS resource.
 - Make sure ASCS, Application Server and Database virtual machines of the SAP system are in **Running** state.
+
+### SAP system level pre-requisites
+
 - sapcontrol and saphostctrl exe files must exist on ASCS, App server and Database.
     - File path on Linux VMs: /usr/sap/hostctrl/exe
     - File path on Windows VMs: C:\Program Files\SAP\hostctrl\exe\
@@ -58,6 +63,8 @@ You can register SAP systems with Azure Center for SAP solutions that run on the
 - SAP NetWeaver or ABAP stacks
 - Windows, SUSE and RHEL Linux operating systems
 - HANA, DB2, SQL Server, Oracle, Max DB, and SAP ASE databases
+- SAP system with multiple Application Server Instances on a single Virtual Machine
+- SAP system with [clustered Application Server architecture](../workloads/high-availability-guide-rhel-with-dialog-instance.md)
 
 The following SAP system configurations aren't supported in Azure Center for SAP solutions:
 
@@ -67,8 +74,6 @@ The following SAP system configurations aren't supported in Azure Center for SAP
 - Dual stack (ABAP and Java)
 - Systems distributed across peered virtual networks
 - Systems using IPv6 addresses
-- SAP system with multiple Application Server Instances on a single Virtual Machine
-- SAP system with [clustered Application Server architecture](../workloads/high-availability-guide-rhel-with-dialog-instance.md)
 - Multiple SIDs running on same set of Virtual Machines. For example, two or more SIDs sharing a single VM for ASCS instance. 
 
 ## Enable resource permissions