Merge pull request #268928 from MicrosoftDocs/main

3/13/2024 AM Publish

Author: Taojunshen

articles/ai-services/speech-service/includes/common/environment-variables.md

@@ -30,6 +30,10 @@ After you add the environment variables, you might need to restart any programs
 
 #### [Linux](#tab/linux)
 
+##### Bash
+
+Edit your *.bashrc* file, and add the environment variables:
+
 ```bash
 export SPEECH_KEY=your-key
 export SPEECH_REGION=your-region

articles/ai-services/speech-service/includes/how-to/recognize-speech/csharp.md

@@ -45,7 +45,7 @@ You can initialize `SpeechConfig` in a few other ways:
 
 ## Recognize speech from a microphone
 
-To recognize speech by using your device microphone, create an [`AudioConfig`](/dotnet/api/microsoft.cognitiveservices.speech.audio.audioconfig) instance by using the `FromDefaultMicrophoneInput()` method. Then initialize the[`SpeechRecognizer`](/dotnet/api/microsoft.cognitiveservices.speech.speechrecognizer) object by passing `audioConfig` and `speechConfig`.
+To recognize speech by using your device microphone, create an [`AudioConfig`](/dotnet/api/microsoft.cognitiveservices.speech.audio.audioconfig) instance by using the `FromDefaultMicrophoneInput()` method. Then initialize the [`SpeechRecognizer`](/dotnet/api/microsoft.cognitiveservices.speech.speechrecognizer) object by passing `speechConfig` and `audioConfig`.
 
 ```csharp
 using System;

articles/ai-services/speech-service/includes/release-notes/release-notes-stt.md

@@ -2,10 +2,18 @@
 author: eric-urban
 ms.service: azure-ai-speech
 ms.topic: include
-ms.date: 09/29/2023
+ms.date: 3/13/2024
 ms.author: eur
 ---
 
+### March 2024 release
+
+#### Whisper general availability (GA)
+
+The Whisper speech to text model with Azure AI Speech is now generally available.
+
+Check out [What is the Whisper model?](../../whisper-overview.md) to learn more about when to use Azure AI Speech vs. Azure OpenAI Service. 
+
 ### February 2024 release
 
 #### Pronunciation Assessment

articles/ai-services/speech-service/speech-container-ntts.md

@@ -30,7 +30,7 @@ The fully qualified container image name is, `mcr.microsoft.com/azure-cognitive-
 | Version | Path |
 |-----------|------------|
 | Latest | `mcr.microsoft.com/azure-cognitive-services/speechservices/neural-text-to-speech:latest`<br/><br/>The `latest` tag pulls the `en-US` locale and `en-us-arianeural` voice. |
-| 3.0.0 | `mcr.microsoft.com/azure-cognitive-services/speechservices/neural-text-to-speech:3.0.0-amd64-mr-in` |
+| 3.1.0 | `mcr.microsoft.com/azure-cognitive-services/speechservices/neural-text-to-speech:3.1.0-amd64-en-us-arianeural` |
 
 All tags, except for `latest`, are in the following format and are case sensitive:
 
@@ -44,19 +44,27 @@ The tags are also available [in JSON format](https://mcr.microsoft.com/v2/azure-
 {
   "name": "azure-cognitive-services/speechservices/neural-text-to-speech",
   "tags": [
-    "1.10.0-amd64-cs-cz-antoninneural",
-    "1.10.0-amd64-cs-cz-vlastaneural",
-    "1.10.0-amd64-de-de-conradneural",
-    "1.10.0-amd64-de-de-katjaneural",
-    "1.10.0-amd64-en-au-natashaneural",
+    <--redacted for brevity-->
+    "3.1.0-amd64-en-us-arianeural",
+    "3.1.0-amd64-en-us-guyneural",
+    "3.1.0-amd64-en-us-jennymultilingualneural",
+    "3.1.0-amd64-en-us-jennyneural",
+    "3.1.0-amd64-en-us-michelleneural",
+    "3.1.0-amd64-es-es-alvaroneural",
+    "3.1.0-amd64-es-es-elviraneural",
+    "3.1.0-amd64-es-mx-candelaneural",
+    "3.1.0-amd64-es-mx-dalianeural",
+    "3.1.0-amd64-es-mx-jorgeneural",
     <--redacted for brevity-->
     "latest"
   ]
 }
 ```
 
 > [!IMPORTANT]
