Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into mrb_06_28_2024_function_calling

Author: mrbullwinkle

.openpublishing.redirection.education.json

@@ -0,0 +1,9 @@
+{
+    "redirections": [
+        {
+            "source_path_from_root": "/articles/education-hub/custom-tenant-set-up-classroom.md",
+            "redirect_url": "/articles/education-hub/about-education-hub.md",
+            "redirect_document_id": false
+        }
+    ]
+    }

articles/ai-services/speech-service/includes/language-support/tts.md

@@ -27,6 +27,7 @@ ms.custom: references_regions
 | `ar-SY` | Arabic (Syria) | `ar-SY-AmanyNeural` (Female)<br/>`ar-SY-LaithNeural` (Male) |
 | `ar-TN` | Arabic (Tunisia) | `ar-TN-ReemNeural` (Female)<br/>`ar-TN-HediNeural` (Male) |
 | `ar-YE` | Arabic (Yemen) | `ar-YE-MaryamNeural` (Female)<br/>`ar-YE-SalehNeural` (Male) |
+| `as-IN` |Assamese (India) | `as-IN-YashicaNeural`<sup>5</sup> (Female)<br/>`as-IN-PriyomNeural`<sup>5</sup> (Male) |
 | `az-AZ` | Azerbaijani (Latin, Azerbaijan) | `az-AZ-BanuNeural`<sup>2</sup> (Female)<br/>`az-AZ-BabekNeural`<sup>2</sup> (Male) |
 | `bg-BG` | Bulgarian (Bulgaria) | `bg-BG-KalinaNeural` (Female)<br/>`bg-BG-BorislavNeural` (Male) |
 | `bn-BD` | Bangla (Bangladesh) | `bn-BD-NabanitaNeural`<sup>2</sup> (Female)<br/>`bn-BD-PradeepNeural`<sup>2</sup> (Male) |
@@ -117,6 +118,8 @@ ms.custom: references_regions
 | `ne-NP` | Nepali (Nepal) | `ne-NP-HemkalaNeural`<sup>2</sup> (Female)<br/>`ne-NP-SagarNeural`<sup>2</sup> (Male) |
 | `nl-BE` | Dutch (Belgium) | `nl-BE-DenaNeural` (Female)<br/>`nl-BE-ArnaudNeural` (Male) |
 | `nl-NL` | Dutch (Netherlands) | `nl-NL-FennaNeural` (Female)<br/>`nl-NL-MaartenNeural` (Male)<br/>`nl-NL-ColetteNeural` (Female) |
+| `or-IN` |Oriya (India) | `or-IN-SubhasiniNeural`<sup>5</sup> (Female)<br/>`or-IN-SukantNeural`<sup>5</sup> (Male) |
+| `pa-IN` | Punjabi (India) | `pa-IN-VaaniNeural`<sup>5</sup> (Female)<br/>`pa-IN-OjasNeural`<sup>5</sup> (Male) |
 | `pl-PL` | Polish (Poland) | `pl-PL-AgnieszkaNeural` (Female)<br/>`pl-PL-MarekNeural` (Male)<br/>`pl-PL-ZofiaNeural` (Female) |
 | `ps-AF` | Pashto (Afghanistan) | `ps-AF-LatifaNeural`<sup>2</sup> (Female)<br/>`ps-AF-GulNawazNeural`<sup>2</sup> (Male) |
 | `pt-BR` | Portuguese (Brazil) | `pt-BR-FranciscaNeural` (Female)<br/>`pt-BR-AntonioNeural` (Male)<br/>`pt-BR-BrendaNeural` (Female)<br/>`pt-BR-DonatoNeural` (Male)<br/>`pt-BR-ElzaNeural` (Female)<br/>`pt-BR-FabioNeural` (Male)<br/>`pt-BR-GiovannaNeural` (Female)<br/>`pt-BR-HumbertoNeural` (Male)<br/>`pt-BR-JulioNeural` (Male)<br/>`pt-BR-LeilaNeural` (Female)<br/>`pt-BR-LeticiaNeural` (Female)<br/>`pt-BR-ManuelaNeural` (Female)<br/>`pt-BR-NicolauNeural` (Male)<br/>`pt-BR-ThalitaMultilingualNeural`<sup>1,3</sup> (Female)<br/>`pt-BR-ValerioNeural` (Male)<br/>`pt-BR-YaraNeural` (Female)<br/>`pt-BR-ThalitaNeural`<sup>1</sup> (Female) |
