Merge pull request #213435 from kalyaninamuduri/patch-21

Update deploy-s4hana.md

Author: prmerger-automator[bot]

articles/center-sap-solutions/deploy-s4hana.md

@@ -20,9 +20,7 @@ In this how-to guide, you'll learn how to deploy S/4HANA infrastructure in *Azur
 - An Azure subscription.
 - Register the **Microsoft.Workloads** Resource Provider on the subscription in which you are deploying the SAP system.
 - An Azure account with **Contributor** role access to the subscriptions and resource groups in which you'll create the Virtual Instance for SAP solutions (VIS) resource.
-- The ACSS application **Azure SAP Workloads Management** also needs Contributor role access to the resource groups for the SAP system. There are two options to grant access:
-    - If your Azure account has **Owner** or **User Access Admin** role access, you can automatically grant access to the application when deploying or registering the SAP system.
-    - If your Azure account doesn't have Owner or User Access Admin role access, you must enable access for the ACSS application. 
+- A **User-assigned managed identity** which has Contributor role access to the resource groups of the SAP system. 
 - A [network set up for your infrastructure deployment](prepare-network.md).
 
 ## Deployment types
@@ -96,6 +94,12 @@ There are three deployment options that you can select for your infrastructure,
 
     1. For **SAP FQDN**, provide FQDN for you system such "sap.contoso.com"
 
+1. Under **User assigned managed identity**, provide the identity which ACSS will use to deploy infrastructure.
+
+    1. For **Managed identity source**, choose if you want to create a new identity or use an existing identity.
+
+    1. For **Managed identity name**, enter a name for a new identity you want to create or select an existing identity from the drop down menu. If you are selecting an existing identity, it should have **Contributor** role access on the Subscription or on Resource Groups related to this SAP system you are trying to deploy. That is, it requires Contributor access to the SAP application Resource Group, Virtual Network Resource Group and Resource Group which has the existing SSHKEY.
+
 1. Select **Next: Virtual machines**.
 
 1. In the **Virtual machines** tab, generate SKU size and total VM count recommendations for each SAP instance from ACSS.