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

Author: HeidiSteen

articles/active-directory/verifiable-credentials/verifiable-credentials-configure-tenant.md

@@ -7,7 +7,7 @@ author: barclayn
 manager: karenhoran
 ms.author: barclayn
 ms.topic: tutorial
-ms.date: 04/26/2022
+ms.date: 05/06/2022
 # Customer intent: As an enterprise, we want to enable customers to manage information about themselves by using verifiable credentials.
 
 ---
@@ -16,16 +16,15 @@ ms.date: 04/26/2022
 
 Azure Active Directory (Azure AD) Verifiable Credentials safeguards your organization with an identity solution that's seamless and decentralized. The service allows you to issue and verify credentials. For issuers, Azure AD provides a service that they can customize and use to issue their own verifiable credentials. For verifiers, the service provides a free REST API that makes it easy to request and accept verifiable credentials in your apps and services.
 
-In this tutorial, you learn how to configure your Azure AD tenant so it can use this credentials service.
+In this tutorial, you learn how to configure your Azure AD tenant so it can use the verifiable credentials service.
 
 Specifically, you learn how to:
 
 > [!div class="checklist"]
->
-> - Set up a service principal.
 > - Create an Azure Key Vault instance.
-> - Register an application in Azure AD. 
 > - Set up the Verifiable Credentials service.
+> - Register an application in Azure AD.
+
 
 The following diagram illustrates the Azure AD Verifiable Credentials architecture and the component you configure.
 
@@ -68,6 +67,29 @@ A Key Vault [access policy](../../key-vault/general/assign-access-policy.md) def
 
 1. To save the changes, select **Save**.
 
