Merge pull request #268910 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/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/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/iot-hub/iot-hub-devguide-messaging.md

@@ -29,7 +29,7 @@ Learn more about these topics:
 
 * [Understand IoT Hub endpoints](iot-hub-devguide-endpoints.md#custom-endpoints-for-message-routing)
 
-* [Use IoT Hub message routing to send device-to-cloud messages to different endponts](iot-hub-devguide-messages-d2c.md)
+* [Use IoT Hub message routing to send device-to-cloud messages to different endpoints](iot-hub-devguide-messages-d2c.md)
 
 ## Send cloud-to-device messages from IoT Hub
 

articles/openshift/openshift-faq.yml

@@ -31,7 +31,7 @@ sections:
         answer: |
           The actual number of supported pods depends on an application’s memory, CPU, and storage requirements.
           
-          Azure Red Hat OpenShift 4.x has a 250 pod-per-node limit and a 60 compute node limit. These limits cap the maximum number of pods supported in a cluster to 250×60 = 15,000. If the cluster is created using User Defined Routing (UDR) and runs version 4.11 or higher, the limits are 120 compute nodes and 30,000 pods.
+          Azure Red Hat OpenShift 4.x has a 250 pod-per-node limit and a 60 compute node limit. These limits cap the maximum number of pods supported in a cluster to 250×60 = 15,000. For a private cluster without any public IPs (for example, created by using [User Defined Routing (UDR)](howto-create-private-cluster-4x.md#create-a-private-cluster-without-a-public-ip-address) and running version 4.11 or higher), the limits are 120 compute nodes and 30,000 pods.
           
       - question: Can a cluster have compute nodes across multiple Azure regions?
         answer: No. All nodes in an Azure Red Hat OpenShift cluster must originate in the same Azure region.

articles/postgresql/flexible-server/concepts-major-version-upgrade.md

@@ -61,6 +61,7 @@ If in-place major version upgrade pre-check operations fail, then the upgrade ab
 
 -	Servers configured with logical replication slots aren't supported. 
 
+- In-place major version upgrade doesn't yet support upgrading to version 16, our team is actively working on this feature.
 
 ## Next steps
 

articles/reliability/availability-zones-migration-overview.md

@@ -43,8 +43,11 @@ The table below lists each product that offers migration guidance and/or informa
 | --- | 
 | [Azure API Management](migrate-api-mgt.md)|
 | [Azure App Configuration](migrate-app-configuration.md)|
+| [Azure App Service](reliability-app-service.md#availability-zone-support)|
+| [Azure Batch](reliability-batch.md#availability-zone-migration)|
 | [Azure Cache for Redis](migrate-cache-redis.md)|
 | [Azure AI Search](migrate-search-service.md)|
+| [Azure Container Apps](reliability-azure-container-apps.md#availability-zone-migration)|
 | [Azure Container Instances](migrate-container-instances.md)|
 | [Azure Container Registry](/azure/container-registry/zone-redundancy?toc=/azure/reliability) |
 | [Azure Cosmos DB](/azure/cosmos-db/high-availability?toc=/azure/reliability) |

articles/virtual-desktop/licensing.md

@@ -16,7 +16,7 @@ This article explains the licensing requirements for using Azure Virtual Desktop
 In the context of providing virtualized infrastructure with Azure Virtual Desktop, *internal users* (for internal commercial purposes) refers to people who are members of your own organization, such as employees of a business or students of a school, including external vendors or contractors. *External users* (for external commercial purposes) aren't members of your organization, but your customers where you might provide a Software-as-a-Service (SaaS) application using Azure Virtual Desktop.
 
 > [!NOTE]
-> Take care not to confuse external *users* with external *identities*. Azure Virtual Desktop doesn't support external identities, including guest accounts or business-to-business (B2B) identities. Whether you're serving internal commercial purposes or external users with Azure Virtual Desktop, you'll need to create and manage identities for those users yourself. For more information, see [Recommendations for deploying Azure Virtual Desktop for internal or external commercial purposes](organization-internal-external-commercial-purposes-recommendations.md).
+> Take care not to confuse external *users* with external *identities*. Azure Virtual Desktop doesn't support external identities, including external guest accounts or business-to-business (B2B) identities. Whether you're serving internal commercial purposes or external users with Azure Virtual Desktop, you'll need to create and manage identities for those users yourself. For more information, see [Recommendations for deploying Azure Virtual Desktop for internal or external commercial purposes](organization-internal-external-commercial-purposes-recommendations.md).
 
 Licensing Azure Virtual Desktop works differently for internal and external commercial purposes. Consider the following examples:
 
@@ -27,7 +27,7 @@ Licensing Azure Virtual Desktop works differently for internal and external comm
 - A software vendor called *Contoso* might use Azure Virtual Desktop to sell remote access of Contoso's productivity app to Contoso's customers (external users). Because Contoso is serving external users for external commercial purposes, Contoso must enroll in Azure Virtual Desktop's per-user access pricing. This enables Contoso to pay for Azure Virtual Desktop access rights on behalf of those external users who connect to Contoso's deployment. The users don't need a separate license like Microsoft 365 to access Azure Virtual Desktop. Contoso still needs to create and manage identities for those external users.
 
 > [!IMPORTANT]
-> Per-user access pricing can only be used for external commercial purposes, not internal purposes. Per-user access pricing isn't a way to enable guest user accounts with Azure Virtual Desktop. Check if your Azure Virtual Desktop solution is is applicable for per-user access pricing by reviewing [our licensing documentation](https://www.microsoft.com/licensing/terms/productoffering/MicrosoftAzure/EAEAS#Documents).
+> Per-user access pricing can only be used for external commercial purposes, not internal purposes. Per-user access pricing isn't a way to enable external guest user accounts with Azure Virtual Desktop. Check if your Azure Virtual Desktop solution is is applicable for per-user access pricing by reviewing [our licensing documentation](https://www.microsoft.com/licensing/terms/productoffering/MicrosoftAzure/EAEAS#Documents).
 
 ## Eligible licenses to use Azure Virtual Desktop