SAP workloads on Azure: planning and deployment checklist
31 minutes to read
This checklist is designed for customers moving SAP applications to Azure infrastructure as a service. SAP applications in this document represent SAP products running the SAP kernel, including SAP NetWeaver, S/4HANA, BW and BW/4 and others. Throughout the duration of the project, a customer and/or SAP partner should review the checklist. It's important to note that many of the checks are completed at the beginning of the project and during the planning phase. After the deployment is done, straightforward changes on deployed Azure infrastructure or SAP software releases can become complex.
Review the checklist at key milestones during your project. Doing so will enable you to detect small problems before they become large problems. You'll also have enough time to re-engineer and test any necessary changes. Don't consider this checklist complete. Depending on your situation, you might need to perform additional more checks.
The checklist doesn't include tasks that are independent of Azure. For example, SAP application interfaces change during a move to the Azure platform or to a hosting provider. SAP documentation and support notes will also contain further tasks, which are not Azure specific but need to be part of your overall planning checklist.
This checklist can also be used for systems that are already deployed. New features or changed recommendations might apply to your environment. It's useful to review the checklist periodically to ensure you're aware of new features in the Azure platform.
Main content in this document is organized in tabs, in a typical project's chronological order. See content of each tab and consider each next tab to build on top of actions done and learnings obtained in the previous phase. For production migration, the content of all tabs should be considered and not just production tab only. To help you map typical project phases with the phase definition used in this article, consult the below table.
Deployment checklist phases
Example project phases or milestones
Preparation and planning phase
Project kick-off / design and definition phase
Early validation / proof of concept / pilot
Completion of the detailed design / non-production environment builds / testing phase
During this phase, you plan the migration of your SAP workload to the Azure platform. Documents such as planning guide for SAP in Azure and Cloud Adoption Framework for SAP cover many topics and help as information in your preparation. At a minimum, during this phase you need to create the following documents, define, and discuss the following elements of the migration:
High-level design document
This document should contain:
The current inventory of SAP components and applications, and a target application inventory for Azure.
A responsibility assignment matrix (RACI) that defines the responsibilities and assignments of the parties involved. Start at a high level, and work to more granular levels throughout planning and the first deployments.
A high-level solution architecture. Best practices and example architectures from Azure Architecture Center should be consulted.
Security principles for running high-impact business data in Azure. To learn about data security, start with the Azure security documentation.
Storage strategy to cover block devices (Managed Disk) and shared filesystems (such as Azure Files or Azure NetApp Files) that should be further refined to file-system sizes and layouts in the technical design document.
Technical design document
This document should contain:
A block diagram for the solution showing the SAP and non-SAP applications and services
An SAP Quicksizer project based on business document volumes. The output of the Quicksizer is then mapped to compute, storage, and networking components in Azure. Alternatively to SAP Quicksizer, diligent sizing based on current workload of source SAP systems. Taking into account the available information, such as DBMS workload reports, SAP EarlyWatch Reports, compute and storage performance indicators.
Business continuity and disaster recovery architecture.
Detailed information about OS, DB, kernel, and SAP support pack versions. It's not necessarily true that every OS release supported by SAP NetWeaver or S/4HANA is supported on Azure VMs. The same is true for DBMS releases. Check the following sources to align and if necessary, upgrade SAP releases, DBMS releases, and OS releases to ensure SAP and Azure support. You need to have release combinations supported by SAP and Azure to get full support from SAP and Microsoft. If necessary, you need to plan for upgrading some software components. More details on supported SAP, OS, and DBMS software are documented here:
SAP note 2039619. This note defines the Oracle support matrix for Azure. Oracle supports only Windows and Oracle Linux as guest operating systems on Azure for SAP workloads. This support statement also applies for the SAP application layer that runs SAP instances, as long they contain Oracle Client.
SAP HANA-supported Azure VMs are listed on the SAP website. Details for each entry contain specifics and requirements, including supported OS version. This might not match latest OS version as per SAP note 2235581.
SMB and/or NFS volume layout and sizes, mount points where applicable
High availability, backup and disaster recovery architecture
Based on RTO and RPO, define what the high availability and disaster recovery architecture needs to look like.
Define the use of availability zones for optimal protection or availability sets within a region.
Considerations for Azure Virtual Machines DBMS deployment for SAP workloads and related documents. In Azure, using a shared disk configuration for the DBMS layer as, for example, described for SQL Server, isn't supported. Instead, use solutions like:
For disaster recovery across Azure regions, review the solutions offered by different DBMS vendors. Most of them support asynchronous replication or log shipping.
For the SAP application layer, determine whether you'll run your business regression test systems, which ideally are replicas of your production deployments, in the same Azure region or in your DR region. In the second case, you can target that business regression system as the DR target for your production deployments.
Security operations for Azure resources and workloads within
Security concept for protecting your SAP workload. This should include all aspects – networking and perimeter monitoring, application and database security, operating systems securing, and any infrastructure measures required, such as encryption. Identify the requirements with your compliance and security teams.
Microsoft recommends either Professional Direct, Premier or Unified Support contract. Identify your escalation paths and contacts for support with Microsoft. For SAP support requirements, see SAP note 2015553.
Data reduction and data migration plan for migrating SAP data into Azure. For SAP NetWeaver systems, SAP has guidelines on how to limit the volume of large amounts of data. See this SAP guide about data management in SAP ERP systems. Some of the content also applies to NetWeaver and S/4HANA systems in general.
An automated deployment approach. Many customers start with scripts, using a combination of PowerShell, CLI, Ansible and Terraform.
Microsoft developed solutions for SAP deployment automation are:
Define a regular design and deployment review cadence between you as the customer, the system integrator, Microsoft, and other involved parties.
Pilot phase (strongly recommended)
You can run a pilot before or during project planning and preparation. You can also use the pilot phase to test approaches and designs made during the planning and preparation phase. And you can expand the pilot phase to make it a real proof of concept.
We recommend that you set up and validate a full HADR solution and security design during a pilot deployment. Some customers perform scalability tests during this phase. Other customers use deployments of SAP sandbox systems as a pilot phase. We assume you've already identified a system that you want to migrate to Azure for the pilot.
Optimize data transfer to Azure. The optimal choice is highly dependent on the specific scenario. If private connectivity is required for database replication, Azure ExpressRoute is fastest if the ExpressRoute circuit has enough bandwidth. In any other scenario, transferring through the internet is faster. Optionally use a dedicated migration VPN for private connectivity to Azure. Any migration network path during pilot should mirror the use for future production systems, eliminating any impact to workloads – SAP or non-SAP - already running in Azure.
For a heterogeneous SAP migration that involves an export and import of data, test and optimize the export and import phases. For migration of large SAP environments, go through available best practices. Use the appropriate tool for the migration scenario, depending on your source and target SAP releases, DBMS and if combining migration with other tasks such as release upgrade or even Unicode or S/4HANA conversion. SAP provides Migration Monitor/SWPM, SAP DMO or DMO with system move, besides other approaches to minimize downtime available as separate service from SAP. In the latest releases of SAP DMO with system move, the use of azcopy for data transfer over the internet is supported as well, enabling the quickest network path natively.
Migrate very large databases (VLDB) to Azure for SAP
Compute / VM types
Review the resources in SAP support notes, in the SAP HANA hardware directory, and in the SAP PAM again. Make sure to match supported VMs for Azure, supported OS releases for those VM types, and supported SAP and DBMS releases.
Validate again the sizing of your application and the infrastructure you deploy on Azure. If you're moving existing applications, you can often derive the necessary SAPS from the infrastructure you use and the SAP benchmark webpage and compare it to the SAPS numbers listed in SAP note 1928533. Also keep this article on SAPS ratings in mind.
Evaluate and test the sizing of your Azure VMs for maximum storage and network throughput of the VM types you chose during the planning phase. Details of VM performance limits are available, for storage it’s important to consider the limit of max uncached disk throughput for sizing. Carefully consider sizing and temporary effects of disk and VM level bursting.
Test and determine whether you want to create your own OS images for your VMs in Azure or whether you want to use an image from the Azure compute gallery (formerly known as shared image gallery). If you're using an image from the Azure compute gallery, make sure to use an image that reflects the support contract with your OS vendor. For some OS vendors, Azure Compute Gallery lets you bring your own license images. For other OS images, support is included in the price quoted by Azure.
Using own OS images allows you to store required enterprise dependencies, such as security agents, hardening and customizations directly in the image. This way they are deployed immediately with every VM. If you decide to create your own OS images, you can find documentation in these articles:
Choosing an OS image determines the type of Azure VM’s generation. Azure supports both Hyper-V generation 1 and 2 VMs. Some VM families are available as generation 2 only, some VM families are certified for SAP use as generation 2 only (SAP note 1928533) even if Azure allows both generations. It is recommended to use generation 2 VM for every VM of SAP landscape.
At a minimum, use Azure standard SSD storage for VMs that represent SAP application layers and for deployment of DBMSs that aren't performance sensitive. Keep in mind different Azure storage types influence the single VM availability SLA.
For the different DBMS types, check the generic SAP-related DBMS documentation and DBMS-specific documentation that the first document points to. Use disk striping over multiple disks with premium storage (v1 or v2) for database data and log area. Verify lvm disk striping is active and with correct stripe size with command 'lvs -a -o+lv_layout,lv_role,stripes,stripe_size,devices' on Linux, see storage spaces properties on Windows.
Use LVM for all disks on Linux VMs, as it allows easier management and online expansion. This includes volumes on single disks, for example /usr/sap.
Test and evaluate your virtual network infrastructure and the distribution of your SAP applications across or within the different Azure virtual networks.
Evaluate the hub-and-spoke or virtual WAN virtual network architecture approach with discrete virtual network(s) spokes for SAP workload. For smaller scale, micro-segmentation approach within a single Azure virtual network. Base this evaluation on:
Advantages of a fast disconnection of the peering between Azure virtual networks as opposed to changing the network security group to isolate a subnet within a virtual network. This evaluation is for cases when applications or VMs hosted in a subnet of the virtual network became a security risk.
Central logging and auditing of network traffic between on-premises, the outside world, and the virtual datacenter you built in Azure.
Evaluate and test the data path between the SAP application layer and the SAP DBMS layer.
Placement of Azure network virtual appliances in the communication path between the SAP application and the DBMS layer of SAP systems running the SAP kernel isn't supported.
Placement of the SAP application layer and SAP DBMS in different Azure virtual networks that aren't peered isn't supported.
Test and evaluate the network latency between the SAP application layer VMs and DBMS VMs according to SAP notes 500235 and 1100926. In addition to SAP’s niping, you can use tools such as sockperf or ethr for tcp latency measurement. Evaluate the results against the network latency guidance in SAP note 1100926. The network latency should be in the moderate or good range.
Optimize network throughput on high vCPU VMs, typically used for database servers. Particularly important for HANA scale-out and any large SAP system. Follow recommendations in this article for optimization.
If deploying with availability sets and latency measurement values are not meeting SAP requirements in SAP note 1100926, consider guidance in article proximity placement groups to get optimal network latency. No usage of proximity placement groups for zonal or cross-zonal deployment patterns.
Verify correct availability, routing and secure access from the SAP landscape to any needed Internet endpoint, such as OS patch repositories, deployment tooling or service endpoint. Similarly, if your SAP environment provides a publicly accessible service such as SAP Fiori or SAProuter, verify it is reachable and secured.
High availability and disaster recovery deployments
Always use standard load balancer for clustered environments. Basic load balancer will be retired.
If you deploy the SAP application layer without defining a specific availability zone, make sure that all VMs that run SAP application instances of a single SAP system are deployed in an availability set.
When you protect SAP Central Services and the DBMS layer for high availability by using passive replication, place the two nodes for SAP Central Services in one separate availability set and the two DBMS nodes in another availability set. Do not mix application VM roles inside an availability set.
If you deploy into availability zones, you can't combine with availability sets. But you do need to make sure you deploy the active and passive central services nodes into two different availability zones. Use two availability zones that have the lowest latency between them.
If you're using Azure Load Balancer together with Linux guest operating systems, check that the Linux network parameter net.ipv4.tcp_timestamps is set to 0. This recommendation conflicts with recommendations in older versions of SAP note 2382421. The SAP note is now updated to state that this parameter needs to be set to 0 to work with Azure load balancers.
Check the SAP NetWeaver developer traces of the SAP instances to make sure there are no connection breaks between the enqueue server and the SAP work processes. You can avoid these connection breaks by setting these two registry parameters:
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveTime = 120000. For more information, see KeepAliveTime.
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveInterval = 120000. For more information, see KeepAliveInterval.
To avoid GUI timeouts between on-premises SAP GUI interfaces and SAP application layers deployed in Azure, check whether these parameters are set in the default.pfl or the instance profile:
rdisp/keepalive_timeout = 3600
rdisp/keepalive = 20
To prevent disruption of established connections between the SAP enqueue process and the SAP work processes, you need to set the enque/encni/set_so_keepalive parameter to true. See also SAP note 2743751.
If you use a Windows failover cluster configuration, make sure that the time to react on non-responsive nodes is set correctly for Azure. The article Tuning Failover Cluster Network Thresholds lists parameters and how they affect failover sensitivities. Assuming the cluster nodes are in the same subnet, you should change these parameters:
SameSubNetDelay = 2000 (number of milliseconds between “heartbeats”)
SameSubNetThreshold = 15 (maximum number of consecutive missed heartbeats)
Test your high availability and disaster recovery procedures
Simulate failover situations by using a tool such as NotMyFault (Windows) or putting operating systems in panic mode or disabling network interface with ifdown (Linux). This step will help you figure out whether your failover configurations work as designed.
Measure how long it takes to execute a failover. If the times are too long, consider:
For SUSE Linux, use SBD devices instead of the Azure Fence agent to speed up failover.
For SAP HANA, if the reload of data takes too long, consider provisioning more storage bandwidth.
Test your backup/restore sequence and timing and make corrections if you need to. Make sure that backup times are sufficient. You also need to test the restore and time restore activities. Make sure that restore times are within your RTO SLAs wherever your RTO relies on a database or VM restore process.
Test cross-region DR functionality and architecture, verify the RPO and RTO match your expectations
Test the validity of your Azure role-based access control (Azure RBAC) architecture. Segregation of duties requires to separate and limit the access and permissions of different teams. For example, SAP Basis team members should be able to deploy VMs and assign disks from Azure Storage into a given Azure virtual machine. But the SAP Basis team shouldn't be able to create its own virtual networks or change the settings of existing virtual networks. Members of the network team shouldn't be able to deploy VMs into virtual networks in which SAP application and DBMS VMs are running. Nor should members of this team be able to change attributes of VMs or even delete VMs or disks.
Make sure that all resources that need to be encrypted are encrypted. Define and implement processes to back up certificates, store and access those certificates, and restore the encrypted entities.
For storage encryption, server-side encryption with platform managed key (SSE-PMK) is enabled for every storage service used for SAP in Azure by default, including managed disks, Azure Files and Azure NetApp Files. Key management with customer managed keys can be considered, if required for customer owned key rotation.
Database native encryption is deployed by most SAP on Azure customers to protect DBMS data and backups. Transparent Data Encryption (TDE) typically has no noticeable performance overhead, greatly increases security, and should be considered. Encryption key management and location must be secured. Database encryption occurs inside the VM and is independent of any storage encryption such as SSE.
In SAP, based on SAP tracing and measurements, make these comparisons:
Inventory and baseline the current on-premises system
SAR reports / perfmon
STAT trace top 10 online reports
Collect batch job history
Focus testing to verify business processes performance. Do not compare hardware KPIs initially and in a vacuum, only when troubleshooting any performance differences.
Where applicable, compare the top 10 online reports to your current implementation.
Where applicable, compare the top 10 batch jobs to your current implementation.
Compare data transfers through interfaces into the SAP system. Focus on interfaces where you know the transfer is going between different locations, like from on-premises to Azure.
In this phase, we assume that after a successful pilot or proof of concept (POC), you're starting to deploy non-production SAP systems to Azure. Incorporate everything you learned and experienced during the POC to this deployment. All the criteria and steps listed for POCs apply to this deployment as well.
During this phase, you usually deploy development systems, unit testing systems, and business regression testing systems to Azure. We recommend that at least one non-production system in one SAP application line has the full high availability configuration that the future production system will have. Here are some tasks that you need to complete during this phase:
Before you move systems from the old platform to Azure, collect resource consumption data, like CPU usage, storage throughput, and IOPS data. Especially collect this data from the DBMS layer units, but also collect it from the application layer units. Also measure network and storage latency. Adapt your sizing and design with the captured data. Tools such as syststat, KSAR, nmon and nmon analyzer for Excel should be used to capture and present resource utilization over peak periods.
Record the availability usage time patterns of your systems. The goal is to figure out whether non-production systems need to be available all day, every day or whether there are non-production systems that can be shut down during certain phases of a week or month.
Reevaluate your OS image choice, VM generation (Generation 2 throughout the SAP landscape), and OS patch strategy.
Make sure to fulfill the SAP support requirements for Microsoft support agreements. See SAP note 2015553.
Check SAP notes related to Azure, like note 1928533, for new VM SKUs and newly supported OS and DBMS releases. Compare the pricing of new VM types against that of older VM types, so you can deploy VMs with the best price/performance ratio.
Recheck SAP support notes, the SAP HANA hardware directory, and the SAP PAM. Make sure there were no changes in supported VMs for Azure, supported OS releases on those VMs, and supported SAP and DBMS releases.
Check the SAP website for new HANA-certified SKUs in Azure. Compare the pricing of new SKUs with the ones you planned to use. Eventually, make necessary changes to use the ones that have the best price/performance ratio.
Adapt your deployment automation to use new VM types and incorporate new Azure features that you want to use.
After deployment of the infrastructure, test and evaluate the network latency between SAP application layer VMs and DBMS VMs, according to SAP notes 500235. Evaluate the results against the network latency guidance in SAP note 1100926. The network latency should be in the moderate or good range. In addition to using tools such as niping, sockperf or ethr, use SAP’s HCMT tool for network measurements between HANA VMs for scale-out or system replication.
Perform all the other checks listed for the proof-of-concept phase before applying the workload.
As the workload applies, record the resource consumption of the systems in Azure. Compare this consumption with records from your old platform. Adjust VM sizing of future deployments if you see that you have large differences. Keep in mind that when you downsize, storage, and network bandwidth of VMs will be reduced as well.
Experiment with system copy functionality and processes. The goal is to make it easy for you to copy a development system or a test system, so project teams can get new systems quickly.
Optimize and hone your team's Azure role-based access, permissions, and processes to make sure you have separation of duties. At the same time, make sure all teams can perform their tasks in the Azure infrastructure.
Exercise, test, and document high-availability and disaster recovery procedures to enable your staff to execute these tasks. Identify shortcomings and adapt new Azure functionality that you're integrating into your deployments.
Production preparation phase
In this phase, collect what you experienced and learned during your non-production deployments and apply it to future production deployments.
Complete any necessary SAP release upgrades of your production systems before moving to Azure.
Agree with the business owners on functional and business tests that need to be conducted after migration of the production system.
Make sure these tests are completed with the source systems in the current hosting location. Avoid conducting tests for the first time after the system is moved to Azure.
Test the process of migrating production systems to Azure. If you're not moving all production systems to Azure during the same time frame, build groups of production systems that need to be at the same hosting location. Test data migration including connected non-SAP applications and interfaces.
Here are some common methods:
Use DBMS methods like backup/restore in combination with SQL Server Always On, HANA System Replication, or log shipping to seed and synchronize database content in Azure.
Use backup/restore for smaller databases.
Use the SAP DMO process for supported scenarios to either move or if you need to combine your migration with an SAP release upgrade and/or move to HANA. Keep in mind that not all combinations of source DBMS and target DBMS are supported. You can find more information in the specific SAP support notes for the different releases of DMO. For example, Database Migration Option (DMO) of SUM 2.0 SP15.
Test whether data transfer throughput is better through the internet or through ExpressRoute, in case you need to move backups or SAP export files. If you're moving data through the internet, you might need to change some of your network security group/application security group rules that you'll need to have in place for future production systems.
Before moving systems from your old platform to Azure, collect resource consumption data. Useful data includes CPU usage, storage throughput, and IOPS data. Especially collect this data from the DBMS layer units, but also collect it from the application layer units. Also measure network and storage latency.
Recheck SAP notes and the required OS settings, the SAP HANA hardware directory, and the SAP PAM. Make sure there were no changes in supported VMs for Azure, supported OS releases in those VMs, and supported SAP and DBMS releases.
Update your deployment automation to consider the latest decisions you've made on VM types and Azure functionality.
Create a playbook for reacting to planned Azure maintenance events. Determine the order in which systems and VMs should be rebooted for planned maintenance.
Exercise, test, and document high-availability and disaster recovery procedures to enable your staff to execute these tasks during migration and immediately after go-live decision.
During the go-live phase, be sure to follow the playbooks you developed during earlier phases. Execute the steps that you tested and practiced. Don't accept last-minute changes in configurations and processes. Also complete these steps:
Verify that Azure portal monitoring and other monitoring tools are working. Use Azure tools such as Azure Monitor for infrastructure monitoring. Azure Monitor for SAP for a combination of OS and application KPIs, allowing you to integrate all in one dashboard for visibility during and after go-live.
For operating system key performance indicators:
On Linux ensure sysstat tool is installed and capturing details at regular intervals
After data migration, perform all the validation tests you agreed upon with the business owners. Accept validation test results only when you have results for the original source systems.
Check whether interfaces are functioning and whether other applications can communicate with the newly deployed production systems.
Check the transport and correction system through SAP transaction STMS.
Perform database backups after the system is released for production.
Perform VM backups for the SAP application layer VMs after the system is released for production.
For SAP systems that weren't part of the current go-live phase but that communicate with the SAP systems that you moved to Azure during this go-live phase, you need to reset the host name buffer in SM51. Doing so will remove the old cached IP addresses associated with the names of the application instances you moved to Azure.
This phase is about monitoring, operating, and administering the system. From an SAP point of view, the usual tasks that you were required to complete in your old hosting location apply. Complete these Azure-specific tasks as well:
Review Azure invoices for high-charging systems. Install a culture of finOps and build an Azure cost optimization capability in your organization.
Optimize price/performance efficiency on the VM side and the storage side.
Once your SAP on Azure has stabilized, your focus needs to shift to a culture of continuous sizing and capacity reviews. Unlike on-premises, where we size for a long period, right-sizing is a key benefit of running SAP on Azure workload, and diligent capacity planning will be key.
Optimize the times when you can shut down systems.
Once your solution has stabilized in Azure, consider moving away from a Pay-As-You-Go commercial model and leverage Azure Reserved Instances.
Plan and execute regular disaster recovery drills.
Define and implement your strategy around ‘ever-greeneing’, to align your own roadmap with Microsoft’s SAP on Azure roadmap to gain benefit from the advancement of technology.
SAP on Azure Infrastructure Checklist
After deploying infrastructure and applications and before each migration starts, validate that:
The correct VM types were deployed, with the correct attributes and storage configuration.
The VMs are on an up to date OS, DBMS and SAP Kernel release and patch and the OS, DB and SAP Kernel uniform throughout the landscape
VMs are secured and hardened as required and in a uniform way across the respective environment.
VMs were deployed into Azure availability zones or availability sets as planned.
Generation 2 VMs have been deployed. Generation 1 VMs should not be used for new deployments
Azure Premium Storage or Premium Storage v2 is used for latency-sensitive disks or where the single-VM SLA of 99.9% is required.
Make sure that, within the VMs, storage spaces, or stripe sets were built correctly across filesystems which require more than disk, such as DBMS data and log areas.
Correct stripe size and filesystem blocksize are used, if noted in respective DBMS guides
Azure VM storage and caching are used appropriately
Make sure that only disks holding DBMS online logs are cached with None+ Write Accelerator.
Other disks with premium storage are using cache settings none or ReadOnly, depending on use
Using Azure services – Azure Files or Azure NetApp Files – for any SMB or NFS volumes or shares. NFS volumes or SMB shares are reachable by the respective SAP environment or individual SAP system(s). Network routing to the NFS/SMB server goes through private network address space, using private endpoint if needed.
No network virtual appliances are in the communication path between the SAP application and the DBMS layer of SAP systems based on SAP NetWeaver or ABAP Platform.
All load balancers for SAP high-available components use standard load balancer with floating IP and HA ports enabled.
SAP application and DBMS VM(s) are placed in same or different subnets of one virtual network or in virtual networks directly peered.
Application and network security group rules allow communication as desired and planned, and block communication where required.
Timeout settings are set correctly, as described earlier.
If using proximity placement groups, check whether the availability sets and their VMs are deployed to the correct PPG.
Network latency between SAP application layer VMs and DBMS VMs is tested and validated as described in SAP notes 500235 and 1100926. Evaluate the results against the network latency guidance in SAP note 1100926. The network latency should be in the moderate or good range.
Encryption was implemented where necessary and with the appropriate encryption method.
Own encryption keys are protected against loss, destruction, or malicious use.
Interfaces and other applications can connect to the newly deployed infrastructure.
Automated checks and insights in SAP landscape
Several of the checks above are checked in automated way with SAP on Azure Quality Check Tool. These checks can be executed automated with the provided open-source project. While no automatic remediation of issues found is performed, the tool will warn about configuration against Microsoft recommendations.
Further tools to allow easier deployment checks and document findings, plan next remediation steps and generally optimize your SAP on Azure landscape are:
Azure Well-Architected Framework review An assessment of your workload focusing on the five main pillars of reliability, security, cost optimization, operation excellence and performance efficiency. Supports SAP workloads and recommended to running a review at start and after every project phase.
Azure Inventory Checks for SAP An open source Azure Monitor workbook, which shows your Azure inventory with intelligence to highlight configuration drift and improve quality.