Networking Support of Azure for SAP Workloads

By Ashwin Venugopal -

 



Network Security

  • It is required for any SAP production system installed on Azure to operate in Virtual Private Network(s) which is/are connected to your datacenters with Azure site-to-site or ExpressRoute connectivity. End-user access to the application should be routed through your company's intranet and the Azure's site-to-site or ExpressRoute connections to the applications hosted in Azure VM Services. This way, the network and other security policies defined for on-premises applications are extended to the application in the Azure VMs.

  • A design that is NOT supported is the segregation of the SAP application and DBMS layers into different Azure VMs that are not peered with each other. It is recommended to segregate the SAP application and DBMS layers by using subnets within an Azure virtual network instead of using the different Azure virtual networks. But, if you segregate the two layers into the different virtual networks, the two virtual networks need to be peered. The network traffic between the two peered networks are subject of transfer cost and with the huge data volume in many Terabytes exchanged between the SAP application and DBMS layers, substantial costs can be accumulated if the SAP application as well as DBMS layers are segregated between the two peered Azure virtual networks.     

Network Performance

  • It is NOT supported at all to run a SAP application layer and DBMS layer split between on-premises and Azure. Both them should completely reside either on-premises or in Azure. SAP instances split between on-premises and Azure is also NOT supported and per individual SAP system, the DBMS as well as all SAP application instance(s) must be in the same location, i.e. either on-premise or in Azure.

  • The location of the Azure data center or region relative to the own datacenter can impact the latency between the on-premises and Azure hosted SAP systems. It is advisable to select Azure regions which are close to the own location, to minimize the latency on-premises and Azure. 

  • It is not supported to configure Network Virtual Appliances (NVA) on Azure in the communication path between the SAP application and the DBMS layers of a SAP NetWeaver, or Hybris or S/4HANA based SAP system. The communication between both the layers should be a direct one. This restriction does not include Azure Security Group (ASG) as well as National Security Group (NSG) rules if those rules allows a direct communication.    

Network Reliability

Customers should use a good quality (low latency, sufficient bandwidth, no packet loss) connection between their datacenter and Azure as well as verify and monitor that the bandwidth on-prmises and Azure is sufficient to handle the communication workload.

Azure VMs and SAP HANA on Azure (Large Instances) can benefit from the use of Accelerated Networking and Proximity Placement Group.








Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning...
Read more