Merge pull request #283840 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/ai-studio/how-to/create-azure-ai-hub-template.md

@@ -105,18 +105,18 @@ To run the Bicep template, use the following commands from the `aistudio-basics`
 1. To run the template, use the following command. Replace `myai` with the name to use for your resources. This value is used, along with generated prefixes and suffixes, to create a unique name for the resources created by the template.
 
     > [!TIP]
-    > The `aiResourceName` must be 5 or less characters. It can't be entirely numeric or contain the following characters: `~ ! @ # $ % ^ & * ( ) = + _ [ ] { } \ | ; : . ' " , < > / ?`.
+    > The `aiHubName` must be 5 or less characters. It can't be entirely numeric or contain the following characters: `~ ! @ # $ % ^ & * ( ) = + _ [ ] { } \ | ; : . ' " , < > / ?`.
 
     # [Azure CLI](#tab/cli)
 
     ```azurecli
-    az deployment group create --resource-group exampleRG --template-file main.bicep --parameters aiResourceName=myai 
+    az deployment group create --resource-group exampleRG --template-file main.bicep --parameters aiHubName=myai 
     ```
 
     # [Azure PowerShell](#tab/powershell)
 
     ```azurepowershell
-    New-AzResourceGroupDeployment -ResourceGroupName exampleRG -TemplateFile main.bicep -aiResourceName myai
+    New-AzResourceGroupDeployment -ResourceGroupName exampleRG -TemplateFile main.bicep -aiHubName myai
     ```
 
     ---

articles/cosmos-db/burst-capacity-faq.yml

@@ -25,7 +25,7 @@ sections:
       - question: |
           How does burst capacity work with autoscale?
         answer: |
-          Autoscale and burst capacity are compatible. Autoscale gives you a guaranteed instant 10 times scale range. Burst capacity allows you to take advantage of unused, idle capacity to handle temporary spikes, potentially beyond your autoscale max RU/s. For example, suppose we have an autoscale container with one physical partition that scales between 100 - 1000 RU/s. Without burst capacity, any requests that consume beyond 1000 RU/s would be rate limited. With burst capacity however, the partition can accumulate a maximum of 1000 RU/s of idle capacity each second. Burst capacity allows the partition to burst at a maximum rate of 3000 RU/s for a limited amount of time.
+          Autoscale and burst capacity are compatible. Autoscale gives you a guaranteed instant 10 times scale range. Burst capacity allows you to take advantage of unused, idle capacity to handle temporary spikes, potentially beyond your autoscale max RU/s. For example, suppose we have an autoscale container with one physical partition that scales between 100 - 1000 RU/s. Without burst capacity, any requests that consume beyond 1000 RU/s would be rate limited. With burst capacity however, the partition can accumulate a maximum of 100 RU/s of idle capacity each second. Burst capacity allows the partition to burst at a maximum rate of 3000 RU/s for a limited amount of time.
 
           Accumulation of burst is based on the maximum autoscale RU/s.
 

articles/machine-learning/how-to-secure-workspace-vnet.md

@@ -273,7 +273,7 @@ Azure Container Registry can be configured to use a private endpoint. Use the fo
     az ml workspace update --name myworkspace --resource-group myresourcegroup --image-build-compute mycomputecluster
     ```
 
-    You can switch back to serverless compute by executing the same command and referencing the compute as an empty space: `--image-build-compute ' '`.
+    You can switch back to serverless compute by executing the same command and referencing the compute as an empty space: `--image-build-compute ''`.
 
     # [Python SDK](#tab/python)
 

articles/virtual-desktop/clipboard-transfer-direction-data-types.md

@@ -86,7 +86,7 @@ To configure the clipboard using Intune, follow these steps. This process create
     - **Restrict clipboard transfer from client to server**: Select **Enabled**.
     - **Restrict clipboard transfer from client to server**: Select the type of clipboard data you want to prevent or allow. Your options:
 
-      - Disable clipboard transfers from server to client
+      - Disable clipboard transfers from client to server
       - Allow plain text
       - Allow plain text and images
       - Allow plain text, images, and Rich Text Format

articles/virtual-desktop/private-link-overview.md

@@ -79,8 +79,6 @@ Private Link with Azure Virtual Desktop has the following limitations:
 
 - After you've changed a private endpoint to a host pool, you must restart the *Remote Desktop Agent Loader* (*RDAgentBootLoader*) service on each session host in the host pool. You also need to restart this service whenever you change a host pool's network configuration. Instead of restarting the service, you can restart each session host.
 
-- Using both Private Link and 
-
 - Using both Private Link and [RDP Shortpath for managed networks](rdp-shortpath.md?tabs=managed-networks) isn't supported, but they can work together. You can use Private Link and RDP Shortpath for managed networks at your own risk. All other RDP Shortpath options using STUN or TURN aren't supported with Private Link.
 
 - Early in the preview of Private Link with Azure Virtual Desktop, the private endpoint for the initial feed discovery (for the *global* sub-resource) shared the private DNS zone name of `privatelink.wvd.microsoft.com` with other private endpoints for workspaces and host pools. In this configuration, users are unable to establish private endpoints exclusively for host pools and workspaces. Starting September 1, 2023, sharing the private DNS zone in this configuration will no longer be supported. You need to create a new private endpoint for the *global* sub-resource to use the private DNS zone name of `privatelink-global.wvd.microsoft.com`. For the steps to do this, see [Initial feed discovery](private-link-setup.md#initial-feed-discovery).

articles/web-application-firewall/afds/waf-front-door-custom-rules.md

@@ -199,6 +199,33 @@ Here's an example JSON description of the custom rule:
   "action": "Block"
 }
 ```
+
+### Match based on request URI
+
+Suppose you need to allow requests where the URI contains 'login'.
+
+Here's an example JSON description of the custom rule:
+
+```json
+{
+  "name": "URIContainsLogin",
+  "priority": 5,
+  "ruleType": "MatchRule",
+  "matchConditions": [
+    {
+      "matchVariable": "RequestUri",
+      "selector": null,
+      "operator": "Contains",
+      "negateCondition": false,
+      "matchValue": [
+        "login"
+      ]
+    }
+  ],
+  "action": "Allow"
+}
+```
+
 ## Copying and duplicating custom rules
 
 Custom rules can be duplicated within a given policy. When duplicating a rule, you need to specify a unique name for the rule and a unique priority value. Additionally, custom rules can be copied from one Azure Front Door WAF policy to another as long as the policies are both in the same subscription. When copying a rule from one policy to another, you need to select the Azure Front Door WAF policy you wish to copy the rule into. Once you select the WAF policy you need to give the rule a unique name, and assign a priority rank.