Merge branch 'main' into repo_sync_working_branch

Author: TimShererWithAquent

.github/policies/disallow-edits.yml

@@ -10,129 +10,80 @@ configuration:
           - payloadType: Pull_Request
           - isAction:
               action: Opened
-          - or:
-              - includesModifiedFiles:
-                  files:
-                    - articles/aks/*
-              - includesModifiedFiles:
-                  files:
-                    - articles/defender-for-cloud/*
-              - includesModifiedFiles:
-                  files: 
-                    - articles/attestation/*
-              - includesModifiedFiles:
-                  files: 
-                    - articles/confidential-ledger/*
-              - includesModifiedFiles:
-                  files: 
-                    - articles/dedicated-hsm/*
-              - includesModifiedFiles:
-                  files:
-                    - articles/key-vault/*
-              - includesModifiedFiles:
-                  files: 
-                    - articles/payment-hsm/*
-              - includesModifiedFiles:
-                  files: 
-                    - articles/postgresql/*
-              - includesModifiedFiles:
-                  files: 
-                    - articles/cosmos-db/*
-              - includesModifiedFiles:
-                  files: 
-                    - articles/dms/*
-              - includesModifiedFiles:
-                  files: 
-                    - articles/mariadb/*
-              - includesModifiedFiles:
-                  files: 
-                    - articles/mysql/*
-              - includesModifiedFiles:
-                  files:   
-                    - articles/managed-instance-apache-cassandra/*
-              - includesModifiedFiles:
-                  files:   
-                    - articles/virtual-machines/*
-              - includesModifiedFiles:
-                  files:   
-                    - articles/virtual-machines-scale-sets/*
-              - includesModifiedFiles:
-                  files:   
-                    - articles/container-instances/*
-              - includesModifiedFiles:
-                  files:   
-                    - articles/service-fabric/*
-              - includesModifiedFiles:
-                  files:   
-                    - articles/machine-learning/*
-              - includesModifiedFiles:
-                  files:   
-                    - articles/ai-studio/*
-              - includesModifiedFiles:
-                  files:   
-                    - articles/ai-services/*
-              - includesModifiedFiles:
-                  files:   
-                    - articles/genomics/*
-              - includesModifiedFiles:
-                  files:   
-                    - articles/open-datasets/*
-              - includesModifiedFiles:
-                  files:   
-                    - articles/search/*
-              - includesModifiedFiles:
-                  files:   
-                    - articles/azure-monitor/*
-              - includesModifiedFiles:
-                  files:  
-                    - articles/advisor/*
-              - includesModifiedFiles:
-                  files:   
-                    - articles/chaos-studio/*
-              - includesModifiedFiles:
-                  files:  
-                    - articles/service-health/*
-              - includesModifiedFiles:
-                  files:  
-                    - articles/azure-arc/*
-              - includesModifiedFiles:
-                  files:   
-                    - articles/azure-linux/*
-              - includesModifiedFiles:
-                  files:   
-                    - articles/azure-portal/*
-              - includesModifiedFiles:
-                  files:   
-                    - articles/copilot/*
-              - includesModifiedFiles:
-                  files:   
-                    - articles/lighthouse/*
-              - includesModifiedFiles:
-                  files:  
-                    - articles/quotas/*
-              - includesModifiedFiles:
-                  files:   
-                    - articles/container-registry/*
-              - includesModifiedFiles:
-                  files:  
-                    - articles/kubernetes-fleet/*
+          - or:              
+              - filesMatchPattern:
+                  pattern: articles/aks/*
+              - filesMatchPattern:
+                  pattern: articles/defender-for-cloud/*
+              - filesMatchPattern:
+                  pattern: articles/attestation/*
+              - filesMatchPattern:
+                  pattern: articles/confidential-ledger/*
+              - filesMatchPattern:
+                  pattern: articles/dedicated-hsm/*
+              - filesMatchPattern:
+                  pattern: articles/key-vault/*
+              - filesMatchPattern:
+                  pattern: articles/payment-hsm/*
+              - filesMatchPattern:
+                  pattern: articles/postgresql/*
+              - filesMatchPattern:
+                  pattern: articles/cosmos-db/*
+              - filesMatchPattern:
+                  pattern: articles/dms/*
+              - filesMatchPattern:
+                  pattern: articles/mariadb/*
+              - filesMatchPattern:
+                  pattern: articles/mysql/*
+              - filesMatchPattern:
+                  pattern: articles/managed-instance-apache-cassandra/*
+              - filesMatchPattern:
+                  pattern: articles/virtual-machines/*
+              - filesMatchPattern:
+                  pattern: articles/virtual-machines-scale-sets/*
+              - filesMatchPattern:
+                  pattern: articles/container-instances/*
+              - filesMatchPattern:
+                  pattern: articles/service-fabric/*
+              - filesMatchPattern:
+                  pattern: articles/machine-learning/*
+              - filesMatchPattern:
+                  pattern: articles/ai-studio/*
+              - filesMatchPattern:
+                  pattern: articles/ai-services/*
+              - filesMatchPattern:
+                  pattern: articles/genomics/*
+              - filesMatchPattern:
+                  pattern: articles/open-datasets/*
+              - filesMatchPattern:
+                  pattern: articles/search/*
+              - filesMatchPattern:
+                  pattern: articles/azure-monitor/*
+              - filesMatchPattern:
+                  pattern: articles/advisor/*
+              - filesMatchPattern:
+                  pattern: articles/chaos-studio/*
+              - filesMatchPattern:
+                  pattern: articles/service-health/*
+              - filesMatchPattern:
+                  pattern: articles/azure-arc/*
+              - filesMatchPattern:
+                  pattern: articles/azure-linux/*
+              - filesMatchPattern:
+                  pattern: articles/azure-portal/*
+              - filesMatchPattern:
+                  pattern: articles/copilot/*
+              - filesMatchPattern:
+                  pattern: articles/lighthouse/*
+              - filesMatchPattern:
+                  pattern: articles/quotas/*
+              - filesMatchPattern:
+                  pattern: articles/container-registry/*
+              - filesMatchPattern:
+                  pattern: articles/kubernetes-fleet/*
         then:
           - addReply:
               reply: >-
-                @${issueAuthor} - You tried to add content to a folder path that has been removed from this repository. Your pull request will be automatically closed. Submit your changes to the updated repository, which can be identified by clicking the Edit this Document link at the top of any published article for that product or service. 
-          - if:
-              - or:
-                  - activitySenderHasPermission:
-                      permission: None
-                  - activitySenderHasPermission:
-                      permission: Read
-                  - activitySenderHasPermission:
-                      permission: Write
-                  - activitySenderHasPermission:
-                      permission: Triage
-                  - activitySenderHasPermission:
-                      permission: Maintain
-                  - activitySenderHasPermission:
-                      permission: Admin
-            then:
-              - closePullRequest
+                @${issueAuthor} - You tried to add content to a folder path that has been removed from this repository. Your pull request will be automatically closed. Submit your changes to the updated repository, which can be identified by clicking the Edit this Document link at the top of any published article for that product or service.
+          - closePullRequest
+          

.openpublishing.publish.config.json

@@ -254,12 +254,6 @@
             "branch": "main",
             "branch_mapping": {}
         },
-        {
-            "path_to_root": "azure-reference-other-repo",
-            "url": "https://github.com/MicrosoftDocs/azure-reference-other-pr",
-            "branch": "main",
-            "branch_mapping": {}
-        },
         {
             "path_to_root": "azure-sdk-for-go-samples",
             "url": "https://github.com/Azure-Samples/azure-sdk-for-go-samples",

articles/api-management/quota-by-key-policy.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: article
-ms.date: 07/23/2024
+ms.date: 09/16/2024
 ms.author: danlep
 ---
 # Set usage quota by key
@@ -29,6 +29,7 @@ To understand the difference between rate limits and quotas, [see Rate limits an
               bandwidth="kilobytes"
               renewal-period="seconds"
               increment-condition="condition"
+              increment-count="number"
               counter-key="key value"
               first-period-start="date-time" />
 ```
@@ -41,6 +42,7 @@ To understand the difference between rate limits and quotas, [see Rate limits an
 | calls               | The maximum total number of calls allowed during the time interval specified in the `renewal-period`. Policy expressions aren't allowed.    | Either `calls`, `bandwidth`, or both together must be specified. | N/A     |
 | counter-key         | The key to use for the `quota policy`. For each key value, a single counter is used for all scopes at which the policy is configured. Policy expressions are allowed.             | Yes                                                              | N/A     |
 | increment-condition | The Boolean expression specifying if the request should be counted towards the quota (`true`). Policy expressions are allowed.             | No                                                               | N/A     |
+| increment-count | The number by which the counter is increased per request. Policy expressions are allowed. | No | 1 |
 | renewal-period      | The length in seconds of the fixed window after which the quota resets. The start of each period is calculated relative to `first-period-start`. Minimum period: 300 seconds. When `renewal-period` is set to 0, the period is set to infinite. Policy expressions aren't allowed.                                                  | Yes                                                              | N/A     |
 | first-period-start      | The starting date and time for quota renewal periods, in the following format: `yyyy-MM-ddTHH:mm:ssZ` as specified by the ISO 8601 standard. Policy expressions aren't allowed.   | No                                                              | `0001-01-01T00:00:00Z`     |
 

articles/api-management/xml-to-json-policy.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: article
-ms.date: 07/23/2024
+ms.date: 09/06/2024
 ms.author: danlep
 ---
 
@@ -21,7 +21,7 @@ The `xml-to-json` policy converts a request or response body from XML to JSON. T
 ## Policy statement
 
 ```xml
-<xml-to-json kind="javascript-friendly | direct" apply="always | content-type-xml" consider-accept-header="true | false"/>
+<xml-to-json kind="javascript-friendly | direct" apply="always | content-type-xml" consider-accept-header="true | false" always-array-children="true | false"/>
 ```
 
 
@@ -32,6 +32,7 @@ The `xml-to-json` policy converts a request or response body from XML to JSON. T
 |kind|The attribute must be set to one of the following values.<br /><br /> -   `javascript-friendly` - the converted JSON has a form friendly to JavaScript developers.<br />-   `direct` - the converted JSON reflects the original XML document's structure.<br/><br/>Policy expressions are allowed.|Yes|N/A|
 |apply|The attribute must be set to one of the following values.<br /><br /> -   `always` - convert always.<br />-   `content-type-xml` - convert only if response Content-Type header indicates presence of XML.<br/><br/>Policy expressions are allowed.|Yes|N/A|
 |consider-accept-header|The attribute must be set to one of the following values.<br /><br /> -   `true` - apply conversion if JSON is requested in request Accept header.<br />-   `false` -always apply conversion.<br/><br/>Policy expressions are allowed.|No|`true`|
+|always-array-children|The attribute must be set to one of the following values.<br /><br /> -   `true` - Always convert child elements into a JSON array.<br />-   `false` - Only convert multiple child elements into a JSON array. Convert a single child element into a JSON object.<br/><br/>Policy expressions are allowed.|No|`false`|
 
 ## Usage
 

articles/app-service/overview-tls.md

@@ -45,7 +45,7 @@ You can use Azure Policy to help audit your resources when it comes to minimum T
 
 ### Minimum TLS Version and SCM Minimum TLS Version 
 
-App Service also allows you to set minimum TLS version for incoming requests to your web app and to SCM site. By default, the minimum TLS version for incoming requests to your web app and to SCM would be set to 1.2 on both portal and API. 
+App Service also allows you to set minimum TLS version for incoming requests to your web app and to SCM site. By default, the minimum TLS version for incoming requests to your web app and to SCM is set to 1.2 on both portal and API. 
 
 ### TLS 1.3
 A [Minimum TLS Cipher Suite](#minimum-tls-cipher-suite-preview) setting is available with TLS 1.3. This includes two cipher suites at the top of the cipher suite order:
@@ -54,12 +54,12 @@ A [Minimum TLS Cipher Suite](#minimum-tls-cipher-suite-preview) setting is avail
 
 ### TLS 1.0 and 1.1 
 
-TLS 1.0 and 1.1 are considered legacy protocols and are no longer considered secure. It's generally recommended for customers to use TLS 1.2 or above as the minimum TLS version. When creating a web app, the default minimum TLS version would be TLS 1.2.
+TLS 1.0 and 1.1 are considered legacy protocols and are no longer considered secure. It's generally recommended for customers to use TLS 1.2 or above as the minimum TLS version. When creating a web app, the default minimum TLS version is TLS 1.2.
 
 To ensure backward compatibility for TLS 1.0 and TLS 1.1, App Service will continue to support TLS 1.0 and 1.1 for incoming requests to your web app. However, since the default minimum TLS version is set to TLS 1.2, you need to update the minimum TLS version configurations on your web app to either TLS 1.0 or 1.1 so the requests won't be rejected. 
 
 > [!IMPORTANT]
-> Incoming requests to web apps and incoming requests to Azure are treated differently. App Service will continue to support TLS 1.0 and 1.1 for incoming requests to the web apps. For incoming requests directly to Azure, for example through ARM or API, it's not recommended to use TLS 1.0 or 1.1.
+> Incoming requests to web apps and incoming requests to Azure are treated differently. App Service will continue to support TLS 1.0 and 1.1 for incoming requests to the web apps. For incoming requests directly to the Azure control plane, for example through ARM or API calls, it is not recommended to use TLS 1.0 or 1.1.
 >
 
 ## Minimum TLS cipher suite (preview)

articles/batch/monitor-batch-reference.md

@@ -19,7 +19,8 @@ See [Monitor Azure Batch](monitor-batch.md) for details on the data you can coll
 ### Supported metrics for Microsoft.Batch/batchaccounts
 The following table lists the metrics available for the Microsoft.Batch/batchaccounts resource type.
 [!INCLUDE [horz-monitor-ref-metrics-tableheader](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-tableheader.md)]
-[!INCLUDE [Microsoft.Batch/batchaccounts](~/azure-reference-other-repo/azure-monitor-ref/supported-metrics/includes/microsoft-batch-batchaccounts-metrics-include.md)]
+[!INCLUDE [Microsoft.Batch/batchaccounts](~/reusable-content/ce-skilling/azure/includes/azure-monitor/reference/metrics/microsoft-batch-batchaccounts-metrics-include.md)]  
+
 
 [!INCLUDE [horz-monitor-ref-metrics-dimensions-intro](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-dimensions-intro.md)]
 
@@ -31,7 +32,7 @@ The following table lists the metrics available for the Microsoft.Batch/batchacc
 [!INCLUDE [horz-monitor-ref-resource-logs](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-resource-logs.md)]
 
 ### Supported resource logs for Microsoft.Batch/batchaccounts
-[!INCLUDE [Microsoft.Batch/batchaccounts](~/azure-reference-other-repo/azure-monitor-ref/supported-logs/includes/microsoft-batch-batchaccounts-logs-include.md)]
+[!INCLUDE [Microsoft.Batch/batchaccounts](~/reusable-content/ce-skilling/azure/includes/azure-monitor/reference/logs/microsoft-batch-batchaccounts-logs-include.md)]
 
 ### Service log events
 

articles/container-apps/plans.md

@@ -31,15 +31,10 @@ You can select from general purpose or specialized compute
 
 Use the Dedicated plan when you need any of the following in a single environment:
 
-- **Secure outbound traffic**: You can assign single outbound network path to systems protected by firewalls or other network appliances.
-
-- **Environment isolation**: Dedicated workload profiles provide access to dedicated hardware with a single tenant guarantee.
+- **Compute isolation**: Dedicated workload profiles provide access to dedicated hardware with a single tenant guarantee.
 
 - **Customized compute**: Select from many types and sizes of workload profiles based on your apps requirements. You can deploy many apps to each workload profile. Each workload profile can scale independently as more apps are added or removed or as apps scale their replicas up or down.
 
-
-- **Cost control**: Traditional serverless compute options optimize for scale in response to events and may not provide cost control options. Dedicated workload profiles let you set minimum and maximum scaling to help you better control costs.
-
     The Dedicated plan can be more cost effective when you're running higher scale deployments with steady throughput.
 
 > [!NOTE]

articles/cost-management-billing/understand/pay-bill.md

@@ -7,7 +7,7 @@ ms.reviewer: lishepar
 ms.service: cost-management-billing
 ms.subservice: billing
 ms.topic: how-to
-ms.date: 10/04/2024
+ms.date: 10/08/2024
 ms.author: banders
 ---
 
@@ -116,9 +116,12 @@ Although you can generally use debit cards to pay your Azure bill, consider thes
 
 If the default payment method of your billing profile is wire transfer, follow the payment instructions on your invoice PDF file.
 
+> [!NOTE]
+> When you pay your bill by wire transfer, the payment might take up to 10 business days to get processed.
+
 Alternatively, if your invoice is under the threshold amount for your currency, you can make a one-time payment in the Azure portal with a credit or debit card by using **Pay now**. If your invoice amount exceeds the threshold, you can't pay your invoice with a credit or debit card. You'll find the threshold amount for your currency in the Azure portal after you select **Pay now**.
 
-> [!NOTE]
+>[!NOTE]
 > When multiple invoices are remitted in a single wire transfer, you must specify the invoice numbers for all of the invoices.
 
 ### Bank details used to send wire transfer payments