Update load balancer creation steps in windows HA document

Author: dennispadia

articles/sap/workloads/sap-ascs-ha-multi-sid-wsfc-azure-shared-disk.md

@@ -2,19 +2,12 @@
 title: SAP ASCS/SCS multi-SID HA with WSFC and Azure shared disk | Microsoft Docs
 description: Learn about multi-SID high availability for an SAP ASCS/SCS instance with Windows Server Failover Clustering and an Azure shared disk.
 services: virtual-machines-windows,virtual-network,storage
-documentationcenter: saponazure
 author: rdeltcheva
 manager: juergent
-editor: ''
-tags: azure-resource-manager
-keywords: ''
 ms.assetid: cbf18abe-41cb-44f7-bdec-966f32c89325
 ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
-ms.topic: article
-ms.tgt_pltfrm: vm-windows
-ms.workload: infrastructure-services
-ms.date: 12/16/2022
+ms.date: 01/19/2024
 ms.author: radeltch
 ms.custom: H1Hack27Feb2017, devx-track-azurepowershell
 ---
@@ -145,59 +138,35 @@ The steps in this article remain the same for both deployment types. But if your
 
 ### Create an Azure internal load balancer
 
-SAP ASCS, SAP SCS, and SAP ERS2 use virtual host names and virtual IP addresses. On Azure, a [load balancer](../../load-balancer/load-balancer-overview.md) is required to use a virtual IP address.
-We strongly recommend using a [standard load balancer](../../load-balancer/quickstart-load-balancer-standard-public-portal.md).
+For multi-sid configuration of SAP SID, PR2, you could use the same internal load balancer that you have created for SAP SID, PR1 system. For the ENSA1 architecture on Windows, you would need only one virtual IP address for SAP ASCS/SCS. On the other hand, the ENSA2 architecture necessitates two virtual IP addresses - one for SAP ASCS and another for ERS2.
+
+Configure additional frontend IP and load balancing rule for SAP SID, PR2 system on the existing load balancer using following guidelines. This section assume that that the configuration of standard internal load balancer for SAP SID, PR1 is already in place as described in [create load balancer](./sap-high-availability-infrastructure-wsfc-shared-disk.md#create-azure-internal-load-balancer).
+
+1. Open the same standard internal load balancer that you have created for SAP SID, PR1 system.
+2. **Frontend IP Configuration:** Create frontend IP (example: 10.0.0.45).
+3. **Backend Pool:** Backend Pool is same as that of SAP SID PR1 system.
+4. **Inbound rules:** Create load balancing rule.
+     - Frontend IP address: Select frontend IP
+     - Backend pool: Select backend pool
+     - Check "High availability ports"
+     - Protocol: TCP
+     - Health Probe: Create health probe with below details
+       - Protocol: TCP
+       - Port: [for example: 620<Instance-no.> for SAP SID, PR2 ASCS]
+       - Interval: 5
+       - Probe Threshold: 2
+     - Idle timeout (minutes): 30
+     - Check "Enable Floating IP"
+5. Applicable to only ENSA2 architecture: Create additional frontend IP (10.0.0.44), load balancing rule (use 621<Instance-no.> for ERS2 health probe port) as described in point 1 and 3.
+
+> [!NOTE]
+> Health probe configuration property numberOfProbes, otherwise known as "Unhealthy threshold" in Portal, isn't respected. So to control the number of successful or failed consecutive probes, set the property "probeThreshold" to 2. It is currently not possible to set this property using Azure portal, so use either the [Azure CLI](/cli/azure/network/lb/probe) or [PowerShell](/powershell/module/az.network/new-azloadbalancerprobeconfig) command.
 
-You need to add configuration to the existing load balancer for the second SAP SID instance, PR2, for ASCS, SCS, or ERS. The configuration for the first SAP SID, PR1, should be already in place.  
-
-#### (A)SCS PR2 [instance number 02]
-
-- Front-end configuration:
-  - Static ASCS/SCS IP address 10.0.0.45.
-- Back-end configuration:
-  - Already in place. The VMs were added to the back-end pool during configuration of SAP SID PR1.
-- Probe port:
-  - Port 620*nr* [62002]. Leave the default options for protocol (TCP), interval (5), and unhealthy threshold (2).
-- Load-balancing rules:
-  - If you're using a standard load balancer, select high-availability (HA) ports.
-  - If you're using a basic load balancer, create load-balancing rules for the following ports:
-    - 32*nr* TCP [3202]
-    - 36*nr* TCP [3602]
-    - 39*nr* TCP [3902]
-    - 81*nr* TCP [8102]
-    - 5*nr*13 TCP [50213]
-    - 5*nr*14 TCP [50214]
-    - 5*nr*16 TCP [50216]
-
-  - Associate load-balancing rules with the PR2 ASCS front-end IP address, the health probe, and the existing back-end pool.  
-
-  - Make sure that idle timeout is set to the maximum value of 30 minutes, and that floating IP (direct server return) is enabled.
-
-#### ERS2 PR2 [instance number 12]
-
-Because ERS2 is clustered, you must configure the ERS2 virtual IP address on an Azure internal load balancer in addition to the preceding SAP ASCS/SCS IP address. This section applies only if you're using the ERS2 architecture for PR2.  
-
-- New front-end configuration:
-  - Static SAP ERS2 IP address 10.0.0.46.
-
-- Back-end configuration:
-  - The VMs were already added to the internal load balancer's back-end pool.  
-
-- New probe port:
-  - Port 621*nr* [62112]. Leave the default options for protocol (TCP), interval (5), and unhealthy threshold (2).
-
-- New load-balancing rules:
-  - If you're using a standard load balancer, select HA ports.
-  - If you're using a basic load balancer, create load-balancing rules for the following ports:
-    - 32*nr* TCP [3212]
-    - 33*nr* TCP [3312]
-    - 5*nr*13 TCP [51212]
-    - 5*nr*14 TCP [51212]
-    - 5*nr*16 TCP [51212]
-  
-  - Associate load-balancing rules with the PR2 ERS2 front-end IP address, the health probe, and the existing back-end pool.  
+> [!IMPORTANT]
+> A floating IP address isn't supported on a network interface card (NIC) secondary IP configuration in load-balancing scenarios. For details, see [Azure Load Balancer limitations](../../load-balancer/load-balancer-multivip-overview.md#limitations). If you need another IP address for the VM, deploy a second NIC.
 
-  - Make sure that idle timeout is set to the maximum value of 30 minutes, and that floating IP (direct server return) is enabled.
+> [!NOTE]
+> When VMs without public IP addresses are placed in the back-end pool of an internal (no public IP address) Standard Azure load balancer, there will be no outbound internet connectivity unless you perform additional configuration to allow routing to public endpoints. For details on how to achieve outbound connectivity, see [Public endpoint connectivity for virtual machines using Azure Standard Load Balancer in SAP high-availability scenarios](./high-availability-guide-standard-load-balancer-outbound-connections.md).  
 
 ### Create and attach a second Azure shared disk