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
title: Supportability matrix for SAP Deployment Automation Framework
3
-
description: Supported platforms, topologies, and capabilities for SAP Deployment Automation Framework.
3
+
description: Learn about the supported operating systems, databases, storage types, and deployment topologies for SAP Deployment Automation Framework.
4
4
author: kimforss
5
5
ms.author: kimforss
6
-
ms.reviewer: kimforss
7
-
ms.date: 3/26/2026
6
+
ms.date: 04/02/2026
8
7
ms.topic: concept-article
9
8
ms.service: sap-on-azure
10
9
ms.subservice: sap-automation
11
10
# Customer intent: As an IT operations manager, I want to understand the supported platforms and configurations of the SAP Deployment Automation Framework, so that I can effectively deploy and manage SAP solutions in our Azure environment.
12
11
---
13
12
14
-
# Supportability matrix for the SAP automation framework
13
+
# Supportability matrix for SAP Deployment Automation Framework
15
14
16
-
[SAP Deployment Automation Framework](deployment-framework.md) supports deployment of all the supported SAP on Azure topologies.
15
+
SAP Deployment Automation Framework is an open-source orchestration tool for deploying, installing,
16
+
and maintaining SAP environments on Azure. Before you plan or modify a deployment, confirm that your
17
+
framework supports the target operating systems, databases, storage options, and topologies.
17
18
18
-
## Supported operating systems
19
-
20
-
The automation framework supports the following operating systems.
21
-
22
-
### Control plane
19
+
-**Control plane**: The deployer virtual machine (VM) of the control plane must run on Linux
20
+
because Ansible controllers only work on Linux.
23
21
24
-
The deployer virtual machine of the control plane must be deployed on Linux because the Ansible controllers only work on Linux.
22
+
-**SAP infrastructure**: The automation framework supports deployment of the SAP on Azure
23
+
infrastructure on both Linux and Windows VMs on x86-64 or x64 hardware.
25
24
26
-
### SAP infrastructure
25
+
This article lists the platforms, database back ends, storage types, and SAP topologies that the
26
+
automation framework supports. For an overview of the framework, see
> | Ultra_SSD | Limited to certain scenarios. For instance, /hana/log on eligible SKU. |
73
-
> | Azure NetApp Files | For HANA, AVG support also available |
74
-
> | Azure Files NFS | For shared files, not for database files |
63
+
| Storage Solution | Notes |
64
+
|--|--|
65
+
| Premium_SSD ||
66
+
| Premium_SSD v2 ||
67
+
| Ultra_SSD | Limited to certain scenarios. For instance, `/hana/log` on eligible SKU. |
68
+
| Azure NetApp Files | For HANA, AVG support also available. |
69
+
| Azure Files NFS | For shared files, not for database files. |
75
70
76
-
Encryption using Azure Disk Encryption with customermanaged keys is supported.
71
+
The automation framework supports encryption with Azure Disk Encryption and customer-managed keys.
77
72
78
73
## Supported SAP topologies
79
74
80
-
By default, the automation framework deploys with database and application tiers. The application tier is split into three more tiers: application, central services, and web dispatchers.
81
-
75
+
By default, the automation framework deploys with database and application tiers. The application
76
+
tier is split into three more tiers: application, central services, and web dispatchers.
> | Standalone | All SAP roles are installed on a single server. |
87
-
> | Distributed | Separate Database server and application tier. The application tier can further split by having SAP central services on one VM and one or more application servers on another. |
88
-
> | Distributed (HA) | Database and/or SAP Central Services are deployed highly available using Pacemaker |
78
+
| Deployment | Notes |
79
+
|--|--|
80
+
| Standalone | All SAP roles are installed on a single server. |
81
+
| Distributed | Separate Database server and application tier. The application tier can further split by having SAP central services on one VM and one or more application servers on another. |
82
+
| Distributed (HA) | Database and/or SAP Central Services are deployed highly available using Pacemaker. |
89
83
90
-
91
-
You can also deploy the automation framework to a standalone server by specifying a configuration without an application tier.
84
+
You can also deploy the automation framework to a standalone server by specifying a configuration
85
+
without an application tier.
92
86
93
87
## Supported deployment topologies
94
88
@@ -98,53 +92,68 @@ The automation framework supports both green-field and brown-field deployments.
98
92
99
93
In a green-field deployment, the automation framework creates all the required resources.
100
94
101
-
In this scenario, you provide the relevant data (address spaces for networks and subnets) when you configure the environment. For more examples, see [Configure the workload zone](configure-workload-zone.md).
95
+
In this scenario, you provide the relevant data (address spaces for networks and subnets) when you
96
+
configure the environment. For more examples, see
97
+
[Configure the workload zone](configure-workload-zone.md).
102
98
103
99
### Brown-field deployments
100
+
104
101
In a brown-field deployment, you can use existing Azure resources as part of the deployment.
105
102
106
-
In this scenario, you provide the Azure resource identifiers for the existing resources when you configure the environment. For more examples, see [Configure the workload zone](configure-workload-zone.md).
103
+
In this scenario, you provide the Azure resource identifiers for the existing resources when you
104
+
configure the environment. For more examples, see
105
+
[Configure the workload zone](configure-workload-zone.md).
107
106
108
107
## Supported Azure features
109
108
110
-
The automation framework can use the following Azure services, features, and capabilities:
109
+
The automation framework can use the following Azure services, features, and capabilities when you
110
+
deploy and manage SAP environments:
111
111
112
112
- Azure Virtual Machines
113
113
- Accelerated networking
114
114
- Anchor VMs (optional)
115
-
- SSH authentication/Username and password authentication
115
+
- SSH or username and password authentication
116
116
- SKU configuration
117
117
- Custom images
118
118
- New or existing proximity placement groups
119
+
119
120
- Azure Virtual Network
120
121
- Deployment in networks peered to your SAP network
121
122
- Customer-specified IP addressing
122
123
- Azure-provided IP addressing
123
124
- New or existing network security groups
124
125
- New or existing virtual networks
125
126
- New or existing subnets
126
-
- Private Endpoints
127
+
- Private endpoints
128
+
127
129
- Azure availability zones
128
130
- High availability (HA)
131
+
129
132
- Azure Firewall
133
+
130
134
- Azure Load Balancer
131
135
- Standard load balancers
136
+
132
137
- Azure Storage
133
138
- Boot diagnostics storage
134
139
- SAP installation media storage
135
140
- Terraform state file storage
136
141
- Cloud Witness storage for HA scenarios
142
+
137
143
- Azure Key Vault
138
144
- New or existing key vaults
139
145
- Customer-managed keys for disk encryption
146
+
140
147
- Azure application security groups
148
+
141
149
- Azure Files for NFS
150
+
142
151
- Azure NetApp Files
143
152
- For shared files
144
153
- For database files
145
154
155
+
## Related content
146
156
147
-
## Next step
148
-
149
-
> [!div class="nextstepaction"]
150
-
> [Get started with the automation framework](get-started.md)
157
+
-[Get started with SAP Deployment Automation Framework](get-started.md)
158
+
-[Deploy the control plane](deploy-control-plane.md)
159
+
-[Configure the workload zone](configure-workload-zone.md)
0 commit comments