fix powershell commands. fix links

Author: b-ahibbard

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

@@ -38,15 +38,14 @@ The following diagram demonstrates how customer-managed keys work with Azure Net
 * Customer-managed keys can only be configured on new volumes. You can't migrate existing volumes to customer-managed key encryption.
 * To create a volume using customer-managed keys, you must select the *Standard* network features. You can't use customer-managed key volumes with volume configured using Basic network features. Follow instructions in to [Set the Network Features option](configure-network-features.md#set-the-network-features-option) in the volume creation page.
 * For increased security, you can select the **Disable public access** option within the network settings of your key vault. When selecting this option, you must also select **Allow trusted Microsoft services to bypass this firewall** to permit the Azure NetApp Files service to access your encryption key.
-* Automatic Managed System Identity (MSI) certificate renewal isn't currently supported. It is recommended to set up an Azure monitor alert for when the MSI certificate is going to expire.
+* Automatic Managed System Identity (MSI) certificate renewal isn't currently supported. It's recommended you create an Azure monitor alert to notify you when the MSI certificate is set to expire.
 * The MSI certificate has a lifetime of 90 days. It becomes eligible for renewal after 46 days. **After 90 days, the certificate is no longer be valid and the customer-managed key volumes under the NetApp account will go offline.**
     * To renew, you need to call the NetApp account operation `renewCredentials` if eligible for renewal. If it's not eligible, an error message communicates the date of eligibility.
     * Version 2.42 or later of the Azure CLI supports running the `renewCredentials` operation with the [az netappfiles account command](/cli/azure/netappfiles/account#az-netappfiles-account-renew-credentials). For example:
 
     `az netappfiles account renew-credentials –-account-name myaccount –resource-group myresourcegroup`
 
     * If the account isn't eligible for MSI certificate renewal, an error message communicates the date and time when the account is eligible. It's recommended you run this operation periodically (for example, daily) to prevent the certificate from expiring and from the customer-managed key volume going offline.
-*  If you are using the CLI or PowerShell, you must take additional steps to enable access from the NetApp account to the customer-managed keys.
 * Applying Azure network security groups on the private link subnet to Azure Key Vault isn't supported for Azure NetApp Files customer-managed keys. Network security groups don't affect connectivity to Private Link unless `Private endpoint network policy` is enabled on the subnet. It's recommended to keep this option disabled.
 * If Azure NetApp Files fails to create a customer-managed key volume, error messages are displayed. Refer to the [Error messages and troubleshooting](#error-messages-and-troubleshooting) section for more information.
 * If Azure Key Vault becomes inaccessible, Azure NetApp Files loses its access to the encryption keys and the ability to read or write data to volumes enabled with customer-managed keys. In this situation, create a support ticket to have access manually restored for the affected volumes.
@@ -99,7 +98,7 @@ Azure NetApp Files customer-managed keys is supported for the following regions:
 
 ## Requirements
 
-Before creating your first customer-managed key volume, you must have set up:
+Before creating your first customer-managed key volume, you must set up:
 * An [Azure Key Vault](../key-vault/general/overview.md), containing at least one key.
     * The key vault must have soft delete and purge protection enabled.
     * The key must be of type RSA.
@@ -183,18 +182,18 @@ The process to configure a NetApp account with customer-managed keys in the Azur
 
 1. Update the NetApp account with your key vault. 
 
-```azurecli
-key_vault_uri=$(az keyvault show \
-    --name <key-vault> \
-    --resource-group <resource_group> \
-    --query properties.vaultUri \
-    --output tsv)
-az netappfiles account update --name <account_name> \  
-    --resource-group <resource_group> \
-    --key-source Microsoft.Keyvault \
-    --key-vault-uri $key_vault_uri \
-    --key-name <key>
-```
+    ```azurecli
+    key_vault_uri=$(az keyvault show \
+        --name <key-vault> \
+        --resource-group <resource_group> \
+        --query properties.vaultUri \
+        --output tsv)
+    az netappfiles account update --name <account_name> \  
+        --resource-group <resource_group> \
+        --key-source Microsoft.Keyvault \
+        --key-vault-uri $key_vault_uri \
+        --key-name <key>
+    ```
 
 #### Use a new user-assigned identity 
 
@@ -219,109 +218,91 @@ az netappfiles account update --name <account_name> \
         --object-id $user_assigned_identity_principal \
         --key-permissions get encrypt decrypt
     ```
-
->[!NOTE]
->You can alternately [use role-based access control to grant access to the key vault](#use-role-based-access-control). 
+    
+    >[!NOTE]
+    >You can alternately [use role-based access control to grant access to the key vault](#use-role-based-access-control). 
 
 1. Assign the user-assigned identity to the NetApp account and update the key vault encryption. 
 
-```azurecli
-key_vault_uri=$(az keyvault show \
-    --name <key-vault> \
-    --resource-group <resource_group> \
-    --query properties.vaultUri \
-    --output tsv)
-user_assigned_identity=$(az identity show \
-    --name <identity_name> \
-    --resource-group <resource_group> \
-    --query id \
-    -output tsv)
-az netappfiles account update --name <account_name> \  
-    --resource-group <resource_group> \
-    --identity-type UserAssigned \
-    --user-identity-id $user-assigned-identity \   
-    --key-source Microsoft.Keyvault \
-    --key-vault-uri $key_vault_uri \
-    --key-name <key> \
-    --keyvault-resource-id <key-vault> \   
-    --user-assigned-identity $user_assigned_identity
- ```
+    ```azurecli
+    key_vault_uri=$(az keyvault show \
+        --name <key-vault> \
+        --resource-group <resource_group> \
+        --query properties.vaultUri \
+        --output tsv)
+    user_assigned_identity=$(az identity show \
+        --name <identity_name> \
+        --resource-group <resource_group> \
+        --query id \
+        -output tsv)
+    az netappfiles account update --name <account_name> \  
+        --resource-group <resource_group> \
+        --identity-type UserAssigned \
+        --user-identity-id $user-assigned-identity \   
+        --key-source Microsoft.Keyvault \
+        --key-vault-uri $key_vault_uri \
+        --key-name <key> \
+        --keyvault-resource-id <key-vault> \   
+        --user-assigned-identity $user_assigned_identity
+     ```
 
 ### [Azure PowerShell](#tab/azure-powershell)
 
-The process to configure a NetApp account with customer-managed keys in the Azure CLI depends on whether you are using a [system-assigned identity](#enable-access-for-system-assigned-identity) or an [user-assigned identity](#enable-access-for-user-assigned-identityy).
+The process to configure a NetApp account with customer-managed keys in the Azure CLI depends on whether you are using a [system-assigned identity](#enable-access-for-system-assigned-identity) or an [user-assigned identity](#enable-access-for-user-assigned-identity).
 
 #### Enable access for system-assigned identity 
 
 1. Update your NetApp account to use system-assigned identity.
 
-```azurepowershell
-$netappAccount = Update-AzNetAppFilesAccount -ResourceGroupName <resource_group> -Name <account_name> -AssignIdentity
-```
+    ```azurepowershell
+    $netappAccount = Update-AzNetAppFilesAccount -ResourceGroupName <resource_group> -Name <account_name> -AssignIdentity
+    ```
 
 1. To use an access policy, run `Set-AzKeyVaultAccessPolicy` with the key vault name, the principal ID of the account identity, and the permissions "Get", "Encrypt", and "Decrypt". 
 
-```azurepowershell
-Set-AzKeyVaultAccessPolicy -VaultName <key_vault_name> -ResourceGroupname <resource_group> -ObjectId $netappAccount.Identity.PrincipalId -PermissionsToKeys get,encrypt,decrypt
-```
+    ```azurepowershell
+    Set-AzKeyVaultAccessPolicy -VaultName <key_vault_name> -ResourceGroupname <resource_group> -ObjectId $netappAccount.Identity.PrincipalId -PermissionsToKeys get,encrypt,decrypt
+    ```
 
 1. Update your NetApp account with the key vault information.
 
-```azurepowershell
-Update-AzNetAppFilesAccount -ResourceGroupName $netappAccount.ResourceGroupName -AccountName $netappAccount.ResourceGroupName   -KeyVaultEncryption -KeyVaultUri <keyVaultUri> -KeyName <keyName>
-```
+    ```azurepowershell
+    Update-AzNetAppFilesAccount -ResourceGroupName $netappAccount.ResourceGroupName -AccountName $netappAccount.ResourceGroupName   -KeyVaultEncryption -KeyVaultUri <keyVaultUri> -KeyName <keyName>
+    ```
 
 #### Enable access for user-assigned identity
 
 1. Create a new user-assigned identity.
 
-```azurepowershell
-az identity create \
-    --name <identity_name> \
-    --resource-group <resource_group>
-```
+    ```azurepowershell
+    $userId = New-AzUserAssignedIdentity -ResourceGroupName <resourceGroupName> -Name $userIdName
+    ```
 
 1. Assign the access policy to the key vault. 
 
-```azurepowershell
-user_assigned_identity_principal=$(az identity show \
-    --name <identity_name> \
-    --resource-group <resource_group> \
-    --query properties.principalId \
-    -output tsv)
-az keyvault set-policy \
-    --name <key_vault_name> \
-    --resource-group <resource-group> \
-    --object-id $user_assigned_identity_principal \
-    --key-permissions get encrypt decrypt
-```
-
->[!NOTE]
->You can alternately [use role-based access control to grant access to the key vault](#use-role-based-access-control). 
+    ```azurepowershell
+    Set-AzKeyVaultAccessPolicy -VaultName <key_vault_name> `
+        -ResourceGroupname <resource_group> `
+        -ObjectId $userId.PrincipalId `
+        -PermissionsToKeys get,encrypt,decrypt `
+        -BypassObjectIdValidation
+    ```
+    
+    >[!NOTE]
+    >You can alternately [use role-based access control to grant access to the key vault](#use-role-based-access-control). 
 
 1. Assign the user-assigned identity to the NetApp account and update the key vault encryption. 
 
-```azurepowershell
-key_vault_uri=$(az keyvault show \
-    --name <key-vault> \
-    --resource-group <resource_group> \
-    --query properties.vaultUri \
-    --output tsv)
-user_assigned_identity=$(az identity show \
-    --name <identity_name> \
-    --resource-group <resource_group> \
-    --query id \
-    -output tsv)
-az netappfiles account update --name <storage-account> \
-    --resource-group <resource_group> \
-    --identity-type UserAssigned \
-    --user-identity-id $user_assigned_identity \
-    --key-source Microsoft.Keyvault \
-    --key-vault-uri $key_vault_uri \
-    --key-name <key> \
-    --keyvault-resource-id <key-vault> \   
-    --user-assigned-identity $user_assigned_identity
-```
+    ```azurepowershell
+    $netappAccount = Update-AzNetAppFilesAccount -ResourceGroupName <resource_group> `
+        -Name <account_name> `
+        -IdentityType UserAssigned `
+        -UserAssignedIdentityId $userId.Id `
+        -KeyVaultEncryption `
+        -KeyVaultUri <keyVaultUri> `
+        -KeyName <keyName> `
+        -EncryptionUserAssignedIdentity $userId.Id
+    ```
 
 ## Use role-based access control