Merge pull request #313294 from jad0126/sap-solutions-quickstarts

[AQ] edit pass: sap-solutions-quickstarts

Author: ShawnJackson

articles/sap/center-sap-solutions/quick-stop-start-sap-cli.md

@@ -1,6 +1,6 @@
 ---
-title: Quickstart - Start and stop SAP systems from Azure Center for SAP solutions with CLI
-description: Learn how to start or stop an SAP system through the Virtual Instance for SAP solutions (VIS) resource in Azure Center for SAP solutions through Azure CLI.
+title: Start or Stop SAP Systems with the Azure CLI
+description: Learn how to start or stop an SAP system in Azure Center for SAP solutions by using the Azure CLI.
 ms.service: sap-on-azure
 ms.subservice: center-sap-solutions
 ms.custom: devx-track-azurecli
@@ -9,74 +9,77 @@ ms.date: 05/04/2023
 ms.author: kanamudu
 author: kalyaninamuduri
 #Customer intent: As a developer, I want to start and stop SAP systems in Azure Center for SAP solutions so that I can control instances through the Virtual Instance for SAP resource.
-# Customer intent: As an SAP system administrator, I want to start and stop SAP systems using the Azure CLI, so that I can efficiently manage system resources and ensure optimal performance of my applications.
+#Customer intent: As an SAP system administrator, I want to start and stop SAP systems by using the Azure CLI, so that I can efficiently manage system resources and optimize performance of my applications.
 ---
-# Quickstart: Start and stop SAP systems from Azure Center for SAP solutions with CLI
+# Start and stop SAP systems in Azure Center for SAP solutions with the Azure CLI
 
-The Azure CLI is used to create and manage Azure resources from the command line or in scripts. 
+Use the Azure CLI to create and manage Azure resources from the command line or in scripts.
 
-In this how-to guide, you'll learn how to start and stop your SAP systems through the *Virtual Instance for SAP solutions (VIS)* resource in *Azure Center for SAP solutions* using the Azure CLI. 
+In this guide, you learn to start and stop your SAP systems through the Virtual Instance for SAP solutions (VIS) resource in Azure Center for SAP solutions. You can start and stop SAP systems by using the Azure CLI or by using Azure PowerShell. This article shows you the steps to use the Azure CLI.
 
 Through the Azure CLI, you can start and stop:
 
-- The entire SAP Application tier, which includes ABAP SAP Central Services (ASCS) and Application Server instances.
-- Individual SAP instances, which include Central Services and Application server instances.
-- HANA Database
-- You can start and stop instances in the following types of deployments:
-    - Single-Server
-    - High Availability (HA)
-    - Distributed Non-HA
-- SAP systems that run on Windows and, RHEL and SUSE Linux operating systems.
-- SAP HA systems that use SUSE and RHEL Pacemaker clustering software and Windows Server Failover Clustering (WSFC). Other certified cluster software isn't currently supported.
+- The entire SAP application tier, which includes Advanced Business Application Programming SAP Central Services (ASCS) and application server instances.
+- Individual SAP instances, which include Central Services and application server instances.
+- A HANA database.
+- Instances in the following types of deployments:
+  - Single-server.
+  - High availability (HA).
+  - Distributed non-HA.
+- SAP systems that run on Windows.
+- SAP systems that run on RHEL and SUSE Linux operating systems.
+- SAP HA systems that use RHEL and SUSE Pacemaker clustering software and Windows Server Failover Clustering. Other certified cluster software isn't currently supported.
 
 ## Prerequisites
