Skip to content

Commit e30bf42

Browse files
authored
Apply suggestions from PR review
1 parent 1970395 commit e30bf42

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ In this how-to guide, you'll learn how to deploy S/4HANA infrastructure in *Azur
2626
- A **User-assigned managed identity** which has Contributor role access on the Subscription or atleast all resource groups (Compute, Network,Storage). If you wish to install SAP Software through the Azure Center for SAP solutions, also provide Storage Blob data Reader, Reader and Data Access roles to the identity on SAP bits storage account where you would store the SAP Media.
2727
- A [network set up for your infrastructure deployment](prepare-network.md).
2828
- Availability of either Standard_D4ds_v4 or Standard_E4s_v3 SKUS which will be used for "Deployer VM".
29-
- - [Review the quotas for your Azure subscription](../../quotas/view-quotas.md). If the quotas are low, you might need to create a support request before creating your infrastructure deployment. Otherwise, you might experience deployment failures or an **Insufficient quota** error.
29+
- [Review the quotas for your Azure subscription](../../quotas/view-quotas.md). If the quotas are low, you might need to create a support request before creating your infrastructure deployment. Otherwise, you might experience deployment failures or an **Insufficient quota** error.
3030
- Note the SAP Application Performance Standard (SAPS) and database memory size that you need to allow Azure Center for SAP solutions to size your SAP system. If you're not sure, you can also select the VMs. There are:
3131
- A single or cluster of ASCS VMs, which make up a single ASCS instance in the VIS.
3232
- A single or cluster of Database VMs, which make up a single Database instance in the VIS.

0 commit comments

Comments
 (0)