You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/sap/center-sap-solutions/faq.yml
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -51,11 +51,11 @@ sections:
51
51
- Registration of an existing Windows and Linux based ABAP/NetWeaver SAP system on Azure
52
52
- Monitoring the health and status of an SAP system
53
53
- 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.
55
55
- Quality checks and recommendations for an SAP system with Azure Advisor
56
56
- Analyze the cost of running the SAP System in Azure [non-shared resources only]
57
57
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.
59
59
60
60
- question: What is Azure Virtual Instance for SAP solutions?
61
61
answer: |
@@ -90,7 +90,7 @@ sections:
90
90
for SAP solutions:
91
91
92
92
- 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
94
94
- SAP systems running on HANA, DB2, SQL Server, Oracle, Max DB, SAP ASE databases
95
95
96
96
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:
133
133
- 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.
134
134
- 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.
135
135
- 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.
137
137
138
138
- question: What resources are created in customer’s subscription when you deploy an SAP S/4/HANA system through Azure Center for SAP solutions?
0 commit comments