Merge pull request #286311 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/azure-arc/servers/prerequisites.md

@@ -40,7 +40,7 @@ Azure Arc supports the following Windows and Linux operating systems. Only x86-6
 
 * AlmaLinux 9
 * Amazon Linux 2 and 2023
-* Azure Linux (CBL-Mariner) 2.0
+* Azure Linux (CBL-Mariner) 2.0 and 3.0
 * Azure Stack HCI
 * Debian 11, and 12
 * Oracle Linux 7, 8, and 9

articles/load-balancer/egress-only.md

@@ -246,7 +246,7 @@ In this section, you'll add the virtual machine you created previously to the ba
 
 1. Select **Connect**.
 
-1. Open Internet Explorer.
+1. Open Microsoft Edge browser.
 
 1.  Enter **https://whatsmyip.org** in the address bar.
 
@@ -292,7 +292,7 @@ In this section, you'll add the virtual machine you created previously to the ba
 
 1. Select **Connect**.
 
-1. Open Internet Explorer.
+1. Open Microsoft Edge browser.
 
 1. Enter **https://whatsmyip.org** in the address bar.
 

articles/load-balancer/load-balancer-outbound-connections.md

@@ -150,7 +150,7 @@ For more information about connection pooling with Azure App Service, see [Troub
 
 New outbound connections to a destination IP fail when port exhaustion occurs. Connections succeed when a port becomes available. This exhaustion occurs when the 64,000 ports from an IP address are spread thin across many backend instances. For guidance on mitigation of SNAT port exhaustion, see the [troubleshooting guide](./troubleshoot-outbound-connection.md).  
 
-### Port reuse
+## Port reuse
 For TCP connections, the load balancer uses a single SNAT port for every destination IP and port. For connections to the same destination IP, a single SNAT port can be reused as long as the destination port differs. Reuse isn't possible when there already exists a connection to the same destination IP and port.
 
 For UDP connections, the load balancer uses a **port-restricted cone NAT** algorithm, which consumes one SNAT port per destination IP, regardless of the destination port. 

articles/security/fundamentals/network-best-practices.md

@@ -47,7 +47,7 @@ Best practices for logically segmenting subnets include:
 **Detail**: Use [CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing)-based subnetting principles to create your subnets.
 
 **Best practice**: Create network access controls between subnets. Routing between subnets happens automatically, and you don't need to manually configure routing tables. By default, there are no network access controls between the subnets that you create on an Azure virtual network.   
-**Detail**: Use a [network security group](../../virtual-network/manage-network-security-group.md) to protect against unsolicited traffic into Azure subnets. Network security groups (NSGs) are simple, stateful packet inspection devices. NSGs use the 5-tuple approach (source IP, source port, destination IP, destination port, and layer 4 protocol) to create allow/deny rules for network traffic. You allow or deny traffic to and from a single IP address, to and from multiple IP addresses, or to and from entire subnets.
+**Detail**: Use a [network security group](../../virtual-network/manage-network-security-group.md) to protect against unsolicited traffic into Azure subnets. Network security groups (NSGs) are simple, stateful packet inspection devices. NSGs use the 5-tuple approach (source IP, source port, destination IP, destination port and protocol) to create allow/deny rules for network traffic. You allow or deny traffic to and from a single IP address, to and from multiple IP addresses, or to and from entire subnets.
 
 When you use network security groups for network access control between subnets, you can put resources that belong to the same security zone or role in their own subnets.
 

articles/storage/container-storage/use-container-storage-with-managed-disks.md

@@ -75,7 +75,7 @@ Follow these steps to create a dynamic storage pool for Azure Disks.
        azureDisk:
          skuName: PremiumV2_LRS
          iopsReadWrite: 5000
-         MbpsReadWrite: 200
+         mbpsReadWrite: 200
      resources:
        requests:
          storage: 1Ti

articles/web-application-firewall/ag/application-gateway-crs-rulegroups-rules.md

@@ -392,6 +392,7 @@ The following rule groups and rules are available when using Web Application Fir
 |942100|SQL Injection Attack Detected via libinjection|
 |942110|SQL Injection Attack: Common Injection Testing Detected|
 |942120|SQL Injection Attack: SQL Operator Detected|
+|942130|SQL Injection Attack: SQL Tautology Detected.|
 |942140|SQL Injection Attack: Common DB Names Detected|
 |942150|SQL Injection Attack|
 |942160|Detects blind sqli tests using sleep() or benchmark().|

includes/elastic-san-regions.md

@@ -35,4 +35,13 @@ The following list contains the regions Elastic SAN is currently available in, a
 - Norway East - LRS
 - UAE North - LRS
 - India Central - LRS
-  
+
+Elastic SAN is also available in the following regions, but without Availability Zone support: 
+- Canada East - LRS
+- North Central US - LRS
+- Japan West - LRS
+
+To enable these regions, run the following command to register the necessary feature flag: 
+```azurepowershell
+Register-AzProviderFeature -FeatureName "EnableElasticSANRegionalDeployment" -ProviderNamespace "Microsoft.ElasticSan"
+```