Merge pull request #282076 from MicrosoftDocs/main

7/29/2024 AM Publish

Author: Taojunshen

articles/ai-services/speech-service/embedded-speech.md

@@ -288,8 +288,8 @@ For embedded voices, it's essential to note that certain SSML tags might not be
 |-----------------|-----------|-------------------------------------------------------|--------------------------|
 | audio           | src       |                                                       | No                       |
 | bookmark        |           |                                                       | Yes                      |
-| break           | strength  |                                                       | No                       |
-|                 | time      |                                                       | No                       |
+| break           | strength  |                                                       | Yes                       |
+|                 | time      |                                                       | Yes                       |
 | silence         | type      | Leading, Tailing, Comma-exact, etc.                   | No                       |
 |                 | value     |                                                       | No                       |
 | emphasis        | level     |                                                       | No                       |

articles/ai-studio/how-to/configure-managed-network.md

@@ -48,7 +48,7 @@ There are three different configuration modes for outbound traffic from the mana
     > While you can create a private endpoint for Azure AI Search, the connected services must allow public networking. For more information, see [Connectivity to other services](#connectivity-to-other-services).
 
 * You must add rules for each outbound connection you need to allow.
-* Adding FQDN outbound rules __increase your costs__ as this rule type uses Azure Firewall.
+* Adding FQDN outbound rules __increase your costs__ as this rule type uses Azure Firewall. If you use outbound FQDN rules, charges for Azure Firewall are included in your billing. For more information, see [Pricing](#pricing).
 * The default rules for _allow only approved outbound_ are designed to minimize the risk of data exfiltration. Any outbound rules you add might increase your risk.
 
 The managed virtual network is preconfigured with [required default rules](#list-of-required-rules). It's also configured for private endpoint connections to your hub, the hub's default storage, container registry, and key vault if they're configured as private or the hub isolation mode is set to allow only approved outbound. After choosing the isolation mode, you only need to consider other outbound requirements you might need to add.
@@ -380,9 +380,6 @@ To configure a managed virtual network that allows internet outbound communicati
 
         If the destination type is __FQDN__, provide the following information:
 
-        > [!WARNING]
-        > FQDN outbound rules are implemented using Azure Firewall. If you use outbound FQDN rules, charges for Azure Firewall are included in your billing. For more information, see [Pricing](#pricing).
-
         * __FQDN destination__: The fully qualified domain name to add to the approved outbound rules.
 
         Select __Save__ to save the rule. You can continue using __Add user-defined outbound rules__ to add rules.
@@ -415,9 +412,6 @@ You can also define _outbound rules_ to define approved outbound communication.
 > * Adding an outbound for a service tag or FQDN is only valid when the managed VNet is configured to `allow_only_approved_outbound`.
 > * If you add outbound rules, Microsoft can't guarantee data exfiltration.
 
-> [!WARNING]
-> FQDN outbound rules are implemented using Azure Firewall. If you use outbound FQDN rules, charges for Azure Firewall are added to your billing. For more information, see [Pricing](#pricing).
-
 ```yaml
 managed_network:
   isolation_mode: allow_only_approved_outbound
@@ -476,9 +470,6 @@ You can configure a managed virtual network using either the `az ml workspace cr
 
     The following YAML file defines a managed virtual network for the hub. It also demonstrates how to add an approved outbound to the managed virtual network. In this example, an outbound rule is added for both a service tag:
 
-    > [!WARNING]
-    > FQDN outbound rules are implemented using Azure Firewall. If you use outbound FQDN rules, charges for Azure Firewall are added to your billing. For more information, see [Pricing](#pricing).
-
     ```yaml
     name: myhub_dep
     managed_network:
@@ -522,9 +513,6 @@ To configure a managed virtual network that allows only approved outbound commun
     > * Adding an outbound for a service tag or FQDN is only valid when the managed VNet is configured to `IsolationMode.ALLOW_ONLY_APPROVED_OUTBOUND`.
     > * If you add outbound rules, Microsoft can't guarantee data exfiltration.
 
-    > [!WARNING]
-    > FQDN outbound rules are implemented using Azure Firewall. If you use outbound FQDN rules, charges for Azure Firewall are added to your billing. For more information, see [Pricing](#pricing).
-
     ```python
     # Basic managed VNet configuration
     network = ManagedNetwork(isolation_mode=IsolationMode.ALLOW_ONLY_APPROVED_OUTBOUND)
@@ -587,9 +575,6 @@ To configure a managed virtual network that allows only approved outbound commun
 
     > [!TIP]
     > Adding an outbound for a service tag or FQDN is only valid when the managed VNet is configured to `IsolationMode.ALLOW_ONLY_APPROVED_OUTBOUND`.
-
-    > [!WARNING]
-    > FQDN outbound rules are implemented using Azure Firewall. If you use outbound FQDN rules, charges for Azure Firewall are added to your billing. For more information, see [Pricing](#pricing).
 
     ```python
     # Get the existing hub
@@ -728,9 +713,6 @@ __Inbound__ service tag rules:
 
 To allow installation of __Python packages for training and deployment__, add outbound _FQDN_ rules to allow traffic to the following host names:
 
-> [!WARNING]
-> FQDN outbound rules are implemented using Azure Firewall. If you use outbound FQDN rules, charges for Azure Firewall are included in your billing. For more information, see [Pricing](#pricing).
-
 > [!NOTE]
 > This is not a complete list of the hosts required for all Python resources on the internet, only the most commonly used. For example, if you need access to a GitHub repository or other host, you must identify and add the required hosts for that scenario.
 
@@ -748,9 +730,6 @@ Visual Studio Code relies on specific hosts and ports to establish a remote conn
 #### Hosts
 If you plan to use __Visual Studio Code__ with the hub, add outbound _FQDN_ rules to allow traffic to the following hosts:
 
-> [!WARNING]
-> FQDN outbound rules are implemented using Azure Firewall. If you use outbound FQDN rules, charges for Azure Firewall are included in your billing. For more information, see [Pricing](#pricing).
-
 * `*.vscode.dev`
 * `vscode.blob.core.windows.net`
 * `*.gallerycdn.vsassets.io`
@@ -773,9 +752,6 @@ You must allow network traffic to ports 8704 to 8710. The VS Code server dynamic
 
 If you plan to use __HuggingFace models__ with the hub, add outbound _FQDN_ rules to allow traffic to the following hosts:
 
-> [!WARNING]
-> FQDN outbound rules are implemented using Azure Firewall. If you use outbound FQDN rules, charges for Azure Firewall are included in your billing. For more information, see [Pricing](#pricing).
-
 * docker.io
 * *.docker.io
 * *.docker.com

articles/api-center/import-api-management-apis.md

@@ -255,15 +255,15 @@ In the following command, substitute the names of your API center, your API cent
 
 ```azurecli
 #! /bin/bash
-import-from-apim --service-name <api-center-name> --resource-group <resource-group-name> \
+az apic import-from-apim --service-name <api-center-name> --resource-group <resource-group-name> \
     --apim-name <api-management-name> --apim-resource-group <api-management-resource-group-name> \
     --apim-apis 'petstore-api'        
 ```
 
 
 ```azurecli
 # PowerShell syntax
-import-from-apim --service-name <api-center-name> --resource-group <resource-group-name> `
+az apic import-from-apim --service-name <api-center-name> --resource-group <resource-group-name> `
     --apim-name <api-management-name> --apim-resource-group <api-management-resource-group-name> `
     --apim-apis 'petstore-api'    
 ```

articles/azure-arc/servers/arc-gateway.md

@@ -225,7 +225,7 @@ To configure an existing machine to use Arc gateway, follow these steps:
 1. Associate your existing machine with your Arc gateway resource:
 
     ```azurecli
-    az connectedmachine setting update --resource-group [res-group] --subscription [subscription name] --base-provider Microsoft.HyrbridCompute --base-resource-type machines --base-resource-name [Arc-server's resource name]  --settings-resource-name default --gateway-resource-id [Full Arm resourceid]
+    az connectedmachine setting update --resource-group [res-group] --subscription [subscription name] --base-provider Microsoft.HybridCompute --base-resource-type machines --base-resource-name [Arc-server's resource name]  --settings-resource-name default --gateway-resource-id [Full Arm resourceid]
     ```
     
 1. Update the machine to use the Arc gateway resource.

articles/azure-functions/functions-identity-access-azure-sql-with-managed-identity.md

@@ -76,7 +76,7 @@ To enable system-assigned managed identity in the Azure portal:
 1. Select Identity.
 1. Within the System assigned tab, switch Status to On. Click Save.
 
-![Turn on system assigned identity for Function app](./media/functions-identity-access-sql-with-managed-identity/function-system-identity.png)
+:::image type="content" source="./media/functions-identity-access-sql-with-managed-identity/function-system-identity.png" alt-text="Screenshot of function app, showing the Status set to On.":::
 
 
 For information on enabling system-assigned managed identity through Azure CLI or PowerShell, check out more information on [using managed identities with Azure Functions](../app-service/overview-managed-identity.md?tabs=dotnet&toc=%2fazure%2fazure-functions%2ftoc.json#add-a-system-assigned-identity).