Merge pull request #115083 from rdeltcheva/ilb-add-link

Add information for 3rd party firewall

Author: ShannonLeavitt

articles/virtual-machines/workloads/sap/get-started.md

@@ -15,7 +15,7 @@ ms.service: virtual-machines-linux
 ms.topic: article
 ms.tgt_pltfrm: vm-linux
 ms.workload: infrastructure-services
-ms.date: 05/11/2020
+ms.date: 05/12/2020
 ms.author: juergent
 ms.custom: H1Hack27Feb2017
 
@@ -110,6 +110,7 @@ For information on integration of Azure services into SAP components, see:
 
 ## Change Log
 
+- 05/12/2020: Change in [Public endpoint connectivity for VMs using Azure Standard ILB in SAP HA scenarios](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/high-availability-guide-standard-load-balancer-outbound-connections) to update links and add information for 3rd party firewall configuration
 - 05/11/2020: Change in [High availability of SAP HANA on Azure VMs on SLES](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/sap-hana-high-availability) to set resource stickiness to 0 for the netcat resource, as that leads to more streamlined failover 
 - 05/05/2020: Changes in [Azure Virtual Machines planning and implementation for SAP NetWeaver](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/planning-guide) to express that Gen2 deployments are available for Mv1 VM family
 - 04/24/2020: Changes in [SAP HANA scale-out with standby node on Azure VMs with ANF on SLES](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/sap-hana-scale-out-standby-netapp-files-suse), in [SAP HANA scale-out with standby node on Azure VMs with ANF on RHEL](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/sap-hana-scale-out-standby-netapp-files-rhel), [High availability for SAP NetWeaver on Azure VMs on SLES with ANF](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/high-availability-guide-suse-netapp-files) and [High availability for SAP NetWeaver on Azure VMs on RHEL with ANF](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/high-availability-guide-rhel-netapp-files) to add clarification that the IP addresses for ANF volumes are automatically assigned

articles/virtual-machines/workloads/sap/high-availability-guide-standard-load-balancer-outbound-connections.md

@@ -14,7 +14,7 @@ ms.devlang: NA
 ms.topic: article
 ms.tgt_pltfrm: vm-windows
 ms.workload: infrastructure-services
-ms.date: 02/07/2020
+ms.date: 05/12/2020
 ms.author: radeltch
 
 ---
@@ -174,7 +174,7 @@ You could use proxy to allow Pacemaker calls to the Azure management API public
 ### Important considerations
 
   - If there is already corporate proxy in place, you could route outbound calls to public end points through it. Outbound calls to public end points will go through the corporate control point.  
-  - Make sure the proxy configuration allows outbound connectivity to Azure management API: `https://management.azure.com`  
+  - Make sure the proxy configuration allows outbound connectivity to Azure management API: `https://management.azure.com` and `https://login.microsoftonline.com`  
   - Make sure there is a route from the VMs to the Proxy  
   - Proxy will handle only HTTP/HTTPS calls. If there is additional need to make outbound calls to public end point over different protocols (like RFC), alternative solution will be needed  
   - The Proxy solution must be highly available, to avoid instability in the Pacemaker cluster  
@@ -218,6 +218,10 @@ To allow pacemaker to communicate with the Azure management API, perform the fol
      sudo pcs property set maintenance-mode=false
      ```
 
+## Other solutions
+
+If outbound traffic is routed via third party firewall, make sure the firewall configuration allows outbound connectivity to the Azure management API: `https://management.azure.com` and `https://login.microsoftonline.com`.  
+
 ## Next steps
 
 * [Learn how to configure Pacemaker on SUSE in Azure](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/high-availability-guide-suse-pacemaker)