Skip to content

Commit 55f9341

Browse files
Update faq.yml
1 parent 23c66fc commit 55f9341

File tree

1 file changed

+4
-4
lines changed
  • articles/sap/center-sap-solutions

1 file changed

+4
-4
lines changed

articles/sap/center-sap-solutions/faq.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -51,11 +51,11 @@ sections:
5151
- Registration of an existing Windows and Linux based ABAP/NetWeaver SAP system on Azure
5252
- Monitoring the health and status of an SAP system
5353
- Creating a new Azure Monitor for SAP solutions provider or integrating an existing one
54-
- Start and Stop of an SAP system, individual SAP instances, and HANA database
54+
- Start and Stop of an SAP system, individual SAP instances, and HANA database.
5555
- Quality checks and recommendations for an SAP system with Azure Advisor
5656
- Analyze the cost of running the SAP System in Azure [non-shared resources only]
5757
58-
Azure Center for SAP solutions also offers the ability to customize the names of the Azure resources deployed through it via API, CLI and PowerShell. Consider referring to sample API payload templates to deploy a system with custom resource naming conventions.
58+
Azure Center for SAP solutions also offers the ability to customize the names of the Azure resources deployed through it via API, CLI, and PowerShell. Consider referring to sample API payload templates to deploy a system with custom resource naming conventions.
5959
6060
- question: What is Azure Virtual Instance for SAP solutions?
6161
answer: |
@@ -90,7 +90,7 @@ sections:
9090
for SAP solutions:
9191
9292
- SAP systems running on SAP NetWeaver or ABAP stack
93-
- SAP systems running on Windows, SUSE and RHEL Linux Operating Systems
93+
- SAP systems running on Windows, SUSE, and RHEL Linux Operating Systems
9494
- SAP systems running on HANA, DB2, SQL Server, Oracle, Max DB, SAP ASE databases
9595
9696
Refer to the [product documentation](/azure/sap/center-sap-solutions/register-existing-system#prerequisites) to review the complete list of supported and unsupported scenarios.
@@ -133,7 +133,7 @@ sections:
133133
- A *User-assigned managed identity* which has *Azure Center for SAP solutions service role* access on the Subscription or all resource groups (Compute, Network, Storage). If you wish to install SAP Software through Azure Center for SAP solutions, provide *Reader and Data Access role* to the identity on SAP software storage account where you would store the SAP Media.
134134
- An existing virtual network that allows outbound internet connectivity from the Virtual Machines even when they are behind a standard Azure load balancer, where you will deploy your new SAP system.
135135
- Register Appropriate resource providers that you have registered. (Compute, Network, Storage, Workloads, Capacity).
136-
- Sufficient virtual machine quota in the region(s) used for the deployment. Additionally, minimum 4 cores of Standard_D4ds_v4 or Standard_E4s_v3 SKU are required for the deployment to succeed.
136+
- Sufficient virtual machine quota in the region(s) used for the deployment. Additionally, minimum *four* cores of Standard_D4ds_v4 or Standard_E4s_v3 SKU are required for the deployment to succeed.
137137
138138
- question: What resources are created in customer’s subscription when you deploy an SAP S/4/HANA system through Azure Center for SAP solutions?
139139
answer: |

0 commit comments

Comments
 (0)