Merge pull request #271714 from kalyaninamuduri/patch-84

ttorble · web-flow · commit db5cd1425296 · 2024-04-10T11:07:37.000+01:00
Update faq.yml
diff --git a/articles/sap/center-sap-solutions/faq.yml b/articles/sap/center-sap-solutions/faq.yml
@@ -51,11 +51,11 @@ sections:
                 - Registration of an existing Windows and Linux based ABAP/NetWeaver SAP system on Azure
                 - Monitoring the health and status of an SAP system
                 - Creating a new Azure Monitor for SAP solutions provider or integrating an existing one
-                - Start and Stop of an SAP system, individual SAP instances, and HANA database
+                - Start and Stop of an SAP system, individual SAP instances, and HANA database.
                 - Quality checks and recommendations for an SAP system with Azure Advisor
                 - Analyze the cost of running the SAP System in Azure [non-shared resources only]
 
-                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.  
+                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.  
 
       - question:  What is Azure Virtual Instance for SAP solutions?
         answer: | 
@@ -79,7 +79,7 @@ sections:
         answer: | 
                 Azure Virtual Instance for SAP solutions is available in the following regions:  
 
-                - West Europe, North Europe, East US, East US 2, West US, West US 2, West US 3, Central US, South Central US,  North Central US, India Central, East Asia, Southeast Asia, Australia East, Australia Central, Canada Central, Brazil South, UK South, Germany West Central and Sweden Central.  
+                - West Europe, North Europe, East US, East US 2, West US, West US 2, West US 3, Central US, South Central US,  North Central US, India Central, East Asia, Southeast Asia, Korea Central, Japan East, Australia East, Australia Central, Canada Central, Brazil South, UK South, Germany West Central, Sweden Central, France Central, Switzerland North, Norway East, South Africa North and UAE North.  
                 - You can also see [Products available by region](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=all#:~:text=Azure%20Center%20for%20SAP%20solutions) page for information about availability of Azure Center for SAP solutions in different Azure regions. 
 
   - name: Registering Existing SAP System Questions 
@@ -90,7 +90,7 @@ sections:
                 for SAP solutions:
 
                 - SAP systems running on SAP NetWeaver or ABAP stack
-                - SAP systems running on Windows, SUSE and RHEL Linux Operating Systems
+                - SAP systems running on Windows, SUSE, and RHEL Linux Operating Systems
                 - SAP systems running on HANA, DB2, SQL Server, Oracle, Max DB, SAP ASE databases
                 
                 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:
                 - 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. 
                 - 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.  
                 - Register Appropriate resource providers that you have registered. (Compute, Network, Storage, Workloads, Capacity). 
-                - 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. 
+                - 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. 
                 
       - question:  What resources are created in customer’s subscription when you deploy an SAP S/4/HANA system through Azure Center for SAP solutions?
         answer: | 
diff --git a/articles/sap/center-sap-solutions/quickstart-register-system-powershell.md b/articles/sap/center-sap-solutions/quickstart-register-system-powershell.md
@@ -41,7 +41,7 @@ This quickstart requires the Az PowerShell module version 1.0.0 or later. Run `G
     - To start hostctrl sapstartsrv use this command for Linux VMs: 'hostexecstart -start'
     - To start instance sapstartsrv use the command: 'sapcontrol -nr 'instanceNr' -function StartService S0S'
     - To check status of hostctrl sapstartsrv use this command for Windows VMs: C:\Program Files\SAP\hostctrl\exe\saphostexec –status
-- For successful discovery and registration of the SAP system, ensure there is network connectivity between ASCS, App and DB VMs. 'ping' command for App instance hostname must be successful from ASCS VM. 'ping' for Database hostname must be successful from App server VM.
+- For successful discovery and registration of the SAP system, ensure there's network connectivity between ASCS, App and DB VMs. 'ping' command for App instance hostname must be successful from ASCS VM. 'ping' for Database hostname must be successful from App server VM.
 - On App server profile, SAPDBHOST, DBTYPE, DBID parameters must have the right values configured for the discovery and registration of Database instance details.
 
 ## Register SAP system
@@ -65,7 +65,7 @@ To register an existing SAP system in Azure Center for SAP solutions:
        -UserAssignedIdentity @{'/subscriptions/sub1/resourcegroups/rg1/providers/Microsoft.ManagedIdentity/userAssignedIdentities/ACSS-MSI'= @{}} `
      ```
    - **ResourceGroupName** is used to specify the name of the existing Resource Group into which you want the Virtual Instance for SAP solutions resource to be deployed. It could be the same RG in which you have Compute, Storage resources of your SAP system or a different one. 
-   - **Name** attribute is used to specify the SAP System ID (SID) that you are registering with Azure Center for SAP solutions.
+   - **Name** attribute is used to specify the SAP System ID (SID) that you're registering with Azure Center for SAP solutions.
    - **Location** attribute is used to specify the Azure Center for SAP solutions service location. Following table has the mapping that enables you to choose the right service location based on where your SAP system infrastructure is located on Azure.
 
    | **SAP application location** | **Azure Center for SAP solutions service location** |
@@ -84,16 +84,23 @@ To register an existing SAP system in Azure Center for SAP solutions:
    | Australia Central | Australia East |
    | East Asia | East Asia |
    | Southeast Asia | East Asia |
+   | Korea Central | Korea Central |
+   | Japan East | Japan East |
    | Central India | Central India |
    | Canada Central | Canada Central |
    | Brazil South | Brazil South |
    | UK South | UK South |
    | Germany West Central | Germany West Central |
    | Sweden Central | Sweden Central |
-
-   - **Environment** is used to specify the type of SAP environment you are registering. Valid values are *NonProd* and *Prod*.
-   - **SapProduct** is used to specify the type of SAP product you are registering. Valid values are *S4HANA*, *ECC*, *Other*.
-   - **ManagedResourceGroupName** is used to specify the name of the managed resource group which is deployed by ACSS service in your Subscription. This RG is unique for each SAP system (SID) you register. If you do not specify the name, ACSS service sets a name with this naming convention 'mrg-{SID}-{random string}'.
+   | France Central | France Central |
+   | Switzerland North | Switzerland North |
+   | Norway East | Norway East |
+   | South Africa North | South Africa North |
+   | UAE North | UAE North |
+   
+   - **Environment** is used to specify the type of SAP environment you're registering. Valid values are *NonProd* and *Prod*.
+   - **SapProduct** is used to specify the type of SAP product you're registering. Valid values are *S4HANA*, *ECC*, *Other*.
+   - **ManagedResourceGroupName** is used to specify the name of the managed resource group which is deployed by ACSS service in your Subscription. This RG is unique for each SAP system (SID) you register. If you don't specify the name, ACSS service sets a name with this naming convention 'mrg-{SID}-{random string}'.
    - **ManagedRgStorageAccountName** is used to specify the name of the Storage Account which is deployed into the managed resource group. This storage account is unique for each SAP system (SID) you register. ACSS service sets a default name using '{SID}{random string}' naming convention. 
 
 3. Once you trigger the registration process, you can view its status by getting the status of the Virtual Instance for SAP solutions resource that gets deployed as part of the registration process.
