Merge pull request #310434 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/api-management/virtual-network-reference.md

@@ -63,7 +63,7 @@ NSG rules allowing outbound connectivity to Storage, SQL, and Azure Event Hubs s
 
 ## TLS functionality  
 
-To enable TLS/SSL certificate chain building and validation, the API Management service needs outbound network connectivity on ports `80` and `443` to `ocsp.msocsp.com`, `oneocsp.msocsp.com`, `mscrl.microsoft.com`, `crl.microsoft.com`, `cacerts.digicert.com`, `crl3.digicert.com` and `csp.digicert.com`. 
+To enable TLS/SSL certificate chain building and validation, the API Management service needs outbound network connectivity on ports `80` and `443` to `mscrl.microsoft.com`, `crl.microsoft.com`, `oneocsp.microsoft.com`, `cacerts.digicert.com`, `crl3.digicert.com` and `csp.digicert.com`. 
 
 
 ## DNS access

articles/communication-services/how-tos/call-automation/audio-streaming-quickstart.md

@@ -16,8 +16,6 @@ zone_pivot_groups: acs-js-csharp-java-python
 
 Get started with using audio streams through Azure Communication Services Audio Streaming API. This quickstart assumes you're already familiar with Call Automation APIs to build an automated call routing solution. 
 
-Functionality described in this quickstart is currently in public preview.
-
 ::: zone pivot="programming-language-csharp"
 [!INCLUDE [Audio Streaming with .NET](./includes//audio-streaming-quickstart-csharp.md)]
 ::: zone-end

articles/container-apps/custom-virtual-networks.md

@@ -129,6 +129,9 @@ You can use NAT Gateway to simplify outbound connectivity for your outbound inte
 
 When you configure a NAT Gateway on your subnet, the NAT Gateway provides a static public IP address for your environment. All outbound traffic from your container app is routed through the NAT Gateway's static public IP address.
 
+> [!NOTE]
+> Standard V2 SKU NAT Gateway is currently not supported for integration.
+
 ## Managed resources
 
 When you deploy an internal or an external environment into your own network, a new resource group is created in the Azure subscription where your environment is hosted. This resource group contains infrastructure components managed by the Azure Container Apps platform. Don't modify the services in this group or the resource group itself.

articles/logic-apps/expression-functions-reference.md

@@ -4971,7 +4971,17 @@ And returns this result XML:
 
 The `xml()` function expects either an object or a string containing valid XML. The function doesn't accept a raw array as input.
 
-If your data is a JSON string, you can use the `json()` function to convert the string to a JSON object before you pass the result to the `xml()` function, for example:
+If you have a JSON array, like the following example, you have four options.
+
+```json
+[
+  { "ID": 1, "Name": "James" },
+  { "ID": 2, "Name": "John" },
+  { "ID": 3, "Name": "Sam" }
+]
+```
+
+Option 1: Convert the JSON string to a JSON object before you pass the result to the `xml()` function, for example:
 
 ```
 xml(
@@ -4983,31 +4993,21 @@ xml(
 )
 ```
 
-If you have a JSON array, like the following example, you have three options.
-
-```json
-[
-  { "ID": 1, "Name": "James" },
-  { "ID": 2, "Name": "John" },
-  { "ID": 3, "Name": "Sam" }
-]
-```
-
-Option 1: Store the JSON array in a **Compose** action named **Compose1**. Then use the `outputs()` function to return a JSON object from **Compose1**.
+Option 2: Store the JSON array in a **Compose** action named **Compose1**. Then use the `outputs()` function to return a JSON object from **Compose1**, and store the returned JSON object in another **Compose** action named **Compose2**.
 
 ```
 {
   "root": { "array": @{outputs('Compose1')} }
 }
 ```
 
-Store the returned JSON object in another action named **Compose2**. You can then use the `xml()` and `outputs()` functions to create XML from the JSON object output from **Compose2**, for example: 
+You can then use the `xml()` and `outputs()` functions to create XML from the JSON object output from **Compose2**, for example: 
 
 ```
 xml(outputs('Compose2'))
 ```
 
-Option 2: Store the JSON array in a **Compose** action named **Compose1**. Then use the `outputs()`, `concat()`, `json()`, and `xml()` functions to create XML from the JSON object output, for example: 
+Option 3: Store the JSON array in a **Compose** action named **Compose1**. Then use the `outputs()`, `concat()`, `json()`, and `xml()` functions to create XML from the JSON object output, for example: 
 
 ```
 xml(
@@ -5019,10 +5019,9 @@ xml(
     )
   )
 )
-
 ```
 
-Option 3: Store the JSON array in a **Compose** action named **Compose1**. You can then use the `outputs()`, `json()`, `addProperty()`, and `xml()` functions to create XML from the JSON object output, for example: 
+Option 4: Similar to option 3, but uses `addProperty()` instead of the `concat()` function to create the JSON object before passing it to the `xml()` function, for example: 
 
 ```
 xml(
@@ -5038,7 +5037,7 @@ xml(
 )
 ```
 
-All examples, which include the JSON string data example and options 1 to 3, return the following XML result:
+All the examples from options 1 to 4 return the following XML result:
 
 ```xml
 <root>