-> We retired the standard speech synthesis voices and standard [text to speech](https://mcr.microsoft.com/product/azure-cognitive-services/speechservices/text-to-speech/tags) container on August 31, 2021. You should use neural voices with the [neural-text to speech](https://mcr.microsoft.com/product/azure-cognitive-services/speechservices/neural-text-to-speech/tags) container instead. For more information on updating your application, see [Migrate from standard voice to prebuilt neural voice](./how-to-migrate-to-prebuilt-neural-voice.md).
+> We retired the standard speech synthesis voices and standard [text to speech](https://mcr.microsoft.com/product/azure-cognitive-services/speechservices/text-to-speech/tags) container on August 31, 2021. You should use neural voices with the [neural-text-to-speech](https://mcr.microsoft.com/product/azure-cognitive-services/speechservices/neural-text-to-speech/tags) container version 3.0 and higher instead. 
+>
+> Starting from February 29, 2024, the text to speech and neural text to speech container versions 2.19 and earlier aren't supported. For more information on updating your application, see [Migrate from standard voice to prebuilt neural voice](./how-to-migrate-to-prebuilt-neural-voice.md).
 
 ## Get the container image with docker pull
 

articles/ai-services/speech-service/speech-container-overview.md

@@ -24,7 +24,7 @@ The following table lists the Speech containers available in the Microsoft Conta
 | [Speech to text](speech-container-stt.md) | Transcribes continuous real-time speech or batch audio recordings with intermediate results.  | Latest: 4.6.0<br/><br/>For all supported versions and locales, see the [Microsoft Container Registry (MCR)](https://mcr.microsoft.com/product/azure-cognitive-services/speechservices/speech-to-text/tags) and [JSON tags](https://mcr.microsoft.com/v2/azure-cognitive-services/speechservices/speech-to-text/tags/list).|
 | [Custom speech to text](speech-container-cstt.md) | Using a custom model from the [custom speech portal](https://speech.microsoft.com/customspeech), transcribes continuous real-time speech or batch audio recordings into text with intermediate results. | Latest: 4.6.0<br/><br/>For all supported versions and locales, see the [Microsoft Container Registry (MCR)](https://mcr.microsoft.com/product/azure-cognitive-services/speechservices/custom-speech-to-text/tags) and [JSON tags](https://mcr.microsoft.com/v2/azure-cognitive-services/speechservices/speech-to-text/tags/list). |
 | [Speech language identification](speech-container-lid.md)<sup>1, 2</sup> | Detects the language spoken in audio files. | Latest: 1.12.0<br/><br/>For all supported versions and locales, see the [Microsoft Container Registry (MCR)](https://mcr.microsoft.com/product/azure-cognitive-services/speechservices/language-detection/tags) and [JSON tags](https://mcr.microsoft.com/v2/azure-cognitive-services/speechservices/language-detection/tags/list). |
-| [Neural text to speech](speech-container-ntts.md) | Converts text to natural-sounding speech by using deep neural network technology, which allows for more natural synthesized speech. | Latest: 3.0.0<br/><br/>For all supported versions and locales, see the [Microsoft Container Registry (MCR)](https://mcr.microsoft.com/product/azure-cognitive-services/speechservices/neural-text-to-speech/tags) and [JSON tags](https://mcr.microsoft.com/v2/azure-cognitive-services/speechservices/neural-text-to-speech/tags/list). |
+| [Neural text to speech](speech-container-ntts.md) | Converts text to natural-sounding speech by using deep neural network technology, which allows for more natural synthesized speech. | Latest: 3.1.0<br/><br/>For all supported versions and locales, see the [Microsoft Container Registry (MCR)](https://mcr.microsoft.com/product/azure-cognitive-services/speechservices/neural-text-to-speech/tags) and [JSON tags](https://mcr.microsoft.com/v2/azure-cognitive-services/speechservices/neural-text-to-speech/tags/list). |
 
 <sup>1</sup> The container is available in public preview. Containers in preview are still under development and don't meet Microsoft's stability and support requirements.
 <sup>2</sup> Not available as a disconnected container.

articles/aks/network-observability-managed-cli.md

@@ -116,8 +116,8 @@ Use [az aks update](/cli/azure/aks#az-aks-update) to enable Network Observabilit
 
 ```azurecli-interactive
 az aks update \
-    --resource-group myResourceGroup \
-    --name myAKSCluster \
+    --resource-group myResourceGroup \
+    --name myAKSCluster \
     --enable-network-observability 
 ```
 

articles/cost-management-billing/manage/cancel-azure-subscription.md

@@ -6,7 +6,7 @@ ms.reviewer: tomasa
 ms.service: cost-management-billing
 ms.subservice: billing
 ms.topic: conceptual
-ms.date: 03/11/2024
+ms.date: 03/12/2024
 ms.author: banders
 ---
 
@@ -63,7 +63,7 @@ An account administrator without the service administrator or subscription owner
 
 ## Cancel a subscription in the Azure portal
 
-Depending on your environment, the cancel subscription experience allows you to:
+Depending on your environment, the subscription cancellation experience allows you to:
 
 - Cancel a subscription
 - Turn off autorenewal for an associated support plan
@@ -164,6 +164,30 @@ You don't have the permissions required to cancel a subscription. See [Who can c
 
 See the [Renewal and Cancellation](/visualstudio/subscriptions/faq/admin/renewal-cancellation) article. If you have any Visual Studio Azure subscriptions, they need to be canceled and deleted as well.
 
+## What data transfer fees are applied when moving all data off Azure?
+
+Azure now offers free egress for customers leaving Azure when taking out their data via the internet to another cloud provider or an on-premises data center. Use the following these steps to submit your request for free egress.
+
+### Create a support request
+
+1. To signal your intent to exit Azure and allow us to accommodate your request, create an [Azure Support request](https://portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/overview) and provide:
+    - Your _Subscription ID_ or _Enrollment ID_
+    - The date you plan to start your transfer
+    - An estimate of the amount of data you plan to egress
+1. Once your request is logged with Azure Support, you have 60 days from the date you indicate as your start data transfer date to egress your data out of Azure. If you need more than 60 days to egress your data, include an overview of your migration timeline in your initial Azure support request.
+1. After egressing your data, cancel all subscriptions associated with your account.
+1. Contact Azure Support and create a request to claim invoice-level credit for your egress charges incurred during your exit. You can either reopen your initial support request (step 1) or create a new Azure Support request. An invoice-level credit adjustment is applied to the existing balance.
+
+### Qualifications
+
+- You must provide advance notice of your intention to leave Azure to Azure Support by creating a support request discussed previously [(Step 1)](#create-a-support-request).
+- You must cancel all Azure subscriptions associated with your account after your data is transferred out before you can request your invoice-level credit.
+- You receive credit for a maximum of 60 calendar days of egress charges starting from the date you specified as your transfer start date.
+- Standard charges for Azure services and data transfer out from specialized services including Express Route, Express Route Direct, VPN, Azure Front Door, and Azure Content Delivery Network (CDN) aren't included in this credit offer. Only [egress charges](https://azure.microsoft.com/pricing/details/bandwidth/) as a result of moving Azure Storage data out of Azure are eligible for credits.
+- Azure reviews your request for adherence to the requirements. If we determine the customer request doesn't follow the documented process, we might not issue the credit request.
+- Azure might make changes regarding the egress credit policy in the future.
+- If a customer purchases Azure services through a partner, the partner is responsible for the credit request process, transferring data, canceling the applicable subscriptions and credit issuance to the customer.
+
 ## Next steps
 
 - If needed, you can reactivate a pay-as-you-go subscription in the [Azure portal](subscription-disabled.md).

articles/iot-edge/how-to-access-host-storage-from-module.md

@@ -72,6 +72,9 @@ Your deployment manifest would be similar to the following:
 }
 ```
 
+> [!NOTE]
+> If you are using a snap installation, ensure you choose a host storage path that is accessible to the snaps. For example, `$HOME/snap/azure-iot-edge/current/modules/`.
+
 ### Automatic host system permissions management
 
 On version 1.4 and newer, there's no need for manually setting ownership or permissions for host storage backing the `StorageFolder`. Permissions and ownership are automatically managed by the system modules during startup.

articles/iot-edge/how-to-provision-devices-at-scale-linux-symmetric.md

@@ -3,7 +3,7 @@ title: Create and provision IoT Edge devices using symmetric keys on Linux - Azu
 description: Use symmetric key attestation to test provisioning Linux devices at scale for Azure IoT Edge with device provisioning service
 author: PatAltimore
 ms.author: patricka
-ms.date: 08/26/2022
+ms.date: 02/27/2024
 ms.topic: conceptual
 ms.service: iot-edge
 services: iot-edge
@@ -51,18 +51,36 @@ Have the following information ready:
 * The device **Registration ID** you created
 * Either the **Primary Key** from an individual enrollment, or a [derived key](#derive-a-device-key) for devices using a group enrollment.
 
-1. Create a configuration file for your device based on a template file that is provided as part of the IoT Edge installation.
+Create a configuration file for your device based on a template file that is provided as part of the IoT Edge installation.
 
-   ```bash
-   sudo cp /etc/aziot/config.toml.edge.template /etc/aziot/config.toml
-   ```
+# [Ubuntu / Debian / RHEL](#tab/ubuntu+debian+rhel)
+
+```bash
+sudo cp /etc/aziot/config.toml.edge.template /etc/aziot/config.toml
+```
 
-1. Open the configuration file on the IoT Edge device.
+Open the configuration file on the IoT Edge device.
 
    ```bash
    sudo nano /etc/aziot/config.toml
    ```
 
+# [Ubuntu Core snaps](#tab/snaps)
+
+If using a snap installation of IoT Edge, the template file is located at `/snap/azure-iot-edge/current/etc/aziot/config.toml.edge.template`. Create a copy of the template file in your home directory and name it config.toml. For example:
+
+```bash
+cp /snap/azure-iot-edge/current/etc/aziot/config.toml.edge.template ~/config.toml
+```
+
+Open the configuration file in your home directory on the IoT Edge device.
+
+```bash
+nano ~/config.toml
+```
+
+---
+
 1. Find the **Provisioning** section of the file. Uncomment the lines for DPS provisioning with symmetric key, and make sure any other provisioning lines are commented out.
 
     ```toml
@@ -90,18 +108,29 @@ Have the following information ready:
 
    If you use any PKCS#11 URIs, find the **PKCS#11** section in the config file and provide information about your PKCS#11 configuration.
 
-1. Optionally, find the auto reprovisioning mode section of the file. Use the `auto_reprovisioning_mode` parameter to configure your device's reprovisioning behavior. **Dynamic** - Reprovision when the device detects that it may have been moved from one IoT Hub to another. This is the default. **AlwaysOnStartup** - Reprovision when the device is rebooted or a crash causes the daemon(s) to restart. **OnErrorOnly** - Never trigger device reprovisioning automatically. Each mode has an implicit device reprovisioning fallback if the device is unable to connect to IoT Hub during identity provisioning due to connectivity errors. For more information, see [IoT Hub device reprovisioning concepts](../iot-dps/concepts-device-reprovision.md).
+    For more information about provisioning configuration settings, see [Configure IoT Edge device settings](configure-device.md#provisioning).
 
-1. Optionally, uncomment the `payload` parameter to specify the path to a local JSON file. The contents of the file will be [sent to DPS as additional data](../iot-dps/how-to-send-additional-data.md#iot-edge-support) when the device registers. This is useful for [custom allocation](../iot-dps/how-to-use-custom-allocation-policies.md). For example, if you want to allocate your devices based on an IoT Plug and Play model ID without human intervention.
+1. Optionally, find the auto reprovisioning mode section of the file. Use the `auto_reprovisioning_mode` parameter to configure your device's reprovisioning behavior. **Dynamic** - Reprovision when the device detects that it may have been moved from one IoT Hub to another. This is the default. **AlwaysOnStartup** - Reprovision when the device is rebooted or a crash causes the daemons to restart. **OnErrorOnly** - Never trigger device reprovisioning automatically. Each mode has an implicit device reprovisioning fallback if the device is unable to connect to IoT Hub during identity provisioning due to connectivity errors. For more information, see [IoT Hub device reprovisioning concepts](../iot-dps/concepts-device-reprovision.md).
 
-1. Save and close the file.
+1. Optionally, uncomment the `payload` parameter to specify the path to a local JSON file. The contents of the file is [sent to DPS as additional data](../iot-dps/how-to-send-additional-data.md#iot-edge-support) when the device registers. This is useful for [custom allocation](../iot-dps/how-to-use-custom-allocation-policies.md). For example, if you want to allocate your devices based on an IoT Plug and Play model ID without human intervention.
 
-1. Apply the configuration changes that you made to IoT Edge.
+1. Save and close the file.
 
-   ```bash
-   sudo iotedge config apply
-   ```
+1. Apply the configuration changes that you made on the device.
 
+    # [Ubuntu / Debian / RHEL](#tab/ubuntu+debian+rhel)
+    ```bash
+    sudo iotedge config apply
+    ```
+    
+    # [Ubuntu Core snaps](#tab/snaps)
+    
+    ```bash
+    sudo snap set azure-iot-edge raw-config="$(cat ~/config.toml)"
+    ```
+    
+    ---
+    
 ## Verify successful installation
 
 If the runtime started successfully, you can go into your IoT Hub and start deploying IoT Edge modules to your device.