Merge pull request #292026 from MicrosoftDocs/repo_sync_working_branch

PhilKang0704 · web-flow · commit 2b2b74b717d5 · 2024-12-17T13:20:32.000+08:00
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
diff --git a/articles/nat-gateway/troubleshoot-nat-connectivity.md b/articles/nat-gateway/troubleshoot-nat-connectivity.md
@@ -56,7 +56,7 @@ You observe a drop in the datapath availability of NAT gateway, which coincides
 * If your investigation is inconclusive, open a support case to [further troubleshoot](#more-troubleshooting-guidance).
 
 >[!NOTE]
->It is important to understand why SNAT port exhaustion occurs. Make sure you use the right patterns for scalable and reliable scenarios. Adding more SNAT ports to a scenario without understanding the cause of the demand should be a last resort. If you do not understand why your scenario is applying pressure on SNAT port inventory, adding more SNAT ports by adding more IP addresses will only delay the same exhaustion failure as your application scales.  You may be masking other inefficiencies and anti-patterns. For more informations, see [best practices for efficient use of outbound connections](#outbound-connectivity-best-practices).
+>It is important to understand why SNAT port exhaustion occurs. Make sure you use the right patterns for scalable and reliable scenarios. Adding more SNAT ports to a scenario without understanding the cause of the demand should be a last resort. If you do not understand why your scenario is applying pressure on SNAT port inventory, adding more SNAT ports by adding more IP addresses will only delay the same exhaustion failure as your application scales.  You may be masking other inefficiencies and anti-patterns. For more information, see [best practices for efficient use of outbound connections](#outbound-connectivity-best-practices).
 
 ### Possible solutions for TCP connection timeouts
 
diff --git a/articles/network-watcher/network-watcher-visualize-nsg-flow-logs-open-source-tools.md b/articles/network-watcher/network-watcher-visualize-nsg-flow-logs-open-source-tools.md
@@ -37,7 +37,7 @@ By connecting NSG flow logs with the Elastic Stack, we can create a Kibana dashb
 
 The following instructions are used to install Elasticsearch in Ubuntu Azure VMs. For instructions on how to install elastic search in Red Hat Enterprise Linux, see [Install Elasticsearch with RPM](https://www.elastic.co/guide/en/elasticsearch/reference/8.6/rpm.html).
 
-1. The Elastic Stack from version 5.0 and above requires Java 8. Run the command `java -version` to check your version. If you don't have Java installed, see the documentation on the [Azure-suppored JDKs](/azure/developer/java/fundamentals/java-support-on-azure).
+1. The Elastic Stack from version 5.0 and above requires Java 8. Run the command `java -version` to check your version. If you don't have Java installed, see the documentation on the [Azure-supported JDKs](/azure/developer/java/fundamentals/java-support-on-azure).
 2. Download the correct binary package for your system:
 
    ```bash
diff --git a/articles/network-watcher/nsg-flow-logs-policy-portal.md b/articles/network-watcher/nsg-flow-logs-policy-portal.md
@@ -92,7 +92,7 @@ To assign the *deployIfNotExists* policy:
     | Setting | Value |
     | --- | --- |
     | **NSG Region** | Select the region of your network security group that you're targeting with the policy. |
-    | **Storage id** | Enter the full resource ID of the storage account. The storage account must be in the same region as the network security group. The format of storage resource ID is `/subscriptions/<SubscriptionID>/resourceGroups/<ResouceGroupName>/providers/Microsoft.Storage/storageAccounts/<StorageAccountName>`. |
+    | **Storage id** | Enter the full resource ID of the storage account. The storage account must be in the same region as the network security group. The format of storage resource ID is `/subscriptions/<SubscriptionID>/resourceGroups/<ResourceGroupName>/providers/Microsoft.Storage/storageAccounts/<StorageAccountName>`. |
     | **Network Watchers RG** | Select the resource group of your Azure Network Watcher instance. |
     | **Network Watcher name** | Enter the name of your Network Watcher instance. |
 
diff --git a/articles/network-watcher/traffic-analytics-schema.md b/articles/network-watcher/traffic-analytics-schema.md
@@ -70,7 +70,7 @@ let TableWithBlobId =
 | extend blobTime = format_datetime(todatetime(FlowIntervalStartTime_t), "yyyy MM dd hh")
 | extend nsgComponents = split(toupper(NSGList_s), "/"), dateTimeComponents = split(blobTime, " ")
 | extend BlobPath = strcat("https://", saName,
-                        "@insights-logs-networksecuritygroupflowevent/resoureId=/SUBSCRIPTIONS/", nsgComponents[0],
+                        "@insights-logs-networksecuritygroupflowevent/resourceId=/SUBSCRIPTIONS/", nsgComponents[0],
                         "/RESOURCEGROUPS/", nsgComponents[1],
                         "/PROVIDERS/MICROSOFT.NETWORK/NETWORKSECURITYGROUPS/", nsgComponents[2],
                         "/y=", dateTimeComponents[0], "/m=", dateTimeComponents[1], "/d=", dateTimeComponents[2], "/h=", dateTimeComponents[3],
@@ -147,7 +147,7 @@ The following table lists the fields in the schema and what they signify for net
 > | **LoadBalancer2_s** | \<SubscriptionID\>/\<ResourceGroupName\>/\<LoadBalancerName\> | Load balancer associated with the Destination IP in the flow. |
 > | **LocalNetworkGateway1_s** | \<SubscriptionID\>/\<ResourceGroupName\>/\<LocalNetworkGatewayName\> | Local network gateway associated with the Source IP in the flow. |
 > | **LocalNetworkGateway2_s** | \<SubscriptionID\>/\<ResourceGroupName\>/\<LocalNetworkGatewayName\> | Local network gateway associated with the Destination IP in the flow. |
-> | **ConnectionType_s** | - VNetPeering <br> - VpnGateway <br> - ExpressRoute | The onnection Type. |
+> | **ConnectionType_s** | - VNetPeering <br> - VpnGateway <br> - ExpressRoute | The Connection Type. |
 > | **ConnectionName_s** | \<SubscriptionID\>/\<ResourceGroupName\>/\<ConnectionName\> | The connection Name. For flow type P2S, it is formatted as \<gateway name\>_\<VPN Client IP\>. |
 > | **ConnectingVNets_s**	| Space separated list of virtual network names | In case of hub and spoke topology, hub virtual networks are populated here. |
 > | **Country_s** | Two letter country code (ISO 3166-1 alpha-2) | Populated for flow type ExternalPublic. All IP addresses in PublicIPs_s field share the same country code. |
diff --git a/articles/networking/create-zero-trust-network-web-apps.md b/articles/networking/create-zero-trust-network-web-apps.md
@@ -395,7 +395,7 @@ You'll deploy Azure Firewall to perform packet inspection between the applicatio
     | Firewall tier | Select **Premium**. |
     | Firewall policy | Select **Add new**.|
     | **Create a new Firewall Policy** | |
-    | Policy name | Enter **myFirewalPolicy**. |
+    | Policy name | Enter **myFirewallPolicy**. |
     | Policy tier | Select **Premium** and select **OK**. |
     | Choose a virtual network | Select **Use existing**. |
     | Virtual network | Select **hub-vnet**. |
@@ -408,7 +408,7 @@ You'll deploy Azure Firewall to perform packet inspection between the applicatio
 In this task, you'll configure the firewall policy used for packet inspection.
 
 1. Navigate to the Azure Firewall that you previously created.
-1. In the **Overview** page, locate and select the link to the **myFirewalPolicy** firewall policy.
+1. In the **Overview** page, locate and select the link to the **myFirewallPolicy** firewall policy.
 1. In the **Firewall Policy** page, select the **IDPS** under **Settings**.
 1. On the **IDPS** page, select **Alert and deny** and then select **Apply**. Wait for the firewall policy to complete updating before proceeding to the next step.
 1. Select **TLS inspection** under **Settings**
diff --git a/articles/openshift/howto-bring-nsg.md b/articles/openshift/howto-bring-nsg.md
@@ -80,7 +80,7 @@ This article shows how to use the "bring your own" Network Security Group (NSG)
     ```
     az aro create \
     --resource-group BASE_RESOURCE_GROUP_NAME \
-    --name CLSUTER_NAME \
+    --name CLUSTER_NAME \
     --vnet VNET_NAME \
     --master-subnet MASTER_SUBNET_NAME \
     --worker-subnet WORKER_SUBNET_NAME \
diff --git a/articles/openshift/quickstart-openshift-arm-bicep-template.md b/articles/openshift/quickstart-openshift-arm-bicep-template.md
@@ -164,7 +164,7 @@ Save the following example as *azuredeploy.json*:
           "type": "string",
           "defaultValue": "172.30.0.0/16",
           "metadata": {
-              "decription": "Cidr of service"
+              "description": "Cidr of service"
           }
       },
       "clusterName" : {
diff --git a/articles/operational-excellence/relocation-automation.md b/articles/operational-excellence/relocation-automation.md
@@ -61,7 +61,7 @@ In the diagram below, the red flow lines illustrate redeployment of the target i
 
 1. Deploy the template using [ARM](/azure/automation/quickstart-create-automation-account-template), [Portal](/azure/automation/automation-create-standalone-account?tabs=azureportal)  or [PowerShell](/powershell/module/az.automation/import-azautomationrunbook?view=azps-11.2.0&preserve-view=true).
 
-1. Use PowerShell to export all associated runbooks from the source Azure Automation instance and import them to the target instance. Reconfigure the properties as per target. For more information, see [Export-AzAuotomationRunbook](/powershell/module/az.automation/export-azautomationrunbook?view=azps-11.2.0&viewFallbackFrom=azps-9.4.0&preserve-view=true).
+1. Use PowerShell to export all associated runbooks from the source Azure Automation instance and import them to the target instance. Reconfigure the properties as per target. For more information, see [Export-AzAutomationRunbook](/powershell/module/az.automation/export-azautomationrunbook?view=azps-11.2.0&viewFallbackFrom=azps-9.4.0&preserve-view=true).
 
 1. Associate the relocated Azure Automation instance to the target Log Analytics workspace.
 
diff --git a/articles/operational-excellence/relocation-firewall.md b/articles/operational-excellence/relocation-firewall.md
@@ -142,7 +142,7 @@ If you're running classic firewall rules without Firewall policy, migrate to Fir
 1. Review and update the configuration for the topics below to reflect the changes required for the target region.
     - **IP Groups.** To include IP addresses from the target region, if different from the source, *IP Groups* should be reviewed. The IP addresses included in the groups must be modified.
     - **Zones.**  Configure the [availability Zones (AZ)](../reliability/availability-zones-overview.md) in the target region.
-    - **Forced Tunneling.**  [Ensure that you've relcoated the virtual network](./relocation-virtual-network.md) and that the firewall *Management Subnet* is present before the Azure Firewall is relocated.   Update the IP Address in the target region of the Network Virtual Appliance (NVA) to which the Azure Firewall should redirect the traffic, in the User Defined Route (UDR).
+    - **Forced Tunneling.**  [Ensure that you've relocated the virtual network](./relocation-virtual-network.md) and that the firewall *Management Subnet* is present before the Azure Firewall is relocated.   Update the IP Address in the target region of the Network Virtual Appliance (NVA) to which the Azure Firewall should redirect the traffic, in the User Defined Route (UDR).
     - **DNS.** Review IP Addresses for your custom custom *DNS Servers* to reflect your target region. If the *DNS Proxy* feature is enabled, be sure to configure your virtual network DNS server settings and set the Azure Firewall’s private IP address as a *Custom DNS server*.
     - **Private IP ranges (SNAT).** - If custom ranges are defined for SNAT, it's recommended that you review and eventually adjust to include the target region address space.
     - **Tags.** - Verify and eventually update any tag that may reflect or refer to the new firewall location.
@@ -185,7 +185,7 @@ To find the location code for your target region, see [Data residency in Azure](
 1. Review and update the configuration for the topics below to reflect the changes required for the target region.
     - **IP Groups.** To include IP addresses from the target region, if different from the source, *IP Groups* should be reviewed. The IP addresses included in the groups must be modified.
     - **Zones.**  Configure the [availability Zones (AZ)](../reliability/availability-zones-overview.md) in the target region.
-    - **Forced Tunneling.**  [Ensure that you've relcoated the virtual network](./relocation-virtual-network.md) and that the firewall *Management Subnet* is present before the Azure Firewall is relocated.   Update the IP Address in the target region of the Network Virtual Appliance (NVA) to which the Azure Firewall should redirect the traffic, in the User Defined Route (UDR).
+    - **Forced Tunneling.**  [Ensure that you've relocated the virtual network](./relocation-virtual-network.md) and that the firewall *Management Subnet* is present before the Azure Firewall is relocated.   Update the IP Address in the target region of the Network Virtual Appliance (NVA) to which the Azure Firewall should redirect the traffic, in the User Defined Route (UDR).
     - **DNS.** Review IP Addresses for your custom custom *DNS Servers* to reflect your target region. If the *DNS Proxy* feature is enabled, be sure to configure your virtual network DNS server settings and set the Azure Firewall’s private IP address as a *Custom DNS server*.
     - **Private IP ranges (SNAT).** - If custom ranges are defined for SNAT, it's recommended that you review and eventually adjust to include the target region address space.
     - **Tags.** - Verify and eventually update any tag that may reflect or refer to the new firewall location.
diff --git a/articles/vpn-gateway/azure-vpn-client-prerequisites-check.md b/articles/vpn-gateway/azure-vpn-client-prerequisites-check.md
@@ -28,7 +28,7 @@ The **Run Prerequisites Test** feature is available in the Azure VPN Client for
 1. Select **Run Prerequisites Test** to run the check.
 1. After the prerequisites check has completed, the **Status** shows **Complete**. Review the results. If any test items don't pass, the status indicates that and prescriptive measures are provided to help you mitigate the issue.
 
-    :::image type="content" source="./media/azure-vpn-client-prerequisites-check/error.png" alt-text="Screenshot of prerequistes test status results." lightbox="./media/azure-vpn-client-prerequisites-check/error.png":::
+    :::image type="content" source="./media/azure-vpn-client-prerequisites-check/error.png" alt-text="Screenshot of prerequisites test status results." lightbox="./media/azure-vpn-client-prerequisites-check/error.png":::
 
 ## Disable automatic prerequisites checks
 
diff --git a/articles/vpn-gateway/bgp-how-to-cli.md b/articles/vpn-gateway/bgp-how-to-cli.md
@@ -274,7 +274,7 @@ az network vnet-gateway show -n VNet1GW -g TestRG1
 Example value for the gateway resource:
 
 ```
-"/subscriptions/<subscripion ID value>/resourceGroups/TestRG2/providers/Microsoft.Network/virtualNetworkGateways/VNet2GW"
+"/subscriptions/<subscription ID value>/resourceGroups/TestRG2/providers/Microsoft.Network/virtualNetworkGateways/VNet2GW"
 ```
 
 #### 2. Get the resource ID of VNet2GW
diff --git a/articles/vpn-gateway/point-to-site-certificate-client-linux-azure-vpn-client.md b/articles/vpn-gateway/point-to-site-certificate-client-linux-azure-vpn-client.md
@@ -69,7 +69,7 @@ openssl x509 -req -days 365 -in "${USERNAME}Req.pem" -CA caCert.pem -CAkey caKey
 
 When you generate and download a VPN client profile configuration package, all the necessary configuration settings for VPN clients are contained in a VPN client profile configuration zip file. The VPN client profile configuration files are specific to the P2S VPN gateway configuration for the virtual network. If there are any changes to the P2S VPN configuration after you generate the files, such as changes to the VPN protocol type or authentication type, you need to generate new VPN client profile configuration files and apply the new configuration to all of the VPN clients that you want to connect.
 
-Locate and unzip the VPN client profile configuration package you generated and downloaded (listed in the [Prequisites](#prerequisites)). Open the **AzureVPN** folder. In this folder, you'll see either the **azurevpnconfig_cert.xml** file or the **azurevpnconfig.xml** file, depending on whether your P2S configuration includes multiple authentication types. The .xml file contains the settings you use to configure the VPN client profile.
+Locate and unzip the VPN client profile configuration package you generated and downloaded (listed in the [Prerequisites](#prerequisites)). Open the **AzureVPN** folder. In this folder, you'll see either the **azurevpnconfig_cert.xml** file or the **azurevpnconfig.xml** file, depending on whether your P2S configuration includes multiple authentication types. The .xml file contains the settings you use to configure the VPN client profile.
 
 If you don't see either file, or you don't have an **AzureVPN** folder, verify that your VPN gateway is configured to use the OpenVPN tunnel type and that certificate authentication is selected.
 
diff --git a/articles/web-application-firewall/ag/rate-limiting-configure.md b/articles/web-application-firewall/ag/rate-limiting-configure.md
@@ -80,7 +80,7 @@ az network application-gateway waf-policy custom-rule match-condition add --matc
 ```azurepowershell
 $variable = New-AzApplicationGatewayFirewallMatchVariable -VariableName RemoteAddr 
 $condition = New-AzApplicationGatewayFirewallCondition -MatchVariable $variable -Operator GeoMatch -MatchValue "US" -NegationCondition $True
-$groupByVariable = New-AzApplicationGatewayFirewallCustomRuleGroupByVariablde -VariableName GeoLocation 
+$groupByVariable = New-AzApplicationGatewayFirewallCustomRuleGroupByVariable -VariableName GeoLocation 
 $groupByUserSession = New-AzApplicationGatewayFirewallCustomRuleGroupByUserSession -GroupByVariable $groupByVariable 
 $ratelimitrule = New-AzApplicationGatewayFirewallCustomRule -Name GeoRateLimitRule -Priority 95 -RateLimitDuration OneMin -RateLimitThreshold 500 -RuleType RateLimitRule -MatchCondition $condition -GroupByUserSession $groupByUserSession -Action Block -State Enabled  
 ```

Original file line number	Diff line number	Diff line change
`@@ -164,7 +164,7 @@ Save the following example as azuredeploy.json:`
`164`	`164`	`"type": "string",`
`165`	`165`	`"defaultValue": "172.30.0.0/16",`
`166`	`166`	`"metadata": {`
`167`		`- "decription": "Cidr of service"`
	`167`	`+ "description": "Cidr of service"`
`168`	`168`	`}`
`169`	`169`	`},`
`170`	`170`	`"clusterName" : {`