Explanation
Graphical user interface, text Description automatically generated with medium confidence

Box 1: A proximity placement group
Azure offers proximity placement groups. Proximity placement groups can be used to force grouping of different VM types into a single Azure datacenter to optimize the network latency between these different VM types to the best possible. In the process of deploying the first VM into such a proximity placement group, the VM gets bound to a specific datacenter.
Note: SAP applications based on the SAP NetWeaver or SAP S/4HANA architecture are sensitive to network latency between the SAP application tier and the SAP database tier. This sensitivity is the result of most of the business logic running in the application layer. Because the SAP application layer runs the business logic, it issues queries to the database tier at a high frequency, at a rate of thousands or tens of thousands per second. In most cases, the nature of these queries is simple. They can often be run on the database tier in 500 microseconds or less.
Box 2: Enable Accelerated Networking
To further reduce network latency between Azure VMs, we recommend that you choose Azure Accelerated Networking. Use it when you deploy Azure VMs for an SAP workload, especially for the SAP application layer and the SAP DBMS layer.
Box 3: Network Performance Monitor
Network Performance Monitor (NPM) - a cloud-based network monitoring solution for cloud-only, on-premises, and hybrid networking environments.
Network Performance Monitor offers three broad capabilities:
Performance Monitor: You can monitor network connectivity across cloud deployments and on-premises locations, multiple data centers, and branch offices and mission-critical multitier applications or microservices. With Performance Monitor, you can detect network issues before users complain.
Service Connectivity Monitor
ExpressRoute Monitor
Note 2: Azure Monitor for SAP Solutions is an Azure-native monitoring product for anyone running their SAP landscapes on Azure. It works with both SAP on Azure Virtual Machines and SAP on Azure Large Instances.
Reference:
https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/sap-proximity-placement-scenarios
https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/dbms_guide_general
https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/sap-on-azure-general-update-march-20

Explanation

Box 1: 4
Scenario: the Azure Resource Manager template that will be used to provision the production application servers.
Ensure that each production application server has four 1-TB data disks.
Box 2: Standard_LRS
Scenario: Minimize costs whenever possible.
Box 3: contoso.onmicrosoft.com
The network contains an on-premises Active Directory domain named ad.contoso.com.
The Initial domain: The default domain (onmicrosoft.com) in the Azure AD Tenant. For example, contoso.onmicrosoft.com.
References:
https://docs.microsoft.com/en-us/azure/active-directory/hybrid/plan-connect-userprincipalname

Explanation
Secondary indexes for very large tables can be removed from the STR file and built ONLINE with scripts after the main portion of the import has finished and post processing tasks such as configuring STMS are occurring.
References:
https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/very-large-database-migration-to-azure