Skip to content

Commit dee6efa

Browse files
JillGrant615JillGrant615
authored
Merge pull request #313360 from Xelu86/quickregps
[Update] Quickstart: Register an existing SAP system with Azure Center for SAP solutions using Azure PowerShell
2 parents 660fbc4 + 7ef7cfd commit dee6efa

1 file changed

Lines changed: 121 additions & 101 deletions

File tree

‎articles/sap/center-sap-solutions/quickstart-register-system-powershell.md‎

Lines changed: 121 additions & 101 deletions
Original file line numberDiff line numberDiff line change
@@ -1,118 +1,138 @@
11
---
2-
title: Quickstart - Register an existing system with Azure Center for SAP solutions with PowerShell
3-
description: Learn how to register an existing SAP system in Azure Center for SAP solutions through Azure PowerShell module.
2+
title: Register an existing SAP system with Azure Center for SAP solutions using Azure PowerShell
3+
description: Learn how to register an existing SAP system in Azure Center for SAP solutions by using the Azure PowerShell module.
44
ms.service: sap-on-azure
55
ms.subservice: center-sap-solutions
66
ms.custom: references_regions, devx-track-azurepowershell
77
ms.topic: how-to
8-
ms.date: 05/04/2023
8+
ms.date: 03/18/2026
99
ms.author: kanamudu
1010
author: kalyaninamuduri
11-
#Customer intent: As a developer, I want to register my existing SAP system so that I can use the system with Azure Center for SAP solutions.
12-
# Customer intent: "As an SAP administrator, I want to register my existing SAP system with Azure Center for SAP solutions using PowerShell, so that I can utilize the platform's management and monitoring capabilities for my SAP infrastructure."
11+
# Customer intent: As an SAP administrator, I want to register my existing SAP system with Azure Center for SAP solutions by using PowerShell, so that I can use the platform's management and monitoring capabilities for my SAP infrastructure.
1312
---
14-
# Quickstart: Register an existing SAP system with Azure Center for SAP solutions with PowerShell
15-
16-
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.
17-
18-
[Azure Center for SAP solutions](overview.md) enables you to deploy and manage SAP systems on Azure. This article shows you how to register an existing SAP system running on Azure with *Azure Center for SAP solutions* using Az PowerShell module. Alternatively, you can register systems using the Azure CLI, or in the Azure portal.
19-
After you register an SAP system with *Azure Center for SAP solutions*, you can use its visualization, management and monitoring capabilities through the Azure portal.
20-
21-
This quickstart requires the Az PowerShell module version 1.0.0 or later. Run `Get-Module -ListAvailable Az` to find the version. If you need to install or upgrade, see [Install Azure PowerShell module](/powershell/azure/install-az-ps).
22-
23-
## Prerequisites for Registering a system
24-
- Check that you're trying to register a [supported SAP system configuration](/azure/sap/center-sap-solutions/register-existing-system#supported-systems)
25-
- Grant access to Azure Storage accounts from the virtual network where the SAP system exists. Use one of these options:
26-
- Allow outbound internet connectivity for the VMs.
27-
- Use a [**Storage** service tag](../../virtual-network/service-tags-overview.md) to allow connectivity to any Azure storage account from the VMs.
28-
- Use a [**Storage** service tag with regional scope](../../virtual-network/service-tags-overview.md) to allow storage account connectivity to the Azure storage accounts in the same region as the VMs.
29-
- Allowlist the region-specific IP addresses for Azure Storage.
30-
- The first time you use Azure Center for SAP solutions, you must register the **Microsoft.Workloads** Resource Provider in the subscription where you have the SAP system with [Register-AzResourceProvider](/powershell/module/az.Resources/Register-azResourceProvider), as follows:
31-
32-
```powershell
33-
Register-AzResourceProvider -ProviderNamespace "Microsoft.Workloads"
34-
```
35-
- Check that your Azure account has **Azure Center for SAP solutions administrator** and **Managed Identity Operator** or equivalent role access on the subscription or resource groups where you have the SAP system resources.
36-
- A **User-assigned managed identity** which has **Azure Center for SAP solutions service role** access on the Compute resource group and **Reader** role access on the Virtual Network resource group of the SAP system. Azure Center for SAP solutions service uses this identity to discover your SAP system resources and register the system as a VIS resource.
37-
- Make sure ASCS, Application Server and Database virtual machines of the SAP system are in **Running** state.
38-
- sapcontrol and saphostctrl exe files must exist on ASCS, App server and Database.
39-
- File path on Linux VMs: /usr/sap/hostctrl/exe
40-
- File path on Windows VMs: C:\Program Files\SAP\hostctrl\exe\
41-
- Make sure the **sapstartsrv** process is running on all **SAP instances** and for **SAP hostctrl agent** on all the VMs in the SAP system.
42-
- To start hostctrl sapstartsrv use this command for Linux VMs: 'hostexecstart -start'
43-
- To start instance sapstartsrv use the command: 'sapcontrol -nr 'instanceNr' -function StartService S0S'
44-
- To check status of hostctrl sapstartsrv use this command for Windows VMs: C:\Program Files\SAP\hostctrl\exe\saphostexec –status
45-
- 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.
46-
- On App server profile, SAPDBHOST, DBTYPE, DBID parameters must have the right values configured for the discovery and registration of Database instance details.
47-
48-
## Register SAP system
13+
14+
# Quickstart: Register an existing SAP system with Azure Center for SAP solutions using Azure PowerShell
15+
16+
In this quickstart, you use the Azure PowerShell module to register an existing SAP system with Azure Center for SAP solutions. After you register the system, Azure Center for SAP solutions creates a Virtual Instance for SAP solutions (VIS) resource that provides visualization, management, and monitoring capabilities through the Azure portal. You can also register systems by using the [Azure CLI](quickstart-register-system-cli.md) or the [Azure portal](register-existing-system.md).
17+
18+
## Prerequisites
19+
20+
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
21+
- The Az PowerShell module version 1.0.0 or later. To find the version, run `Get-Module -ListAvailable Az`. If you need to install or upgrade, see [Install Azure PowerShell module](/powershell/azure/install-az-ps).
22+
- A [supported SAP system configuration](/azure/sap/center-sap-solutions/register-existing-system#supported-systems).
23+
- Network access to Azure Storage accounts from the virtual network where the SAP system exists. Use one of these options:
24+
25+
- Allow outbound internet connectivity for the virtual machines (VMs).
26+
- Use a [**Storage** service tag](../../virtual-network/service-tags-overview.md) to allow connectivity to any Azure storage account from the VMs.
27+
- Use a [**Storage** service tag with regional scope](../../virtual-network/service-tags-overview.md) to allow storage account connectivity to the Azure storage accounts in the same region as the VMs.
28+
- Add the region-specific IP addresses for Azure Storage to an allow list.
29+
30+
- The first time you use Azure Center for SAP solutions, register the **Microsoft.Workloads** resource provider in the subscription where you have the SAP system by using [Register-AzResourceProvider](/powershell/module/az.Resources/Register-azResourceProvider):
31+
32+
```azurepowershell
33+
Register-AzResourceProvider -ProviderNamespace "Microsoft.Workloads"
34+
```
35+
36+
- An Azure account with **Azure Center for SAP solutions administrator** and **Managed Identity Operator** or equivalent role access on the subscription or resource groups where the SAP system resources exist.
37+
- A user-assigned managed identity that has **Azure Center for SAP solutions service role** access on the compute resource group and **Reader** role access on the virtual network resource group of the SAP system. Azure Center for SAP solutions uses this identity to discover your SAP system resources and register the system as a VIS resource.
38+
- Advanced Business Application Programming Central Services (ASCS), Application Server, and Database VMs of the SAP system in **Running** state.
39+
- The `sapcontrol` and `saphostctrl` executable files on ASCS, Application Server, and Database VMs:
40+
41+
- Linux VMs: `/usr/sap/hostctrl/exe`
42+
- Windows VMs: `C:\Program Files\SAP\hostctrl\exe\`
43+
44+
- The `sapstartsrv` process running on all SAP instances and for the SAP `hostctrl` agent on all VMs in the SAP system.
45+
46+
- To start `hostctrl` `sapstartsrv` on Linux VMs, run: `hostexecstart -start`
47+
- To start instance `sapstartsrv`, run: `sapcontrol -nr <instanceNr> -function StartService S0S`
48+
- To check the status of `hostctrl` `sapstartsrv` on Windows VMs, run: `C:\Program Files\SAP\hostctrl\exe\saphostexec –status`
49+
50+
- Network connectivity between ASCS, Application Server, and Database VMs for successful discovery and registration. The `ping` command for the Application Server instance hostname must succeed from the ASCS VM. The `ping` command for the database hostname must succeed from the Application Server VM.
51+
52+
- On the Application Server profile, the `SAPDBHOST`, `DBTYPE`, and `DBID` parameters must have the correct values configured for discovery and registration of the database instance.
53+
54+
## Register an SAP system
4955

5056
To register an existing SAP system in Azure Center for SAP solutions:
5157

52-
1. Use the [New-AzWorkloadsSapVirtualInstance](/powershell/module/az.workloads/New-AzWorkloadsSapVirtualInstance) to register an existing SAP system as a *Virtual Instance for SAP solutions* resource:
53-
54-
```powershell
55-
New-AzWorkloadsSapVirtualInstance `
56-
-ResourceGroupName 'TestRG' `
57-
-Name L46 `
58-
-Location eastus `
59-
-Environment 'NonProd' `
60-
-SapProduct 'S4HANA' `
61-
-CentralServerVmId '/subscriptions/sub1/resourcegroups/rg1/providers/microsoft.compute/virtualmachines/l46ascsvm' `
62-
-Tag @{k1 = "v1"; k2 = "v2"} `
63-
-ManagedResourceGroupName "acss-L46-rg" `
64-
-ManagedRgStorageAccountName 'acssstoragel46' `
65-
-ManagedResourcesNetworkAccessType 'private' `
66-
-IdentityType 'UserAssigned' `
67-
-UserAssignedIdentity @{'/subscriptions/sub1/resourcegroups/rg1/providers/Microsoft.ManagedIdentity/userAssignedIdentities/ACSS-MSI'= @{}} `
68-
```
69-
- **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.
70-
- **Name** attribute is used to specify the SAP System ID (SID) that you're registering with Azure Center for SAP solutions.
71-
- **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.
72-
73-
| **SAP application location** | **Azure Center for SAP solutions service location** |
74-
| ------------------------| --------------------------------------------------- |
75-
| East US | East US |
76-
| East US 2 | East US 2|
77-
| North Central US | South Central US |
78-
| South Central US | South Central US |
79-
| Central US | South Central US |
80-
| West US | West US 3 |
81-
| West US 2 | West US 2 |
82-
| West US 3 | West US 3 |
83-
| West Europe | West Europe |
84-
| North Europe | North Europe |
85-
| Australia East | Australia East |
86-
| Australia Central | Australia East |
87-
| East Asia | East Asia |
88-
| Southeast Asia | East Asia |
89-
| Korea Central | Korea Central |
90-
| Japan East | Japan East |
91-
| Central India | Central India |
92-
| Canada Central | Canada Central |
93-
| Brazil South | Brazil South |
94-
| UK South | UK South |
95-
| Germany West Central | Germany West Central |
96-
| Sweden Central | Sweden Central |
97-
| France Central | France Central |
98-
| Switzerland North | Switzerland North |
99-
| Norway East | Norway East |
100-
| South Africa North | South Africa North |
101-
| UAE North | UAE North |
102-
103-
- **Environment** is used to specify the type of SAP environment you're registering. Valid values are *NonProd* and *Prod*.
104-
- **SapProduct** is used to specify the type of SAP product you're registering. Valid values are *S4HANA*, *ECC*, *Other*.
105-
- **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}'.
106-
- **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.
107-
- **ManagedResourcesNetworkAccessType** specifies the network access configuration for the resources that will be deployed in the Managed Resource Group. The options to choose from are Public and Private. If 'Private' is chosen, the Storage Account service tag should be enabled on the subnets in which the SAP VMs exist. This is required for establishing connectivity between VM extensions and the managed resource group storage account. This setting is currently applicable only to Storage Account.
108-
109-
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.
110-
111-
```powershell
58+
1. Use `New-AzWorkloadsSapVirtualInstance` to register an existing SAP system as a *Virtual Instance for SAP solutions* resource:
59+
60+
```azurepowershell
61+
New-AzWorkloadsSapVirtualInstance `
62+
-ResourceGroupName 'TestRG' `
63+
-Name L46 `
64+
-Location eastus `
65+
-Environment 'NonProd' `
66+
-SapProduct 'S4HANA' `
67+
-CentralServerVmId '/subscriptions/sub1/resourcegroups/rg1/providers/microsoft.compute/virtualmachines/l46ascsvm' `
68+
-Tag @{k1 = "v1"; k2 = "v2"} `
69+
-ManagedResourceGroupName "acss-L46-rg" `
70+
-ManagedRgStorageAccountName 'acssstoragel46' `
71+
-ManagedResourcesNetworkAccessType 'private' `
72+
-IdentityType 'UserAssigned' `
73+
-UserAssignedIdentity @{'/subscriptions/sub1/resourcegroups/rg1/providers/Microsoft.ManagedIdentity/userAssignedIdentities/ACSS-MSI'= @{}} `
74+
```
75+
76+
1. After you trigger the registration process, view its status by getting the VIS resource status:
77+
78+
```azurepowershell
11279
Get-AzWorkloadsSapVirtualInstance -ResourceGroupName TestRG -Name L46
11380
```
11481