-- An SAP system that you've [created in Azure Center for SAP solutions](prepare-network.md) or [registered with Azure Center for SAP solutions](register-existing-system.md) as a *Virtual Instance for SAP solutions* resource.
-- Check that your Azure account has **Azure Center for SAP solutions administrator** or equivalent role access on the Virtual Instance for SAP solutions resources. You can learn more about the granular permissions that govern Start and Stop actions on the VIS, individual SAP instances and HANA Database [in this article](manage-with-azure-rbac.md#start-sap-system).
-- For the start operation to work, the underlying virtual machines (VMs) of the SAP instances must be running. This capability starts or stops the SAP application instances, not the VMs that make up the SAP system resources.
-- The `sapstartsrv` service must be running on all VMs related to the SAP system.
-- For HA deployments, the HA interface cluster connector for SAP (`sap_vendor_cluster_connector`) must be installed on the ASCS instance. For more information, see the [SUSE connector specifications](https://www.suse.com/c/sap-netweaver-suse-cluster-integration-new-sap_suse_cluster_connector-version-3-0-0/) and [RHEL connector specifications](https://access.redhat.com/solutions/3606101).
-- The Stop operation function for the HANA Database can only be initiated when the cluster maintenance mode is in **Disabled** status. Similarly,  the Start operation function can only be initiated when the cluster maintenance mode is in **Enabled** status.
 
-## Start SAP system
-To Start an SAP system represented as a *Virtual Instance for SAP solutions* resource:
+To start and stop on the VIS solutions resource, you must:
 
-Use the [az workloads sap-virtual-instance start](/cli/azure/workloads/sap-virtual-instance#az-workloads-sap-virtual-instance-start) command:
+- Use an SAP system that you [created in Azure Center for SAP solutions](prepare-network.md) or [registered with Azure Center for SAP solutions](register-existing-system.md) as a VIS resource.
 
-Option 1:
+- Confirm that your Azure account has the following role, or equivalent role access on the VIS resource: Azure Center for SAP solutions administrator. For more information about the granular permissions that govern start and stop actions on the VIS, individual SAP instances, and HANA database, see [Start SAP system](manage-with-azure-rbac.md#start-sap-system).
 
-Use the Virtual Instance for SAP solutions resource Name and ResourceGroupName to identify the system you intend to start.
+- Confirm that the underlying virtual machines (VMs) of the SAP instances are running. This capability starts or stops the SAP application instances, not the VMs that make up the SAP system resources.
 
-```azurecli-interactive
-     az workloads sap-virtual-instance start -g <Resource-group-name> -n <ResourceName>
-```
-Option 2:
+- Confirm that the `sapstartsrv` service is running on all VMs related to the SAP system.
 
-Use the `id` parameter and pass the resource ID of the Virtual Instance for SAP solutions resource you intend to start.
-     
-```azurecli-interactive
-     az workloads sap-virtual-instance start --id <ResourceID>
-```
+- For HA deployments, install the HA interface cluster connector for SAP (`sap_vendor_cluster_connector`) on the ASCS instance. For more information, see the [SUSE connector specifications](https://www.suse.com/c/sap-netweaver-suse-cluster-integration-new-sap_suse_cluster_connector-version-3-0-0/) and [RHEL connector specifications](https://access.redhat.com/solutions/3606101).
+
+- For start operations, ensure that the cluster maintenance mode is in the **Enabled** status. The start operation function for the HANA database can only be initiated when the cluster maintenance mode is enabled.
+
+- For stop operations, ensure that the cluster maintenance mode is in the **Disabled** status. The stop operation function for the HANA database can only be initiated when the cluster maintenance mode is disabled.
+
+## Start an SAP system
+
+To start an SAP system represented as a Virtual Instance for SAP solutions resource, use the [az workloads sap-virtual-instance start](/cli/azure/workloads/sap-virtual-instance#az-workloads-sap-virtual-instance-start) command. Choose one of the following options:
 
-## Stop SAP system
+- Use the Virtual Instance for SAP solutions resource `ResourceName` and `ResourceGroupName` to identify the system that you want to start.
 
-To stop an SAP system represented as a *Virtual Instance for SAP solutions* resource:
+   ```azurecli-interactive
+     az workloads sap-virtual-instance start -g <Resource-group-name> -n <ResourceName>
+   ```  
+
+- Use the `id` parameter and pass the resource ID of the Virtual Instance for SAP solutions resource that you want to start.
+
+   ```azurecli-interactive
+     az workloads sap-virtual-instance start --id <ResourceID>
+   ```
 
-Use the [az workloads sap-virtual-instance stop](/cli/azure/workloads/sap-virtual-instance#az-workloads-sap-virtual-instance-stop) command:
+## Stop an SAP system
 
-Option 1:
+To stop an SAP system represented as a Virtual Instance for SAP solutions resource, use the [az workloads sap-virtual-instance stop](/cli/azure/workloads/sap-virtual-instance#az-workloads-sap-virtual-instance-stop) command. Choose one of the following options:
 
-Use the Virtual Instance for SAP solutions resource Name and ResourceGroupName to identify the system you intend to stop.
+- Use the Virtual Instance for SAP solutions `ResourceName` and `ResourceGroupName` to identify the system that you want to stop.
 
-```azurecli-interactive
+   ```azurecli-interactive
      az workloads sap-virtual-instance stop -g <Resource-group-name> -n <ResourceName>
-```
-Option 2:
+   ```
 
-Use the `id` parameter and pass the resource ID of the Virtual Instance for SAP solutions resource you intend to stop.
-     
-```azurecli-interactive
+- Use the `id` parameter and pass the resource ID of the Virtual Instance for SAP solutions resource that you want to stop.
+  
+   ```azurecli-interactive
      az workloads sap-virtual-instance stop --id <ResourceID>
-```
- 
- ## Next steps
+   ```
+
+## Related content
+
 - [Monitor SAP system from the Azure portal](monitor-portal.md)

articles/sap/center-sap-solutions/quick-stop-start-sap-powershell.md

@@ -1,88 +1,85 @@
 ---
-title: Quickstart - Start and stop SAP systems from Azure Center for SAP solutions with PowerShell
-description: Learn how to start or stop an SAP system through the Virtual Instance for SAP solutions (VIS) resource in Azure Center for SAP solutions through Azure PowerShell module.
+title: Start or Stop SAP Systems with Azure PowerShell
+description: Learn how to start or stop an SAP system in Azure Center for SAP solutions by using an Azure PowerShell module.
 ms.service: sap-on-azure
-ms.subservice: center-sap-solutions
+ms.subservice: center-sap-solutions 
 ms.custom: devx-track-azurepowershell
 ms.topic: how-to
 ms.date: 05/04/2023
 ms.author: kanamudu
 author: kalyaninamuduri
 #Customer intent: As a developer, I want to start and stop SAP systems in Azure Center for SAP solutions so that I can control instances through the Virtual Instance for SAP resource.
-# Customer intent: As a system administrator, I want to use PowerShell to start and stop SAP systems in Azure Center for SAP solutions, so that I can efficiently manage application instances and optimize resource utilization.
+#Customer intent: As a system administrator, I want to use Azure PowerShell to start and stop SAP systems in Azure Center for SAP solutions, so that I can efficiently manage application instances and optimize use of resources.
 ---
-# Quickstart: Start and stop SAP systems from Azure Center for SAP solutions with PowerShell
+# Start and stop SAP systems in Azure Center for SAP solutions with Azure PowerShell
 
-The [Azure PowerShell AZ](/powershell/azure/new-azureps-module-az) module is used to create and manage Azure resources from the command line or in scripts.
+Use the [Az PowerShell module](/powershell/azure/new-azureps-module-az) to create and manage Azure resources from the command line or in scripts.
 
-In this how-to guide, you'll learn to start and stop your SAP systems through the *Virtual Instance for SAP solutions (VIS)* resource in *Azure Center for SAP solutions* using PowerShell.
+In this guide, you learn to start and stop your SAP systems through the Virtual Instance for SAP solutions (VIS) resource in Azure Center for SAP solutions. You can start and stop SAP systems by using the Azure CLI or by using Azure PowerShell. This article shows you the steps to use Azure PowerShell.
 
 Through the Azure PowerShell module, you can start and stop:
 
-- The entire SAP Application tier, which includes ABAP SAP Central Services (ASCS) and Application Server instances.
-- Individual SAP instances, which include Central Services and Application server instances.
-- HANA Database
-- You can start and stop instances in the following types of deployments:
-  - Single-Server
-  - High Availability (HA)
-  - Distributed Non-HA
-- SAP systems that run on Windows and, RHEL and SUSE Linux operating systems.
-- SAP HA systems that use SUSE and RHEL Pacemaker clustering software and Windows Server Failover Clustering (WSFC). Other certified cluster software isn't currently supported.
+- The entire SAP application tier, which includes Advanced Business Application Programming SAP Central Services (ASCS) and application server instances.
+- Individual SAP instances, which include Central Services and application server instances.
+- A HANA database.
+- Instances in the following types of deployments:
+  - Single-server.
+  - High availability (HA).
+  - Distributed non-HA.
+- SAP systems that run on Windows.
+- SAP systems that run on RHEL and SUSE Linux operating systems.
+- SAP HA systems that use RHEL and SUSE Pacemaker clustering software and Windows Server Failover Clustering. Other certified cluster software isn't currently supported.
 
 ## Prerequisites
 
-The following are prerequisites that you need to ensure before using the Start or Stop capability on the Virtual Instance for SAP solutions resource.
-- An SAP system that you've [created in Azure Center for SAP solutions](prepare-network.md) or [registered with Azure Center for SAP solutions](register-existing-system.md) as a *Virtual Instance for SAP solutions* resource.
-- Check that your Azure account has **Azure Center for SAP solutions administrator** or equivalent role access on the Virtual Instance for SAP solutions resources. You can learn more about the granular permissions that govern Start and Stop actions on the VIS, individual SAP instances and HANA Database [in this article](manage-with-azure-rbac.md#start-sap-system).
-- For the start operation to work, the underlying virtual machines (VMs) of the SAP instances must be running. This capability starts or stops the SAP application instances, not the VMs that make up the SAP system resources.
-- The `sapstartsrv` service must be running on all VMs related to the SAP system.
-- For HA deployments, the HA interface cluster connector for SAP (`sap_vendor_cluster_connector`) must be installed on the ASCS instance. For more information, see the [SUSE connector specifications](https://www.suse.com/c/sap-netweaver-suse-cluster-integration-new-sap_suse_cluster_connector-version-3-0-0/) and [RHEL connector specifications](https://access.redhat.com/solutions/3606101).
-- The Stop operation function for the HANA Database can only be initiated when the cluster maintenance mode is in **Disabled** status. Similarly, Start operation can only be initiated when the cluster maintenance mode is in **Enabled** status.
+To start and stop on the VIS solutions resource, you must:
 
-## Start SAP system
+- Use an SAP system that you've [created in Azure Center for SAP solutions](prepare-network.md) or [registered with Azure Center for SAP solutions](register-existing-system.md) as a VIS resource.
 
-To Start an SAP system represented as a *Virtual Instance for SAP solutions* resource:
+- Confirm that your Azure account has the following role, or equivalent role access on the VIS resource: Azure Center for SAP solutions administrator. For more information about the granular permissions that govern start and stop actions on the VIS, individual SAP instances, and HANA database, see [Start SAP system](manage-with-azure-rbac.md#start-sap-system).
 
-Use the [Start-AzWorkloadsSapVirtualInstance](/powershell/module/az.workloads/Start-AzWorkloadsSapVirtualInstance) command:
+- Confirm that the underlying virtual machines (VMs) of the SAP instances are running. This capability starts or stops the SAP application instances, not the VMs that make up the SAP system resources.
 
-Option 1:
+- Confirm that the `sapstartsrv` service is running on all VMs related to the SAP system.
 
-Use the Virtual Instance for SAP solutions resource Name and ResourceGroupName to identify the system you intend to start.
+- For HA deployments, install the HA interface cluster connector for SAP (`sap_vendor_cluster_connector`) on the ASCS instance. For more information, see the [SUSE connector specifications](https://www.suse.com/c/sap-netweaver-suse-cluster-integration-new-sap_suse_cluster_connector-version-3-0-0/) and [RHEL connector specifications](https://access.redhat.com/solutions/3606101).
 
-```powershell
-     Start-AzWorkloadsSapVirtualInstance -Name DB0 -ResourceGroupName db0-vis-rg `
-```
+- For start operations, ensure that the cluster maintenance mode is in the **Enabled** status. The start operation function for the HANA database can only be initiated when the cluster maintenance mode is enabled.
 
-Option 2:
+- For stop operations, ensure that the cluster maintenance mode is in the **Disabled** status. The stop operation function for the HANA database can only be initiated when the cluster maintenance mode is disabled.
 
-Use the InputObject parameter and pass the resource ID of the Virtual Instance for SAP solutions resource you intend to start.
+## Start an SAP system
 
- ```powershell
-     Start-AzWorkloadsSapVirtualInstance -InputObject /subscriptions/sub1/resourceGroups/rg1/providers/Microsoft.Workloads/sapVirtualInstances/DB0 `
- ```
+To start an SAP system represented as a Virtual Instance for SAP solutions resource, use the [Start-AzWorkloadsSapVirtualInstance](/powershell/module/az.workloads/Start-AzWorkloadsSapVirtualInstance) command. Choose one of the following options:
 
-## Stop SAP system
+- Use the Virtual Instance for SAP solutions resource `Name` and `ResourceGroupName` to identify the system that you want to start.
 
-To stop an SAP system represented as a *Virtual Instance for SAP solutions* resource:
+   ```powershell
+     Start-AzWorkloadsSapVirtualInstance -Name DB0 -ResourceGroupName db0-vis-rg `
+   ```
 
-Use the [Stop-AzWorkloadsSapVirtualInstance](/powershell/module/az.workloads/Stop-AzWorkloadsSapVirtualInstance) command:
+- Use the `InputObject` parameter and pass the resource ID of the Virtual Instance for SAP solutions resource that you want to start.
 
-Option 1:
+   ```powershell
+     Start-AzWorkloadsSapVirtualInstance -InputObject /subscriptions/sub1/resourceGroups/rg1/providers/Microsoft.Workloads/sapVirtualInstances/DB0 `
+   ```
 
-Use the Virtual Instance for SAP solutions resource Name and ResourceGroupName to identify the system you intend to stop.
+## Stop an SAP system
 
-```powershell
-     Stop-AzWorkloadsSapVirtualInstance -Name DB0 -ResourceGroupName db0-vis-rg `
-```
+To stop an SAP system represented as a Virtual Instance for SAP solutions resource, use the [Stop-AzWorkloadsSapVirtualInstance](/powershell/module/az.workloads/Stop-AzWorkloadsSapVirtualInstance) command. Choose one of the following options:
+
+- Use the Virtual Instance for SAP solutions resource `Name` and `ResourceGroupName` to identify the system that you want to stop.
 
-Option 2:
+   ```powershell
+     Stop-AzWorkloadsSapVirtualInstance -Name DB0 -ResourceGroupName db0-vis-rg `
+   ```
 
-Use the InputObject parameter and pass the resource ID of the Virtual Instance for SAP solutions resource you intend to stop.
+- Use the `InputObject` parameter and pass the resource ID of the Virtual Instance for SAP solutions resource that you want to stop.
 
-```powershell
+   ```powershell
      Stop-AzWorkloadsSapVirtualInstance -InputObject /subscriptions/sub1/resourceGroups/rg1/providers/Microsoft.Workloads/sapVirtualInstances/DB0 `
-```
+   ```
 
-## Next steps
+## Related content
 
 - [Monitor SAP system from the Azure portal](monitor-portal.md)