Merge pull request #226640 from kalyaninamuduri/patch-34

Update register-existing-system.md

Author: prmerger-automator[bot]

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

@@ -29,7 +29,7 @@ In this how-to guide, you'll learn how to register an existing SAP system with *
 - Check that you're trying to register a [supported SAP system configuration](#supported-systems)
 - Check that your Azure account has **Contributor** role access on the subscription or resource groups where you have the SAP system resources.
 - Register the **Microsoft.Workloads** Resource Provider in the subscription where you have the SAP system.
-- A **User-assigned managed identity** which has **Virtual Machine Contributor** role access to the Compute resource group and **Reader** and **Tag Contributor** role access to the 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.
+- A **User-assigned managed identity** which has **Virtual Machine Contributor** and **Tag Contributor** role access on the Compute resource group and **Reader** and **Tag Contributor** role access on the 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 each virtual machine (VM) in the SAP system is currently running on Azure. These VMs include:
     - The ABAP SAP Central Services (ASCS) Server instance
     - The Application Server instance or instances
@@ -64,20 +64,20 @@ The following SAP system configurations aren't supported in Azure Center for SAP
 
 ## Enable resource permissions
 
-When you register an existing SAP system as a VIS, Azure Center for SAP solutions service needs a **User-assigned managed identity** which has **Virtual Machine Contributor** role access to the Compute resource groups and **Reader** and **Tag Contributor** role access to the Network resource groups of the SAP system. Before you register an SAP system with Azure Center for SAP solutions, either [create a new user-assigned managed identity or update role access for an existing managed identity](#setup-user-assigned-managed-identity).
+When you register an existing SAP system as a VIS, Azure Center for SAP solutions service needs a **User-assigned managed identity** which has **Virtual Machine Contributor** and **Tag Contributor** role access on the Compute (VMs, Disks, Load balancers) resource group and **Reader** role access on the Virtual Network resource group of the SAP system. Before you register an SAP system with Azure Center for SAP solutions, either [create a new user-assigned managed identity or update role access for an existing managed identity](#setup-user-assigned-managed-identity).
 
-Azure Center for SAP solutions uses this user-assigned managed identity to install VM extensions on the ASCS, Application Server and DB VMs. This step allows Azure Center for SAP solutions to discover the SAP system components, and other SAP system metadata. Azure Center for SAP solutions also needs this user-assigned managed identity to enable SAP system monitoring and management capabilities.
+Azure Center for SAP solutions uses this user-assigned managed identity to install VM extensions on the ASCS, Application Server and DB VMs. This step allows Azure Center for SAP solutions to discover the SAP system components, and other SAP system metadata. User-assigned managed identity is required to enable SAP system monitoring and management capabilities.
 
 ### Setup User-assigned managed identity
 
 To provide permissions to the SAP system resources to a user-assigned managed identity:
 
 1. [Create a new user-assigned managed identity](../active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities.md#create-a-user-assigned-managed-identity) if needed or use an existing one.
-1. [Assign **Virtual Machine Contributor** role access](../active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities.md#manage-access-to-user-assigned-managed-identities) to the user-assigned managed identity on the resource group(s) which have the Virtual Machines of the SAP system and **Reader** and **Tag Contributor** role on the resource group(s) which have the Network components of the SAP system.
+1. [Assign **Virtual Machine Contributor** and **Tag Contributor**](../active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities.md#manage-access-to-user-assigned-managed-identities) role access to the user-assigned managed identity on the resource group(s) which have the Virtual Machines, Disks and Load Balancers of the SAP system and **Reader** role on the resource group(s) which have the Virtual Network components of the SAP system.
 1. Once the permissions are assigned, this managed identity can be used in Azure Center for SAP solutions to register and manage SAP systems.
 
 > [!NOTE]
-> User-assigned managed identity requires **Tag Contributor** role on Network resources of the SAP system to enable [Cost Analysis](view-cost-analysis.md) at SAP SID level.
+> User-assigned managed identity requires **Tag Contributor** role on VMs, Disks and Load Balancers of the SAP system to enable [Cost Analysis](view-cost-analysis.md) at SAP SID level.
 
 ## Register SAP system
 
@@ -118,9 +118,10 @@ The process of registering an SAP system in Azure Center for SAP solutions might
     - Command to start up sapstartsrv process on SAP VMs: /usr/sap/hostctrl/exe/hostexecstart -start
 - At least one Application Server and the Database aren't running for the SAP system that you chose. Make sure the Application Servers and Database VMs are in the **Running** state.
 - The user trying to register the SAP system doesn't have **Contributor** role permissions. For more information, see the [prerequisites for registering an SAP system](#prerequisites).
-- The user-assigned managed identity doesn't have **Virtual Machine Contributor** role access to the Compute resources and **Reader** and **Tag Contributor** role access to the Network resource groups of the SAP system. For more information, see [how to enable Azure Center for SAP solutions resource permissions](#enable-resource-permissions).
+- The user-assigned managed identity doesn't have **Virtual Machine Contributor** role access to the Compute resources and **Reader** role access to the Network resource groups of the SAP system. For more information, see [how to enable Azure Center for SAP solutions resource permissions](#enable-resource-permissions).
 
-There's also a known issue with registering *S/4HANA 2021* version SAP systems. You might receive the error message: **Failed to discover details from the Db VM**. This error happens when the Database identifier is incorrectly configured on the SAP system. One possible cause is that the Application Server profile parameter `rsdb/dbid` has an incorrect identifier for the HANA Database. To fix the error:
+### Error - Failed to discover details from the DB VM
+This error happens when the Database identifier is incorrectly configured on the SAP system. One possible cause is that the Application Server profile parameter `rsdb/dbid` has an incorrect identifier for the HANA Database. To fix the error:
 
 1. Stop the Application Server instance:
 
@@ -148,6 +149,17 @@ There's also a known issue with registering *S/4HANA 2021* version SAP systems.
 
 1. [Register the SAP system](#register-sap-system) again.
 
+### Error - Azure VM Agent not in desired provisioning state
+This issue occurs when Azure VM agent's provisioning state is not as expected on the specified Virtual Machine. Expected state is **Ready**. Verify the agent status by checking the properties section in the VM overview page. To fix the VM Agent, 
+1. Login to the VM using bastion or serial console.
+1. If the VM agent exists and is not running, then restart the waagent.
+  - sudo systemctl status waagent. 
+  - If the service is not running then restart this service. To restart use the following steps:
+  - sudo systemctl stop waagent
+  - sudo systemctl start waagent
+  - If this does not solve the issue, try updating the VM Agent using [this document](../virtual-machines/extensions/update-linux-agent.md)
+3. If the VM agent does not exist or needs to be re-installed, then follow [this documentation](../virtual-machines/extensions/update-linux-agent.md).
+
 If your registration fails:
 
 1. Review the previous list of possible reasons for failure. Follow any steps to fix the issue.