115-
## Next steps
82+
The following table describes the parameters:
83+
84+
| Parameter | Description |
85+
|---|---|
86+
| **ResourceGroupName** | The name of the existing resource group where the VIS resource is deployed. This resource group can be the same one that contains your SAP system's compute and storage resources, or a different one. |
87+
| **Name** | The SAP system ID (SID) that you're registering. |
88+
| **Location** | The Azure Center for SAP solutions service location. See the [region mapping table](#region-mapping) for valid values. |
89+
| **Environment** | The SAP environment type. Valid values are `NonProd` and `Prod`. |
90+
| **SapProduct** | The SAP product type. Valid values are `S4HANA`, `ECC`, and `Other`. |
91+
| **ManagedResourceGroupName** | The name of the managed resource group that Azure Center for SAP solutions deploys in your subscription. This group is unique for each SAP system (SID). If you don't specify a name, the default naming convention is `mrg-{SID}-{random string}`. |
92+
| **ManagedRgStorageAccountName** | The name of the storage account deployed into the managed resource group. This account is unique for each SAP system (SID). The default naming convention is `{SID}{random string}`. |
93+
| **ManagedResourcesNetworkAccessType** | The network access configuration for resources in the managed resource group. Options are `Public` and `Private`. If you choose `Private`, enable the Storage Account service tag on the subnets where the SAP VMs exist. This tag is required for connectivity between VM extensions and the managed resource group storage account. |
94+
95+
To learn more, see the [New-AzWorkloadsSapVirtualInstance](/powershell/module/az.workloads/new-azworkloadssapvirtualinstance) module reference.
96+
97+
### Region mapping
98+
99+
The following table maps SAP application locations to the Azure Center for SAP solutions service location.
100+
101+
| **SAP application location** | **Azure Center for SAP solutions service location** |
102+
|---|---|
103+
| Australia Central | Australia East |
104+
| Australia East | Australia East |
105+
| Brazil South | Brazil South |
106+
| Canada Central | Canada Central |
107+
| Central India | Central India |
108+
| Central US | South Central US |
109+
| East Asia | East Asia |
110+
| East US | East US |
111+
| East US 2 | East US 2 |
112+
| France Central | France Central |
113+
| Germany West Central | Germany West Central |
114+
| Japan East | Japan East |
115+
| Korea Central | Korea Central |
116+
| North Central US | South Central US |
117+
| North Europe | North Europe |
118+
| Norway East | Norway East |
119+
| South Africa North | South Africa North |
120+
| South Central US | South Central US |
121+
| Southeast Asia | East Asia |
122+
| Sweden Central | Sweden Central |
123+
| Switzerland North | Switzerland North |
124+
| UAE North | UAE North |
125+
| UK South | UK South |
126+
| West Europe | West Europe |
127+
| West US | West US 3 |
128+
| West US 2 | West US 2 |
129+
| West US 3 | West US 3 |
130+
131+
## Clean up resources
132+
133+
If you no longer need the Virtual Instance for SAP solutions resource that you created in this quickstart, you can delete it from the Azure portal. Go to the VIS resource in your resource group, and select **Delete**. Deleting the VIS also removes the managed resource group and its instances, but doesn't delete the underlying infrastructure like VMs or disks.
134+
135+
## Related content
116136

117137
- [Monitor SAP system from Azure portal](monitor-portal.md)
118138
- [Manage a VIS](manage-virtual-instance.md)

0 commit comments

Comments
 (0)