Supportability matrix for the SAP automation framework
SAP Deployment Automation Framework supports deployment of all the supported SAP on Azure topologies.
Supported operating systems
The automation framework supports the following operating systems.
Control plane
The deployer virtual machine of the control plane must be deployed on Linux because the Ansible controllers only work on Linux.
SAP infrastructure
The automation framework supports deployment of the SAP on Azure infrastructure both on Linux or Windows virtual machines on x86-64 or x64 hardware.
The framework supports the following operating systems and distributions:
- Windows server 64 bit for the x86-64 platform
- SUSE Linux 64 bit for the x86-64 platform (12.x and 15.x)
- Red Hat Linux 64 bit for the x86-64 platform (7.x and 8.x)
- Oracle Linux 64 bit for the x86-64 platform
The following distributions have been tested with the framework:
| Database | Versions |
|---|---|
| Red Hat | 7.9, 8.2, 8.4, 8.6, 8.8, 9.0, 9.2 |
| SUSE | 12 SP4, 15 SP2, 15 SP3, 15 SP4, 15 SP5 |
| Oracle | 8.2, 8.4, 8.6, 8.8, 8.9 |
| Windows Server | 2016, 2019, 2022 |
Supported database back ends
The automation framework supports the following database back ends:
| Database | Versions |
|---|---|
| SAP HANA (S4/NW) | 1909, 2020, 2021, 2022, 2023 |
| ASE | 1603SP11, 1603SP14 |
| DB2 | 11.5 |
| MS SQL Server | 2016, 2019, 2022 |
Supported storage types
The automation framework supports the following storage types:
| Storage Solution | Notes |
|---|---|
| Premium_SSD | |
| Premium_SSDv2 | |
| Ultra_SSD | Limited to certain scenarios. For instance, /hana/log on eligible SKU. |
| Azure NetApp Files | For HANA, AVG support also available |
| Azure Files NFS | For shared files, not for database files |
Encryption using Azure Disk Encryption with customer managed keys is supported.
Supported SAP topologies
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.
| Deployment | Notes |
|---|---|
| Standalone | All SAP roles are installed on a single server. |
| 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. |
| Distributed (HA) | Database and/or SAP Central Services are deployed highly available using Pacemaker |
You can also deploy the automation framework to a standalone server by specifying a configuration without an application tier.
Supported deployment topologies
The automation framework supports both green-field and brown-field deployments.
Green-field deployments
In a green-field deployment, the automation framework creates all the required resources.
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.
Brown-field deployments
In a brown-field deployment, you can use existing Azure resources as part of the deployment.
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.
Supported Azure features
The automation framework can use the following Azure services, features, and capabilities:
- Azure Virtual Machines
- Accelerated networking
- Anchor VMs (optional)
- SSH authentication/Username and password authentication
- SKU configuration
- Custom images
- New or existing proximity placement groups
- Azure Virtual Network
- Deployment in networks peered to your SAP network
- Customer-specified IP addressing
- Azure-provided IP addressing
- New or existing network security groups
- New or existing virtual networks
- New or existing subnets
- Private Endpoints
- Azure availability zones
- High availability (HA)
- Azure Firewall
- Azure Load Balancer
- Standard load balancers
- Azure Storage
- Boot diagnostics storage
- SAP installation media storage
- Terraform state file storage
- Cloud Witness storage for HA scenarios
- Azure Key Vault
- New or existing key vaults
- Customer-managed keys for disk encryption
- Azure application security groups
- Azure Files for NFS
- Azure NetApp Files
- For shared files
- For database files
Next step
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for