Merge pull request #263979 from MicrosoftDocs/repo_sync_working_branch

Taojunshen · web-flow · commit 146de42652ad · 2024-01-23T14:45:17.000-08:00
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
diff --git a/articles/ai-services/speech-service/batch-transcription-get.md b/articles/ai-services/speech-service/batch-transcription-get.md
@@ -23,7 +23,7 @@ To get transcription results, first check the [status](#get-transcription-status
 To get the status of the transcription job, call the [Transcriptions_Get](https://eastus.dev.cognitive.microsoft.com/docs/services/speech-to-text-api-v3-1/operations/Transcriptions_Get) operation of the [Speech to text REST API](rest-speech-to-text.md).
 
 > [!IMPORTANT]
-> Batch transcription jobs are scheduled on a best-effort basis. At pick hours it may take up to 30 minutes or longer for a transcription job to start processing. Most of the time during the execution the transcription status will be `Running`. This is because the job is assigned with `Running` status the moment it moves to the batch transcription backend system, which happens almost immediately when base model is used, and slightly slower for custom models. Thus the amount of time a transcription job spends in `Running` state doesn't correspond to the actual transcription time, but also includes waiting time in the internal queues.
+> Batch transcription jobs are scheduled on a best-effort basis. At peak hours, it may take up to 30 minutes or longer for a transcription job to start processing. Most of the time during the execution the transcription status will be `Running`. This is because the job is assigned the `Running` status the moment it moves to the batch transcription backend system. When the base model is used, this assignment happens almost immediately; it's slightly slower for custom models. Thus, the amount of time a transcription job spends in the `Running` state doesn't correspond to the actual transcription time but also includes waiting time in the internal queues.
 
 Make an HTTP GET request using the URI as shown in the following example. Replace `YourTranscriptionId` with your transcription ID, replace `YourSubscriptionKey` with your Speech resource key, and replace `YourServiceRegion` with your Speech resource region.
 
@@ -77,7 +77,7 @@ The `status` property indicates the current status of the transcriptions. The tr
 ::: zone pivot="speech-cli"
 
 > [!IMPORTANT]
-> Batch transcription jobs are scheduled on a best-effort basis. At pick hours it may take up to 30 minutes or longer for a transcription job to start processing. Most of the time during the execution the transcription status will be `Running`. This is because the job is assigned with `Running` status the moment it moves to the batch transcription backend system, which happens almost immediately when base model is used, and slightly slower for custom models. Thus the amount of time a transcription job spends in `Running` state doesn't correspond to the actual transcription time, but also includes waiting time in the internal queues.
+> Batch transcription jobs are scheduled on a best-effort basis. At peak hours, it may take up to 30 minutes or longer for a transcription job to start processing. Most of the time during the execution the transcription status will be `Running`. This is because the job is assigned the `Running` status the moment it moves to the batch transcription backend system. When the base model is used, this assignment happens almost immediately; it's slightly slower for custom models. Thus, the amount of time a transcription job spends in the `Running` state doesn't correspond to the actual transcription time but also includes waiting time in the internal queues.
 
 To get the status of the transcription job, use the `spx batch transcription status` command. Construct the request parameters according to the following instructions:
 
diff --git a/articles/ai-services/speech-service/how-to-pronunciation-assessment.md b/articles/ai-services/speech-service/how-to-pronunciation-assessment.md
@@ -617,6 +617,16 @@ You can get pronunciation assessment scores for:
 - Syllable groups
 - Phonemes in [SAPI](/previous-versions/windows/desktop/ee431828(v=vs.85)#american-english-phoneme-table) or [IPA](https://en.wikipedia.org/wiki/IPA) format
 
+## Supported features per locale
+
+The following table summarizes which feature are supported per locale. You can read more on the specific feature in the sections below.
+
+| Phoneme alphabet | IPA | SAPI |
+|-----------|-------------|-------------|
+| Phoneme name | `en-US` | `en-US`, `en-GB`, `zh-CN` |
+| Syllable group | `en-US` | `en-US`, `en-GB` |
+| Spoken phoneme | `en-US` | `en-US`, `en-GB` |
+
 ## Syllable groups
 
 Pronunciation assessment can provide syllable-level assessment results. Grouping in syllables is more legible and aligned with speaking habits, as a word is typically pronounced syllable by syllable rather than phoneme by phoneme.
diff --git a/articles/ai-services/speech-service/regions.md b/articles/ai-services/speech-service/regions.md
@@ -44,7 +44,7 @@ The following regions are supported for Speech service features such as speech t
 | Europe | France Central | `francecentral` |
 | Europe | Germany West Central | `germanywestcentral` |
 | Europe | Norway East | `norwayeast` |
-| Europe | Sweden Central | `swedentcentral`<sup>8</sup> |
+| Europe | Sweden Central | `swedencentral`<sup>8</sup> |
 | Europe | Switzerland North | `switzerlandnorth` <sup>6</sup>|
 | Europe | Switzerland West | `switzerlandwest` |
 | Europe | UK South | `uksouth` <sup>1,2,3,4,7</sup>|
diff --git a/articles/ai-services/speech-service/text-to-speech-avatar/real-time-synthesis-avatar.md b/articles/ai-services/speech-service/text-to-speech-avatar/real-time-synthesis-avatar.md
@@ -76,8 +76,8 @@ The following code snippet shows how to set avatar character and style:
 
 ```JavaScript
 const avatarConfig = new SpeechSDK.AvatarConfig(
-"lisa", // Set avatar character here.
-"casual-sitting", // Set avatar style here.
+    "lisa", // Set avatar character here.
+    "casual-sitting", // Set avatar style here.
 );  
 ```
 
@@ -138,7 +138,7 @@ var avatarSynthesizer = new SpeechSDK.AvatarSynthesizer(speechConfig, avatarConf
 
 // Start avatar and establish WebRTC connection
 avatarSynthesizer.startAvatarAsync(peerConnection).then(
-(r) => { console.log("Avatar started.") }
+    (r) => { console.log("Avatar started.") }
 ).catch(
     (error) => { console.log("Avatar failed to start. Error: " + error) }
 );
diff --git a/articles/aks/deploy-confidential-containers-default-policy.md b/articles/aks/deploy-confidential-containers-default-policy.md
@@ -271,7 +271,7 @@ For this preview release, we recommend for test and evaluation purposes to eithe
           command:
             - /bin/skr
           volumeMounts:
-            - mountPath: /opt/confidential-containers/share/kata-containers/reference-info-base64d
+            - mountPath: /opt/confidential-containers/share/kata-containers/reference-info-base64
               name: endor-loc
         - image: "mcr.microsoft.com/acc/samples/kafka/consumer:1.0"
           imagePullPolicy: Always
@@ -297,7 +297,7 @@ For this preview release, we recommend for test and evaluation purposes to eithe
       volumes:
         - name: endor-loc
           hostPath:
-            path: /opt/confidential-containers/share/kata-containers/reference-info-base64d
+            path: /opt/confidential-containers/share/kata-containers/reference-info-base64
     ---
     apiVersion: v1
     kind: Service
diff --git a/articles/iot-hub-device-update/create-update-group.md b/articles/iot-hub-device-update/create-update-group.md
@@ -197,6 +197,17 @@ az iot du device group show \
 
 ---
 
+## Removing a device from a device group
+
+To remove a device from a device group, the ADUGroup tag value must be changed to "null".
+
+   ```JSON
+       "tags": {
+               "ADUGroup": "null"
+               }
+   ```
+This will delete the ADUGroup tag from the device twin and remove the device from its device group.
+
 ## Deleting device groups
 
 While device groups are automatically created, groups, device classes and deployments are not automatically cleaned up so as to retain them for historical records or other user needs. Device groups can be deleted through Azure portal by individually selecting and deleting the desired groups, or by calling the DELETE API on the group. [Learn more](/cli/azure/iot/du/device/group#az-iot-du-device-group-delete)
diff --git a/articles/iot-operations/connect-to-cloud/tutorial-connect-event-grid.md b/articles/iot-operations/connect-to-cloud/tutorial-connect-event-grid.md
@@ -63,8 +63,16 @@ d84481ae-9181-xxxx-xxxx-xxxxxxxxxxxx
 
 Then, use Azure CLI to assign publisher and subscriber roles to IoT MQ for the topic space you created. Replace `<MQ_ID>` with the principal ID you found in the previous step, and replace `<SUBSCRIPTION_ID>`, `<RESOURCE_GROUP>`, `<EG_NAME>` with your values matching the Event Grid namespace you created.
 
+Assigning the publisher role:
+
+```azurecli
+az role assignment create --assignee <MQ_ID> --role "EventGrid TopicSpaces Publisher" --scope /subscriptions/<SUBSCRIPTION_ID>/resourceGroups/<RESOURCE_GROUP>/providers/Microsoft.EventGrid/namespaces/<EG_NAME>/topicSpaces/tutorial
+```
+
+Assigning the subscriber role:
+
 ```azurecli
-az role assignment create --assignee <MQ_ID> --role "EventGrid TopicSpaces Publisher" --role "EventGrid TopicSpaces Subscriber" --scope /subscriptions/<SUBSCRIPTION_ID>/resourceGroups/<RESOURCE_GROUP>/providers/Microsoft.EventGrid/namespaces/<EG_NAME>/topicSpaces/tutorial
+az role assignment create --assignee <MQ_ID> --role "EventGrid TopicSpaces Subscriber" --scope /subscriptions/<SUBSCRIPTION_ID>/resourceGroups/<RESOURCE_GROUP>/providers/Microsoft.EventGrid/namespaces/<EG_NAME>/topicSpaces/tutorial
 ```
 
 > [!TIP]
diff --git a/articles/machine-learning/concept-v2.md b/articles/machine-learning/concept-v2.md
@@ -92,7 +92,7 @@ SDK v2 is useful in the following scenarios:
 
 ## Should I use v1 or v2?
 
-Support for CLI v2 will end on September 30, 2025.  
+Support for CLI v1 will end on September 30, 2025.  
 
 We encourage you to migrate your code for both CLI and SDK v1 to CLI and SDK v2. For more information, see [Upgrade to v2](how-to-migrate-from-v1.md).
 
diff --git a/articles/openshift/configure-azure-ad-ui.md b/articles/openshift/configure-azure-ad-ui.md
@@ -118,3 +118,7 @@ Scroll down to the **Claims** section and update the **Preferred Username** to u
 If you now logout of the OpenShift Web Console and try to login again, you'll be presented with a new option to login with **Microsoft Entra ID**. You may need to wait for a few minutes.
 
 ![Login screen with Microsoft Entra option](media/aro4-login-2.png)
+
+
+> [!NOTE]
+> If you encounter the error like "AADSTS50011: The redirect URI https\://oauth-openshift.apps.xxxxxxxxxx.xxxxxxx.aroapp.io/oauth2callback/xxxx specified in the request does not match the redirect URIs configured", you can follow the troubleshooting guide [Azure AD (OIDC) login failed when Redirect URI is not set correctly](https://access.redhat.com/solutions/7016893) to solve the issue.  
diff --git a/articles/sap/workloads/sap-hana-high-availability.md b/articles/sap/workloads/sap-hana-high-availability.md
@@ -275,7 +275,7 @@ Replace `<placeholders>` with the values for your SAP HANA installation.
 
    To install SAP HANA system replication, review chapter 4 in the [SAP HANA SR Performance Optimized Scenario](https://www.suse.com/products/sles-for-sap/resource-library/sap-best-practices/) guide.
 
-1. **[A]** Run the **hdblcm** program from the HANA DVD.
+1. **[A]** Run the **hdblcm** program from the HANA installation media.
 
    When you're prompted, enter the following values:
 
diff --git a/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-automatic-upgrade.md b/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-automatic-upgrade.md
@@ -140,7 +140,7 @@ The following platform SKUs are currently supported (and more are added periodic
 - Must use application health probes or [Application Health extension](virtual-machine-scale-sets-health-extension.md) for non-Service Fabric scale sets. For Service Fabric requirements, see [Service Fabric requirement](#service-fabric-requirements).
 - Use Compute API version 2018-10-01 or higher.
 - Ensure that external resources specified in the scale set model are available and updated. Examples include SAS URI for bootstrapping payload in VM extension properties, payload in storage account, reference to secrets in the model, and more.
-- For scale sets using Windows virtual machines, starting with Compute API version 2019-03-01, the *virtualMachineProfile.osProfile.windowsConfiguration.enableAutomaticUpdates* property must set to *false* in the scale set model definition. The *enableAutomaticUpdates* property enables in-VM patching where "Windows Update" applies operating system patches without replacing the OS disk. With automatic OS image upgrades enabled on your scale set, an extra patching process through Windows Update is not required.
+- For scale sets using Windows virtual machines, starting with Compute API version 2019-03-01, the *virtualMachineProfile.osProfile.windowsConfiguration.enableAutomaticUpdates* property must set to *false* in the scale set model definition. The *enableAutomaticUpdates* property enables in-VM patching where "Windows Update" applies operating system patches without replacing the OS disk. With automatic OS image upgrades enabled on your scale set, which can be done by setting the *automaticOSUpgradePolicy.enableAutomaticOSUpgrade* to *true*, an extra patching process through Windows Update is not required.
 
 > [!NOTE]
 > After an OS disk is replaced through reimage or upgrade, the attached data disks may have their drive letters reassigned. To retain the same drive letters for attached disks, it is suggested to use a custom boot script.
@@ -153,7 +153,7 @@ If you are using Service Fabric, ensure the following conditions are met:
 -	The Service Fabric extension on the scale set model definition must have TypeHandlerVersion 1.1 or above.
 -	Durability level should be the same at the Service Fabric cluster and Service Fabric extension on the scale set model definition.
 - An additional health probe or use of application health extension is not required for Silver or Gold durability. Bronze durability with Stateless-only node types requires an additional health probe.
-- The property *virtualMachineProfile.osProfile.windowsConfiguration.enableAutomaticUpdates* property must set to *false* in the scale set model definition. The *enableAutomaticUpdates* property enables in-VM patching using "Windows Update" and is not supported on Service Fabric scale sets.
+- The property *virtualMachineProfile.osProfile.windowsConfiguration.enableAutomaticUpdates* property must set to *false* in the scale set model definition. The *enableAutomaticUpdates* property enables in-VM patching using "Windows Update" and is not supported on Service Fabric scale sets. You should use the *automaticOSUpgradePolicy.enableAutomaticOSUpgrade* property instead.
 
 Ensure that durability settings are not mismatched on the Service Fabric cluster and Service Fabric extension, as a mismatch will result in upgrade errors. Durability levels can be modified per the guidelines outlined on [this page](../service-fabric/service-fabric-cluster-capacity.md#changing-durability-levels).
 
@@ -177,6 +177,9 @@ To configure automatic OS image upgrade, ensure that the *automaticOSUpgradePoli
 > [!NOTE]
 > **Upgrade Policy mode** and **Automatic OS Upgrade Policy** are separate settings and control different aspects of the scale set. When there are changes in the scale set template, the Upgrade Policy `mode` will determine what happens to existing instances in the scale set. However, Automatic OS Upgrade Policy `enableAutomaticOSUpgrade` is specific to the OS image and tracks changes the image publisher has made and determines what happens when there is an update to the image.
 
+> [!Note]
+> If `enableAutomaticOSUpgrade` is set to *true*, `enableAutomaticUpdates` is automatically set to *false* and cannot be set to *true*.
+
 ### REST API
 The following example describes how to set automatic OS upgrades on a scale set model:
 
diff --git a/articles/virtual-machines/workloads/redhat/redhat-rhui.md b/articles/virtual-machines/workloads/redhat/redhat-rhui.md
@@ -339,7 +339,7 @@ If you experience problems connecting to Azure RHUI from your Azure RHEL PAYG VM
 
 In September 2016, Azure deployed an updated Azure RHUI. In April 2017, the old Azure RHUI was shut down. If you have been using the RHEL PAYG images or their snapshots from September 2016 or later, you're automatically connecting to the new Azure RHUI. If, however, you have older snapshots on your VMs, you need to manually update their configuration to access the Azure RHUI as described in a following section.
 
-The new Azure RHUI servers are deployed with [Azure Traffic Manager](https://azure.microsoft.com/services/traffic-manager/). In Traffic Manager, any VM can use a single endpoint, rhui-1.microsoft.com and rhui4-1.microfot.com, regardless of region.
+The new Azure RHUI servers are deployed with [Azure Traffic Manager](https://azure.microsoft.com/services/traffic-manager/). In Traffic Manager, any VM can use a single endpoint, rhui-1.microsoft.com and rhui4-1.microsoft.com, regardless of region.
 
 ### Manual update procedure to use the Azure RHUI servers
 