+## Set up Verifiable Credentials 
+
+To set up Azure AD Verifiable Credentials, follow these steps:
+
+1. In the [Azure portal](https://portal.azure.com/), search for *verifiable credentials*. Then, select **Verifiable Credentials (Preview)**.
+
+1. From the left menu, select **Getting started**.
+
+1. Set up your organization by providing the following information:
+
+    1. **Organization name**: Enter a name to reference your business within Verifiable Credentials. Your customers don't see this name.
+
+    1. **Domain**: Enter a domain that's added to a service endpoint in your decentralized identity (DID) document. The domain is what binds your DID to something tangible that the user might know about your business. Microsoft Authenticator and other digital wallets use this information to validate that your DID is linked to your domain. If the wallet can verify the DID, it displays a verified symbol. If the wallet can't verify the DID, it informs the user that the credential was issued by an organization it couldn't validate.
+            
+        >[!IMPORTANT]
+        > The domain can't be a redirect. Otherwise, the DID and domain can't be linked. Make sure to use HTTPS for the domain. For example: `https://contoso.com`.
+
+    1. **Key vault**: Enter the name of the key vault that you created earlier.
+
+1. Select **Save and create credential**.  
+    
+    ![Screenshots that shows how to set up Verifiable Credentials.](media/verifiable-credentials-configure-tenant/verifiable-credentials-getting-started.png)
+
 ## Register an application in Azure AD
 
 Azure AD Verifiable Credentials Request Service needs to be able to get access tokens to issue and verify. To get access tokens, register a web application and grant API permission for the API Verifiable Credential Request Service that you set up in the previous step.
@@ -112,28 +134,6 @@ To add the required permissions, follow these steps:
 
 1. Select **Grant admin consent for \<your tenant name\>**.
 
-## Set up Verifiable Credentials 
-
-To set up Azure AD Verifiable Credentials, follow these steps:
-
-1. In the [Azure portal](https://portal.azure.com/), search for *verifiable credentials*. Then, select **Verifiable Credentials (Preview)**.
-
-1. From the left menu, select **Getting started**.
-
-1. Set up your organization by providing the following information:
-
-    1. **Organization name**: Enter a name to reference your business within Verifiable Credentials. Your customers don't see this name.
-
-    1. **Domain**: Enter a domain that's added to a service endpoint in your decentralized identity (DID) document. The domain is what binds your DID to something tangible that the user might know about your business. Microsoft Authenticator and other digital wallets use this information to validate that your DID is linked to your domain. If the wallet can verify the DID, it displays a verified symbol. If the wallet can't verify the DID, it informs the user that the credential was issued by an organization it couldn't validate.
-            
-        >[!IMPORTANT]
-        > The domain can't be a redirect. Otherwise, the DID and domain can't be linked. Make sure to use HTTPS for the domain. For example: `https://contoso.com`.
-
-    1. **Key vault**: Enter the name of the key vault that you created earlier.
-
-1. Select **Save and create credential**.  
-    
-    ![Screenshots that shows how to set up Verifiable Credentials.](media/verifiable-credentials-configure-tenant/verifiable-credentials-getting-started.png)
 
 ## Next steps
 

articles/aks/use-managed-identity.md

@@ -319,6 +319,57 @@ A successful cluster creation using your own kubelet managed identity contains t
   },
 ```
 
+### Update an existing cluster using kubelet identity (Preview)
+
+Update kubelet identity on an existing cluster with your existing identities. 
+
+#### Install the `aks-preview` Azure CLI
+
+You also need the *aks-preview* Azure CLI extension version 0.5.64 or later. Install the *aks-preview* Azure CLI extension by using the [az extension add][az-extension-add] command. Or install any available updates by using the [az extension update][az-extension-update] command.
+
+```azurecli-interactive
+# Install the aks-preview extension
+az extension add --name aks-preview
+
+# Update the extension to make sure you have the latest version installed
+az extension update --name aks-preview
+```
+#### Updating your cluster with kubelet identity (Preview)
+
+Now you can use the following command to update your cluster with your existing identities. Provide the control plane identity id via `assign-identity` and the kubelet managed identity via `assign-kubelet-identity`:
+
+```azurecli-interactive
+az aks update \
+    --resource-group myResourceGroup \
+    --name myManagedCluster \
+    --enable-managed-identity \
+    --assign-identity <identity-id> \
+    --assign-kubelet-identity <kubelet-identity-id>
+```
+
+A successful cluster update using your own kubelet managed identity contains the following output:
+
+```output
+  "identity": {
+    "principalId": null,
+    "tenantId": null,
+    "type": "UserAssigned",
+    "userAssignedIdentities": {
+      "/subscriptions/<subscriptionid>/resourcegroups/resourcegroups/providers/Microsoft.ManagedIdentity/userAssignedIdentities/myIdentity": {
+        "clientId": "<client-id>",
+        "principalId": "<principal-id>"
+      }
+    }
+  },
+  "identityProfile": {
+    "kubeletidentity": {
+      "clientId": "<client-id>",
+      "objectId": "<object-id>",
+      "resourceId": "/subscriptions/<subscriptionid>/resourcegroups/resourcegroups/providers/Microsoft.ManagedIdentity/userAssignedIdentities/myKubeletIdentity"
+    }
+  },
+```
+
 ## Next steps
 * Use [Azure Resource Manager templates ][aks-arm-template] to create Managed Identity enabled clusters.
 

articles/automation/update-management/deploy-updates.md

@@ -13,9 +13,8 @@ This article describes how to schedule an update deployment and review the proce
 
 Under each scenario, the deployment you create targets that selected machine or server, or in the case of creating a deployment from your Automation account, you can target one or more machines. When you schedule an update deployment from an Azure VM or Azure Arc-enabled server, the steps are the same as deploying from your Automation account, with the following exceptions:
 
-* The operating system is automatically pre-selected based on the OS of the machine
-* The target machine to update is set to target itself automatically
-* When configuring the schedule, you can specify **Update now**, occurs once, or uses a recurring schedule.
+* The operating system is automatically pre-selected based on the OS of the machine.
+* The target machine to update is set to target itself automatically.
 
 > [!IMPORTANT]
 > By creating an update deployment, you accept the terms of the Software License Terms (EULA) provided by the company offering updates for their operating system.
@@ -99,9 +98,6 @@ To schedule a new update deployment, perform the following steps. Depending on t
 
 9. Select **Schedule settings**. The default start time is 30 minutes after the current time. You can set the start time to any time from 10 minutes in the future.
 
-    > [!NOTE]
-    > This option is different if you selected an Azure Arc-enabled server. You can select **Update now** or a start time 20 minutes into the future.
-
 10. Use the **Recurrence** to specify if the deployment occurs once or uses a recurring schedule, then select **OK**.
 
 11. In the **Pre-scripts + Post-scripts** region, select the scripts to run before and after your deployment. To learn more, see [Manage pre-scripts and post-scripts](pre-post-scripts.md).

articles/azure-arc/data/release-notes.md

@@ -151,7 +151,7 @@ For complete release version information, see [Version log](version-log.md).
 
 - Support for readable secondary replicas:
     - To set readable secondary replicas use `--readable-secondaries` when you create or update an Arc-enabled SQL Managed Instance deployment. 
-    - Set `--readable secondaries` to any value between 0 and the number of replicas minus 1.
+    - Set `--readable-secondaries` to any value between 0 and the number of replicas minus 1.
     - `--readable-secondaries` only applies to Business Critical tier. 
 - Automatic backups are taken on the primary instance in a Business Critical service tier when there are multiple replicas. When a failover happens, backups move to the new primary. 
 - RWX capable storage class is required for backups, for both General Purpose and Business Critical service tiers.

articles/azure-monitor/usage-estimated-costs.md

@@ -22,7 +22,7 @@ Several other features don't have a direct cost, but you instead pay for the ing
 | Platform Logs | Processing of [diagnostic and auditing information](essentials/resource-logs.md) is charged for [certain services](essentials/resource-logs-categories.md#costs) when sent to destinations other than a Log Analytics workspace. There's no direct charge when this data is sent to a Log Analytics workspace, but there is a charge for the workspace data ingestion and collection. |
 | Metrics | There is no charge for [standard metrics](essentials/metrics-supported.md) collected from Azure resources. There is a cost for cost for collecting [custom metrics](essentials/metrics-custom-overview.md) and for retrieving metrics from the [REST API](essentials/rest-api-walkthrough.md#retrieve-metric-values). |
 | Alerts | Charged based on the type and number of [signals](alerts/alerts-overview.md#what-you-can-alert-on) used by the alert rule, its frequency, and the type of [notification](alerts/action-groups.md) used in response. For [log alerts](alerts/alerts-unified-log.md) configured for [at scale monitoring](alerts/alerts-unified-log.md#split-by-alert-dimensions), the cost will also depend on the number of time series created by the dimensions resulting from your query. |
-| Web tests | There is a cost for [multi-step web tests](app/availability-multistep.md) in Application Insights, but this feature has been deprecated.
+| Web tests | There is a cost for [standard web tests](app/availability-standard-tests.md) and [multi-step web tests](app/availability-multistep.md) in Application Insights. Multi-step web tests have been deprecated.
 
 ## Data transfer charges 
 Sending data to Azure Monitor can incur data bandwidth charges. As described in the [Azure Bandwidth pricing page](https://azure.microsoft.com/pricing/details/bandwidth/), data transfer between Azure services located in two regions charged as outbound data transfer at the normal rate, although data sent to a different region via [Diagnostic Settings](essentials/diagnostic-settings.md) does not incur data transfer charges. Inbound data transfer is free. Data transfer charges are typically very small compared to the costs for data ingestion and retention. Controlling costs for Log Analytics should focus on your ingested data volume.

articles/cognitive-services/Speech-Service/how-to-custom-voice-prepare-data.md

@@ -64,14 +64,14 @@ To produce a good voice model, create the recordings in a quiet room with a high
 
 ### Audio files
 
-Each audio file should contain a single utterance (a single sentence or a single turn of a dialog system), less than 15 seconds long. All files must be in the same spoken language. Multi-language custom Text-to-Speech voices aren't supported, with the exception of the Chinese-English bi-lingual. Each audio file must have a unique numeric filename with the filename extension .wav.
+Each audio file should contain a single utterance (a single sentence or a single turn of a dialog system), less than 15 seconds long. All files must be in the same spoken language. Multi-language custom Text-to-Speech voices aren't supported, with the exception of the Chinese-English bi-lingual. Each audio file must have a unique filename with the filename extension .wav.
 
 Follow these guidelines when preparing audio.
 
 | Property | Value |
 | -------- | ----- |
 | File format | RIFF (.wav), grouped into a .zip file |
-| File name | Numeric, with .wav extension. No duplicate file names allowed. |
+| File name | File name characters supported by Windows OS, with .wav extension.<br>The characters \ / : * ? " < > \| aren't allowed. <br>It can't start or end with a space, and can't start with a dot. <br>No duplicate file names allowed. |
 | Sampling rate	| For creating a custom neural voice, 24,000 Hz is required. |
 | Sample format | PCM, at least 16-bit |
 | Audio length | Shorter than 15 seconds |
@@ -115,7 +115,7 @@ Follow these guidelines when preparing audio for segmentation.
 | Property | Value |
 | -------- | ----- |
 | File format | RIFF (.wav) or .mp3, grouped into a .zip file |
-| File name	| ASCII and Unicode characters supported. No duplicate names allowed. |
+| File name	|  File name characters supported by Windows OS, with .wav extension. <br>The characters \ / : * ? " < > \| aren't allowed. <br>It can't start or end with a space, and can't start with a dot. <br>No duplicate file names allowed. |
 | Sampling rate	| For creating a custom neural voice, 24,000 Hz is required. |
 | Sample format |RIFF(.wav): PCM, at least 16-bit<br>mp3: at least 256 KBps bit rate|
 | Audio length | Longer than 20 seconds |
@@ -155,7 +155,7 @@ Follow these guidelines when preparing audio.
 | Property | Value |
 | -------- | ----- |
 | File format | RIFF (.wav) or .mp3, grouped into a .zip file |
-| File name | ASCII and Unicode characters supported. No duplicate name allowed. |
+| File name |  File name characters supported by Windows OS, with .wav extension. <br>The characters \ / : * ? " < > \| aren't allowed. <br>It can't start or end with a space, and can't start with a dot. <br>No duplicate file names allowed. |
 | Sampling rate	| For creating a custom neural voice, 24,000 Hz is required. |
 | Sample format |RIFF(.wav): PCM, at least 16-bit<br>mp3: at least 256 KBps bit rate|
 | Audio length | No limit |

articles/cognitive-services/Speech-Service/includes/release-notes/release-notes-tts.md

@@ -5,6 +5,16 @@ ms.topic: include
 ms.date: 01/24/2022
 ms.author: eur
 ---
+### 2022-May release
+
+#### Prebuilt Neural TTS Voice
+
+* Released 5 new voices in public preview with multiple styles to enrich the variety in American English. See [full language and voice list](../../language-support.md#prebuilt-neural-voices).
+
+* Support these new styles `Angry`, `Excited`, `Friendly`, `Hopeful`, `Sad`, `Shouting`, `Unfriendly`, `Terrified` and `Whispering` in public preview for `en-US-AriaNeural`. 
+* Support these new styles `Angry`, `Cheerful`, `Excited`, `Friendly`, `Hopeful`, `Sad`, `Shouting`, `Unfriendly`, `Terrified` and `Whispering` in public preview for `en-US-GuyNeural`, `en-US-JennyNeural`. 
+* Support these new styles `Excited`, `Friendly`, `Hopeful`, `Shouting`, `Unfriendly`, `Terrified` and `Whispering` in public preview for `en-US-SaraNeural`. See [voice styles and roles](../../language-support.md#voice-styles-and-roles).
+* Released disconnected containers for prebuilt neural TTS voices in public preview. See [use Docker containers in disconnected environments](../../../containers/disconnected-containers.md).
 
 ### 2022-March release