@@ -167,3 +170,4 @@ ms.custom: references_regions
 
 <sup>4</sup> The OpenAI text to speech voices in Azure AI Speech are in public preview and only available in North Central US (`northcentralus`) and Sweden Central (`swedencentral`). Locales not listed for OpenAI voices aren't supported. For information about additional differences between OpenAI text to speech voices and Azure AI Speech text to speech voices, see [OpenAI text to speech voices](../../openai-voices.md#openai-text-to-speech-voices-via-azure-openai-service-or-via-azure-ai-speech).
 
+<sup>5</sup> The neural voices in public preview are only available in these service [regions](../../regions.md): East Asia, Southeast Asia, East US, West US, and Central India.

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

@@ -9,6 +9,21 @@ ms.custom: references_regions
 
 ### June 2024 release
 
+#### Prebuilt neural voice
+
+- Introducing 6 new voices in public preview available in specific regions: East Asia, Southeast Asia, East US, West US, and Central India.
+  
+  | Locale | Language    | Text to speech voices  |
+  |--------|-----------------|-------------------------|
+  | `or-IN`  | Oriya (India)   | `or-IN-SubhasiniNeural` (Female) |
+  | `or-IN`  | Oriya (India)   | `or-IN-SukantNeural` (Male)      | 
+  | `pa-IN`  | Punjabi (India) | `pa-IN-VaaniNeural` (Female)     |
+  | `pa-IN`  | Punjabi (India) | `pa-IN-OjasNeural` (Male)        | 
+  | `as-IN`  | Assamese (India)| `as-IN-YashicaNeural` (Female)   | 
+  | `as-IN`  | Assamese (India)| `as-IN-PriyomNeural` (Male)      |
+
+  See the [full language and voice list](../../language-support.md?tabs=tts) for more information.
+  
 #### Text to speech avatar
 
 - Text to speech avatar now supports the following regions: Southeast Asia, North Europe, West Europe, Sweden Central, South Central US, and West US 2. For more information, see [Speech service regions](../../regions.md#speech-service).

articles/aks/use-node-taints.md

@@ -250,6 +250,7 @@ This article assumes you have an existing AKS cluster. If you need an AKS cluste
     az aks nodepool update \
     --cluster-name $CLUSTER_NAME \
     --name $NODE_POOL_NAME \
+    --resource-group $RESOURCE_GROUP_NAME \
     --node-taints "sku=gpu:NoSchedule"
     ```
 
@@ -260,6 +261,7 @@ This article assumes you have an existing AKS cluster. If you need an AKS cluste
     ```azurecli-interactive
     az aks nodepool update \
     --cluster-name $CLUSTER_NAME \
+    --resource-group $RESOURCE_GROUP_NAME \
     --name $NODE_POOL_NAME \
     --node-taints ""
     ```
@@ -295,7 +297,7 @@ When you remove all initialization taint occurrences from node pool replicas, th
     az aks update \
     --resource-group $RESOURCE_GROUP_NAME \
     --name $CLUSTER_NAME \
-    --node-init-taints "sku=gpu:NoSchedule"
+    --node-init-taints ""
     ```
 
 ## Check that the taint has been removed from the node

articles/app-service/environment/side-by-side-migrate.md

@@ -4,7 +4,7 @@ description: Learn how to migrate your App Service Environment v2 to App Service
 author: seligj95
 ms.topic: tutorial
 ms.custom: devx-track-azurecli, references_regions
-ms.date: 6/26/2024
+ms.date: 6/28/2024
 ms.author: jordanselig
 ---
 # Migration to App Service Environment v3 using the side-by-side migration feature
@@ -17,7 +17,7 @@ ms.author: jordanselig
 
 App Service can automate migration of your App Service Environment v1 and v2 to an [App Service Environment v3](overview.md). There are different migration options. Review the [migration path decision tree](upgrade-to-asev3.md#migration-path-decision-tree) to decide which option is best for your use case. App Service Environment v3 provides [advantages and feature differences](overview.md#feature-differences) over earlier versions. Make sure to review the [supported features](overview.md#feature-differences) of App Service Environment v3 before migrating to reduce the risk of an unexpected application issue. 
 
-The side-by-side migration feature automates your migration to App Service Environment v3. The side-by-side migration feature creates a new App Service Environment v3 with all of your apps in a different subnet. Your existing App Service Environment isn't deleted until you initiate its deletion at the end of the migration process. Because of this process, there's a rollback option if you need to cancel your migration. This migration option is best for customers who want to migrate to App Service Environment v3 with zero downtime and can support using a different subnet for their new environment. If you need to use the same subnet and can support about one hour of application downtime, see the [in-place migration feature](migrate.md). For manual migration options that allow you to migrate at your own pace, see [manual migration options](migration-alternatives.md).
+The side-by-side migration feature automates your migration to App Service Environment v3. The side-by-side migration feature creates a new App Service Environment v3 with all of your apps in a different subnet. Your existing App Service Environment isn't deleted until you initiate its deletion at the end of the migration process. This migration option is best for customers who want to migrate to App Service Environment v3 with zero downtime and can support using a different subnet for their new environment. If you need to use the same subnet and can support about one hour of application downtime, see the [in-place migration feature](migrate.md). For manual migration options that allow you to migrate at your own pace, see [manual migration options](migration-alternatives.md).
 
 > [!IMPORTANT]
 > If you fail to complete all steps described in this tutorial, you'll experience downtime. For example, if you don't update all dependent resources with the new IP addresses or you don't allow access to/from your new subnet, such as the case for your custom domain suffix key vault, you'll experience downtime until that's addressed.
@@ -215,7 +215,7 @@ Once you're ready to redirect traffic, you can complete the final step of the mi
 > You have 14 days to complete this step. If you don't complete this step in 14 days, your migration is automatically reverted back to an App Service Environment v2. If you need more than 14 days to complete this step, contact support.
 >
 
-If you discover any issues with your new App Service Environment v3, don't run the command to redirect customer traffic. This command also initiates the deletion of your App Service Environment v2. If you find an issue, you can revert all changes and return to your old App Service Environment v2. The revert process takes 3 to 6 hours to complete. Once the revert process completes, your old App Service Environment is back online and your new App Service Environment v3 is deleted. You can then attempt the migration again once you resolve any issues.
+If you discover any issues with your new App Service Environment v3, don't run the command to redirect customer traffic. This command also initiates the deletion of your App Service Environment v2. If you find an issue, contact support.
 
 ## Use the side-by-side migration feature
 
@@ -445,7 +445,7 @@ This step is your opportunity to test and validate your new App Service Environm
 
 Once you confirm your apps are working as expected, you can finalize the migration by running the following command. This command also deletes your old environment. You have 14 days to complete this step. If you don't complete this step in 14 days, your migration is automatically reverted back to an App Service Environment v2. If you need more than 14 days to complete this step, contact support.
 
-If you find any issues or decide at this point that you no longer want to proceed with the migration, contact support to revert the migration. Don't run the DNS change command if you need to revert the migration. For more information, see [Revert migration](#redirect-customer-traffic-validate-your-app-service-environment-v3-and-complete-migration).
+If you find any issues or decide at this point that you no longer want to proceed with the migration, contact support to discuss your options. Don't run the DNS change command since that command completes the migration.
 
 ```azurecli
 az rest --method post --uri "${ASE_ID}/NoDowntimeMigrate?phase=DnsChange&api-version=2022-03-01"
@@ -494,7 +494,7 @@ The App Service plan SKUs available for App Service Environment v3 run on the Is
 - **What properties of my App Service Environment will change?**  
   You're on App Service Environment v3 so be sure to review the [features and feature differences](overview.md#feature-differences) compared to previous versions. Both your inbound and outbound IPs change when using the side-by-side migration feature. Note for ELB App Service Environment, previously there was a single IP for both inbound and outbound. For App Service Environment v3, they're separate. For more information, see [App Service Environment v3 networking](networking.md#addresses). For a full comparison of the App Service Environment versions, see [App Service Environment version comparison](version-comparison.md).
 - **What happens if migration fails or there is an unexpected issue during the migration?**  
-  If there's an unexpected issue, support teams are on hand. We recommend that you migrate dev environments before touching any production environments to learn about the migration process and see how it impacts your workloads. With the side-by-side migration feature, you can revert all changes if there's any issues.
+  If there's an unexpected issue, support teams are on hand. We recommend that you migrate dev environments before touching any production environments to learn about the migration process and see how it impacts your workloads.
 - **What happens to my old App Service Environment?**  
   If you decide to migrate an App Service Environment using the side-by-side migration feature, your old environment is used up until the final step in the migration process. Once you complete the final step, the old environment and all of the apps hosted on it get shutdown and deleted. Your old environment is no longer accessible. A revert to the old environment at this point isn't possible.
 - **What will happen to my App Service Environment v1/v2 resources after 31 August 2024?**  

articles/azure-arc/data/validation-program.md

@@ -79,10 +79,11 @@ To see how all Azure Arc-enabled components are validated, see [Validation progr
 
 ### PureStorage
 
-|Solution and version | Kubernetes version | Azure Arc-enabled data services version | SQL engine version | PostgreSQL server version
+|Solution and version | Kubernetes version | Azure Arc-enabled data services version | SQL engine version | PostgreSQL server version|
 |-----|-----|-----|-----|-----|
-| Portworx Enterprise 2.7	1.22.5 | 1.20.7 | 1.1.0_2021-11-02 | 15.0.2148.140 | Not validated |
-| Portworx Enterprise 2.9 | 1.22.5 | 1.1.0_2021-11-02 | 15.0.2195.191 |  12.3 (Ubuntu 12.3-1) |
+|[Portworx Enterprise 3.1](https://www.purestorage.com/products/cloud-native-applications/portworx.html)|1.28.7|1.30.0_2024-06-11|16.0.5349.20214|Not validated|
+|Portworx Enterprise 2.7	1.22.5 |1.20.7 |1.1.0_2021-11-02 |15.0.2148.140 |Not validated |
+|Portworx Enterprise 2.9 |1.22.5 |1.1.0_2021-11-02 |15.0.2195.191 |12.3 (Ubuntu 12.3-1) |
 
 ### Red Hat
 

articles/azure-monitor/agents/azure-monitor-agent-migration.md

@@ -19,10 +19,10 @@ Migration is a complex task. Start planning your migration to Azure Monitor Agen
 
 > [!IMPORTANT]
 > The Log Analytics agent will be [retired on **August 31, 2024**](https://azure.microsoft.com/updates/were-retiring-the-log-analytics-agent-in-azure-monitor-on-31-august-2024/). You can expect the following when you use the MMA or OMS agent after this date.
-> - **Data upload:** Cloud ingestion services will gradually reduce support for MMA agents, which may result in decreased support and potential compatibility issues for MMA agents over time.  Ingestion for MMA will be unchanged until Febuary 1 2025.
-> - **Installation:** The ability to install the legacy agents will be removed from the Azure Portal and installation policies for legacy agents will be removed. You can still install the MMA agents extension as well as perfrom offline installations.
+> - **Data upload:** Cloud ingestion services will gradually reduce support for MMA agents, which may result in decreased support and potential compatibility issues for MMA agents over time.  Ingestion for MMA will be unchanged until February 1 2025.
+> - **Installation:** The ability to install the legacy agents will be removed from the Azure Portal and installation policies for legacy agents will be removed. You can still install the MMA agents extension as well as perform offline installations.
 > - **Customer Support:** You will not be able to get support for legacy agent issues.
-> - **OS Support:** Support for new Linux or Windows distros, incluing service packs won't be added after the deprecation of the legacy agents.
+> - **OS Support:** Support for new Linux or Windows distros, including service packs, won't be added after the deprecation of the legacy agents.
 
 ## Before you begin
 

articles/azure-resource-manager/bicep/bicep-config-modules.md

@@ -3,7 +3,7 @@ title: Module setting for Bicep config
 description: Describes how to customize configuration values for modules in Bicep deployments.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 02/16/2024
+ms.date: 06/28/2024
 ---
 
 # Add module settings in the Bicep config file
@@ -100,13 +100,16 @@ For a template spec, use:
 module stgModule  'ts/CoreSpecs:storage:v1' = {
 ```
 
-An alias has been predefined for the [public module registry](./modules.md#path-to-module). To reference a public module, you can use the format:
+An alias has been predefined for [public modules](./modules.md#file-in-registry). To reference a public module, you can use the format:
 
 ```bicep
 br/public:<file>:<tag>
 ```
 
-You can override the public module registry alias definition in the bicepconfig.json file:
+> [!NOTE]
+> Non-AVM (Azure Verified Modules) modules are retired from the public module registry with most of them available as AVM modules.
+
+You can override the public module registry alias definition in the [bicepconfig.json file](./bicep-config.md):
 
 ```json
 {

articles/azure-resource-manager/bicep/bicep-using.md

@@ -3,7 +3,7 @@ title: Using statement
 description: Describes how to use the using statement in Bicep.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 10/11/2023
+ms.date: 06/28/2024
 ---
 
 # Using statement
@@ -29,7 +29,7 @@ The `using` statement in [Bicep parameter files](./parameter-files.md) ties the
   using '<path>/<file-name>.json'
   ```
 
-- To use public module:
+- To use [public modules](./modules.md#path-to-module):
 
   ```bicep
   using 'br/public:<file-path>:<tag>'
@@ -38,7 +38,7 @@ The `using` statement in [Bicep parameter files](./parameter-files.md) ties the
   For example:
 
   ```bicep
-  using 'br/public:storage/storage-account:3.0.1'
+  using 'br/public:avm/res/storage/storage-account:0.9.0' 
 
   param name = 'mystorage'
   ```