Skip to content

Commit edd846c

Browse files
authored
Merge pull request #291191 from MicrosoftDocs/main
11/28/2024 AM Publish
2 parents 402d445 + 7877f1b commit edd846c

File tree

3 files changed

+11
-7
lines changed

3 files changed

+11
-7
lines changed

articles/backup/encryption-at-rest-with-cmk-for-backup-vault.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Encrypt backup data in a Backup vault by using customer-managed keys
33
description: Learn how to use Azure Backup to encrypt your backup data by using customer-managed keys (CMKs) in a Backup vault.
44
ms.topic: how-to
5-
ms.date: 11/20/2024
5+
ms.date: 11/28/2024
66
ms.custom: references_regions, devx-track-azurepowershell-azurecli
77
ms.service: azure-backup
88
author: AbhishekMallick-MS
@@ -258,7 +258,7 @@ To assign a user-assigned managed identity for your Backup vault, follow these s
258258

259259
6. Select **Add** to finish assigning the identity.
260260

261-
:::image type="content" source="./media/encryption-at-rest-with-cmk-for-backup-vault/assign-user-assigned-managed-identity-to-vault.png" alt-text="Screenshot that shows selections for assigning a user-assigned managed identity to a vault." lightbox="./media/encryption-at-rest-with-cmk-for-backup-vault/assign-user-assigned-managed-identity-to-vault.png":::
261+
:::image type="content" source="./media/encryption-at-rest-with-cmk-for-backup-vault/add-user-assigned-managed-identity.png" alt-text="Screenshot that shows selections for assigning a user-assigned managed identity to a vault." lightbox="./media/encryption-at-rest-with-cmk-for-backup-vault/add-user-assigned-managed-identity.png":::
262262

263263
> [!NOTE]
264264
> Key vaults that limit access to specific networks aren't yet supported for use with user-assigned managed identities for CMK encryption.
@@ -444,6 +444,10 @@ To assign the key, follow these steps:
444444

445445
When you try to update encryption settings but the update operation fails because of an internal error, the encryption setting is updated to **Inconsistent** and requires your attention. In such cases, check your encryption settings details, ensure that they are correct. For example, the **Update Encryption Settings** operation runs again with the existing Managed Identity attached to the vault. If the encryption settings details are same, the update operation is not affected.
446446

447+
Also if you disable or detach the managed identity being used in Encryption Settings, the Encryption Settings would change to ‘Inconsistent’ state unless you re-enable system assign identity(if it was used), grant the required Key Vault permissions and perform Encryption Settings update operation again. For User Assigned Identity, when you re-attach the identity, Encryption Settings state will be automatically be restored if the Key Vault permissions are there.
448+
449+
450+
447451
:::image type="content" source="./media/encryption-at-rest-with-cmk-for-backup-vault/key-uri.png" alt-text="Screenshot that shows the status warning for a failed update." lightbox="./media/encryption-at-rest-with-cmk-for-backup-vault/key-uri.png":::
448452

449453
When you're specifying the encryption key by using the full key URI with the version component, the key won't be autorotated. You need to update keys manually by specifying the new key or version when required. Alternatively, remove the version component of the key URI to get automatic key version rotation.
@@ -454,7 +458,7 @@ To assign the key, follow these steps:
454458

455459
:::image type="content" source="./media/encryption-at-rest-with-cmk-for-backup-vault/key-vault-encryption.png" alt-text="Screenshot that shows the option for selecting a key from a key vault." lightbox="./media/encryption-at-rest-with-cmk-for-backup-vault/key-vault-encryption.png":::
456460

457-
When you specify the encryption key by using the **Key picker** pane, the key will be autorotated whenever a new version for the key is enabled. [Learn more about enabling autorotation of encryption keys](encryption-at-rest-with-cmk.md#enable-autorotation-of-encryption-keys).
461+
When you specify the encryption key by using the **Key picker** pane, the key version will be autorotated whenever a new version for the key is enabled. [Learn more about enabling autorotation of encryption keys](encryption-at-rest-with-cmk.md#enable-autorotation-of-encryption-keys).
458462

459463
4. Select **Update**.
460464

articles/backup/tutorial-sap-hana-manage-cli.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: 'Tutorial: Manage backed-up SAP HANA DB using CLI'
33
description: In this tutorial, learn how to manage backed-up SAP HANA databases running on an Azure VM using Azure CLI.
44
ms.topic: tutorial
5-
ms.date: 08/11/2022
5+
ms.date: 10/20/2024
66
ms.custom: devx-track-azurecli
77
author: AbhishekMallick-MS
88
ms.author: v-abhmallick

articles/iot-operations/connect-to-cloud/tutorial-mqtt-bridge.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: patricka
66
ms.service: azure-iot-operations
77
ms.subservice: azure-data-flows
88
ms.topic: tutorial
9-
ms.date: 11/11/2024
9+
ms.date: 11/25/2024
1010

1111
#CustomerIntent: As an operator, I want to understand how to create a bi-directional MQTT bridge to Azure Event Grid so that I can send and receive messages between devices and services.
1212
---
@@ -372,7 +372,7 @@ resource dataflow_1 'Microsoft.IoTOperations/instances/dataflowProfiles/dataflow
372372
{
373373
operationType: 'Destination'
374374
destinationSettings: {
375-
endpointRef: remoteMqttBrokerDataflowEndpoint.name
375+
endpointRef: 'eventgrid'
376376
dataDestination: 'telemetry/aio'
377377
}
378378
}
@@ -392,7 +392,7 @@ resource dataflow_2 'Microsoft.IoTOperations/instances/dataflowProfiles/dataflow
392392
{
393393
operationType: 'Source'
394394
sourceSettings: {
395-
endpointRef: remoteMqttBrokerDataflowEndpoint.name
395+
endpointRef: 'eventgrid'
396396
dataSources: array('telemetry/#')
397397
}
398398
}

0 commit comments

Comments
 (0)