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

Author: asudbring

articles/aks/use-azure-linux.md

@@ -4,7 +4,7 @@ title: Use the Azure Linux container host on Azure Kubernetes Service (AKS)
 description: Learn how to use the Azure Linux container host on Azure Kubernetes Service (AKS)
 ms.topic: article
 ms.custom: build-2023
-ms.date: 09/18/2023
+ms.date: 02/27/2024
 ---
 
 # Use the Azure Linux container host for Azure Kubernetes Service (AKS)
@@ -53,7 +53,7 @@ The Azure Linux container host is available for use in the same regions as AKS.
 To learn more about Azure Linux, see the [Azure Linux documentation][azurelinuxdocumentation].
 
 <!-- LINKS - Internal -->
-[azurelinux-doc]: https://microsoft.github.io/CBL-Mariner/docs/#cbl-mariner-linux
+[azurelinux-doc]: ../azure-linux/intro-azure-linux.md
 [azurelinux-capabilities]: ../azure-linux/intro-azure-linux.md#azure-linux-container-host-key-benefits
 [azurelinux-cluster-config]: cluster-configuration.md#azure-linux-container-host-for-aks
 [azurelinux-node-pool]: create-node-pools.md#add-an-azure-linux-node-pool

articles/communication-services/how-tos/calling-sdk/includes/record-calls/record-calls-web.md

@@ -40,13 +40,13 @@ const isRecordingActiveChangedHandler = () => {
 callRecordingApi.on('isRecordingActiveChanged', isRecordingActiveChangedHandler);
 ```
 
-You can get a list of recordings by using the `recordings` property of `callRecordingApi`. It returns `RecordingInfo[]`, which has the display name of the user and the current state of the cloud recording.
+You can get a list of recordings by using the `recordings` property of `callRecordingApi`. It returns `RecordingInfo[]`, which has the current state of the cloud recording.
 
 ```js
 const recordings = callRecordingApi.recordings;
 
 recordings.forEach(r => {
-    console.log("User: ${r.displayName}, State: ${r.state}");
+    console.log("State: ${r.state}");
 ```
 
 You can also subscribe to `recordingsUpdated` and get a collection of updated recordings. This event is triggered whenever there's a recording update.
@@ -55,12 +55,12 @@ You can also subscribe to `recordingsUpdated` and get a collection of updated re
 const cloudRecordingsUpdatedHandler = (args: { added: SDK.RecordingInfo[], removed: SDK.RecordingInfo[]}) => {
                         console.log('Recording started by: ');
                         args.added?.forEach(a => {
-                            console.log('User: ${a.displayName}');
+                            console.log('State: ${a.state}');
                         });
 
                         console.log('Recording stopped by: ');
                         args.removed?.forEach(r => {
-                            console.log('User: ${r.displayName}');
+                            console.log('State: ${r.state}');
                         });
                     };
 callRecordingApi.on('recordingsUpdated', cloudRecordingsUpdatedHandler );

includes/virtual-machines-managed-disks-customer-managed-keys-restrictions.md

@@ -4,15 +4,17 @@
  author: roygara
  ms.service: azure-disk-storage
  ms.topic: include
- ms.date: 02/22/2023
+ ms.date: 02/28/2024
  ms.author: rogarana
  ms.custom: include file
 ---
 - If this feature is enabled for a disk with incremental snapshots, it can't be disabled on that disk or its snapshots.
     To work around this, copy all the data to an entirely different managed disk that isn't using customer-managed keys. You can do that with either the [Azure CLI](../articles/virtual-machines/linux/disks-upload-vhd-to-managed-disk-cli.md#copy-a-managed-disk) or the [Azure PowerShell module](../articles/virtual-machines/windows/disks-upload-vhd-to-managed-disk-powershell.md#copy-a-managed-disk).
 - Only [software and HSM RSA keys](../articles/key-vault/keys/about-keys.md) of sizes 2,048-bit, 3,072-bit and 4,096-bit are supported, no other keys or sizes.
     - [HSM](../articles/key-vault/keys/hsm-protected-keys.md) keys require the **premium** tier of Azure Key vaults.
-- For Ultra Disks and Premium SSD v2 disks only: Snapshots created from disks that are encrypted with server-side encryption and customer-managed keys must be encrypted with the same customer-managed keys.
+- For Ultra Disks and Premium SSD v2 disks only:
+    - Snapshots created from disks that are encrypted with server-side encryption and customer-managed keys must be encrypted with the same customer-managed keys.
+    - User-assigned managed identities aren't supported for Ultra Disks and Premium SSD v2 disks encrypted with customer-managed keys.
 - Most resources related to your customer-managed keys (disk encryption sets, VMs, disks, and snapshots) must be in the same subscription and region.
     - Azure Key Vaults may be used from a different subscription but must be in the same region as your disk encryption set. As a preview, you can use Azure Key Vaults from [different Microsoft Entra tenants](../articles/virtual-machines/disks-cross-tenant-customer-managed-keys.md).
 - Disks encrypted with customer-managed keys can only move to another resource group if the VM they are attached to is deallocated.