Skip to content

Commit 4cdc3a3

Browse files
committed
fix image paths
1 parent bb2191e commit 4cdc3a3

File tree

2 files changed

+3
-6
lines changed

2 files changed

+3
-6
lines changed

articles/azure-netapp-files/configure-customer-managed-keys-hardware.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -153,7 +153,7 @@ To use a system-assigned identity, the Azure Key Vault must be configured to use
153153
* Select the NetApp **Subscription**.
154154
* For **Identity type**, select **System-assigned**.
155155
156-
:::image type="content" source="./media/azure-netapp-files/key-enter-uri.png" alt-text="Screenshot of the encryption menu showing key URI field." lightbox="./media/azure-netapp-files/key-enter-uri.png":::
156+
:::image type="content" source="./media/configure-customer-managed-keys/key-enter-uri.png" alt-text="Screenshot of the encryption menu showing key URI field." lightbox="./media/configure-customer-managed-keys//key-enter-uri.png":::
157157
158158
1. Select **Save**.
159159
@@ -173,7 +173,7 @@ To use a system-assigned identity, the Azure Key Vault must be configured to use
173173
* "Microsoft.KeyVault/vaults/keys/decrypt/action"
174174
The user-assigned identity you select is added to your NetApp account. Due to RBAC being customizable, the Azure portal doesn't configure access to the key vault. For more information, see [Using Azure RBAC secret, key, and certificate permissions with Key Vault](../key-vault/general/rbac-guide.md#using-azure-rbac-secret-key-and-certificate-permissions-with-key-vault)
175175
176-
:::image type="content" source="./media/azure-netapp-files/encryption-user-assigned.png" alt-text="Screenshot of user-assigned submenu." lightbox="./media/azure-netapp-files/encryption-user-assigned.png":::
176+
:::image type="content" source="./media/configure-customer-managed-keys/encryption-user-assigned.png" alt-text="Screenshot of user-assigned submenu." lightbox="./media/configure-customer-managed-keys/encryption-user-assigned.png":::
177177
178178
1. Select **Save**.
179179

articles/azure-netapp-files/whats-new.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,12 +14,10 @@ ms.author: anfdocs
1414

1515
Azure NetApp Files is updated regularly. This article provides a summary about the latest new features and enhancements.
1616

17-
<<<<<<< HEAD
18-
* [Volume encryption with customer-managed keys with managed ardware Security Module (HSM)](configure-customer-managed-keys-hardware.md) (Preview)
17+
* [Volume encryption with customer-managed keys with managed Hardware Security Module (HSM)](configure-customer-managed-keys-hardware.md) (Preview)
1918

2019
Volume encryption with customer-managed keys with managed HSM extends the [customer-managed keys](configure-customer-managed-keys.md), enabling you to store your keys in a more secure FIPS 140-2 Level 3 HSM service instead of the FIPS 140-2 Level 1 or 2 encryption offered with Azure Key Vault.
2120

22-
=======
2321
## April 2024
2422

2523
* [Application volume group for Oracle](application-volume-group-oracle-introduction.md) (Preview)
@@ -32,7 +30,6 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
3230

3331
Application volume group for Oracle is supported in all Azure NetApp Files-enabled regions.
3432

35-
>>>>>>> a25a70ebd7353d631242f79fd206eb8344fc9187
3633
## March 2024
3734

3835
* [Large volumes (Preview) improvement:](large-volumes-requirements-considerations.md) new minimum size of 50 TiB

0 commit comments

Comments
 (0)