new screenshots & ui, resolve blockers

Author: ekpgh

articles/hpc-cache/configuration.md

@@ -4,8 +4,8 @@ description: Explains how to configure additional settings for the cache like MT
 author: ekpgh
 ms.service: hpc-cache
 ms.topic: conceptual
-ms.date: 03/20/2020
-ms.author: rohogue
+ms.date: 04/15/2020
+ms.author: v-erkel
 ---
 
 # Configure additional Azure HPC Cache settings
@@ -16,7 +16,7 @@ This article also describes how to use the snapshot feature for Azure Blob stora
 
 To see the settings, open the cache's **Configuration** page in the Azure portal.
 
-![screenshot of configuration page in Azure portal](media/draft-configuration.png)
+![screenshot of configuration page in Azure portal](media/configuration.png)
 
 ## Adjust MTU value
 <!-- linked from troubleshoot-nas article -->

articles/hpc-cache/customer-keys.md

@@ -4,8 +4,8 @@ description: How to use Azure Key Vault with Azure HPC Cache to control encrypti
 author: ekpgh
 ms.service: hpc-cache
 ms.topic: conceptual
-ms.date: 04/06/2020
-ms.author: rohogue
+ms.date: 04/15/2020
+ms.author: v-erkel
 ---
 
 # Use customer-managed encryption keys for Azure HPC Cache
@@ -77,7 +77,7 @@ You must specify the encryption key source when you create your Azure HPC Cache.
 
 The user who creates the cache must have privileges equal to the [Key Vault contributor role](../role-based-access-control/built-in-roles.md#key-vault-contributor) or higher.
 
-1. Click the button to enable privately managed keys. After you change this setting, the key vault settings appear. <!-- double check if this is true -->
+1. Click the button to enable privately managed keys. After you change this setting, the key vault settings appear.
 
 1. Click **Select a key vault** to open the key selection page. Choose or create the key vault and key for encrypting data on this cache's disks.
 
@@ -96,7 +96,7 @@ Continue with the rest of the specifications and create the cache as described i
 ## 3. Authorize Azure Key Vault encryption from the cache
 <!-- header is linked from create article, update if changed -->
 
-After a few minutes, the new Azure HPC Cache appears in your Azure portal. Go to the **Overview** page to authorize it to access your Azure Key Vault and enable customer-managed key encryption.
+After a few minutes, the new Azure HPC Cache appears in your Azure portal. Go to the **Overview** page to authorize it to access your Azure Key Vault and enable customer-managed key encryption. (The cache might appear in the resources list before the "deployment underway" messages clear.)
 
 This two-step process is necessary because the Azure HPC Cache instance needs an identity to pass to the Azure Key Vault for authorization. The cache identity doesn't exist until after its initial creation steps are complete.
 
@@ -105,11 +105,11 @@ This two-step process is necessary because the Azure HPC Cache instance needs an
 
 The cache shows the status **Waiting for key**. Click the **Enable encryption** button at the top of the page to authorize the cache to access the specified key vault.
 
-![screenshot of cache overview page in portal, with a banner message at the top that asks the user to enable encryption by clicking yes](media/draft-enable-keyvault.png)
+![screenshot of cache overview page in portal, with highlighting on the Enable encryption button (top row) and Status: Waiting for key](media/waiting-for-key.png)
 
-Click the **Yes** button to authorize the cache to use the encryption key. This action also enables soft-delete and purge protection (if not already enabled) on the key vault.<!-- xxx problem? xxx -->
+Click **Enable encryption** and then click the **Yes** button to authorize the cache to use the encryption key. This action also enables soft-delete and purge protection (if not already enabled) on the key vault.
 
-![screenshot of cache overview page in portal, with a banner message at the top that asks the user to enable encryption by clicking yes](media/draft-enable-keyvault-banner.png)
+![screenshot of cache overview page in portal, with a banner message at the top that asks the user to enable encryption by clicking yes](media/enable-keyvault.png)
 
 After the cache requests access to the key vault, it can create and encrypt the disks that store cached data.
 
@@ -119,17 +119,17 @@ After you authorize encryption, Azure HPC Cache goes through several more minute
 
 You can change the key vault, key, or key version for your cache from the Azure portal. Click the cache's **Encryption** settings link to open the **Customer key settings** page. (You cannot change a cache between customer-managed keys and system-managed keys.)
 
-![screenshot of "Customer keys setting" page, reached by clicking Settings > Encryption from the cache overview page in the Azure portal](media/draft-customer-key-settings.png)
+![screenshot of "Customer keys settings" page, reached by clicking Settings > Encryption from the cache page in the Azure portal](media/change-key-click.png)
 
-Click the **Change key** link to open the key selector.
+Click the **Change key** link, then click **Change the key vault, key, or version** to open the key selector.
 
-![screenshot of "select key from Azure Key Vault" page with three drop-down selectors to choose key vault, key, and version](media/draft-select-new-key.png)
+![screenshot of "select key from Azure Key Vault" page with three drop-down selectors to choose key vault, key, and version](media/select-new-key.png)
 
 Key vaults in the same subscription and same region as this cache are shown in the list.
 
-After you choose the new encryption key values, click **Save**<!--not in screenshot - verify -->. A confirmation page appears with the new values. Click **Save** at the top of the confirmation page to finalize the selection.
+After you choose the new encryption key values, click **Select**. A confirmation page appears with the new values. Click **Save** to finalize the selection.
 
-![screenshot of confirmation page with Save button at top left](media/draft-save-new-key.png)
+![screenshot of confirmation page with Save button at top left](media/save-key-settings.png)
 
 ## Read more about customer-managed keys in Azure
 

articles/hpc-cache/hpc-cache-add-storage.md

@@ -113,8 +113,6 @@ Fill in these values for each namespace path:
 
 * **Virtual namespace path** - Set the client-facing file path for this storage target. Read [Configure aggregated namespace](hpc-cache-namespace.md) to learn more about the virtual namespace feature.
 
-<!--  The virtual path should start with a slash ``/``. -->
-
 * **NFS export path** - Enter the path to the NFS export.
 
 * **Subdirectory path** - If you want to mount a specific subdirectory of the export, enter it here. If not, leave this field blank.

articles/hpc-cache/hpc-cache-create.md

@@ -4,8 +4,8 @@ description: How to create an Azure HPC Cache instance
 author: ekpgh
 ms.service: hpc-cache
 ms.topic: how-to
-ms.date: 03/19/2020
-ms.author: rohogue
+ms.date: 04/15/2020
+ms.author: v-erkel
 ---
 
 # Create an Azure HPC Cache
@@ -62,10 +62,9 @@ You can skip this section if you do not need customer-managed keys. Azure encryp
 
 For a complete explanation of the customer-managed key encryption process, read [Use customer-managed encryption keys for Azure HPC Cache](customer-keys.md).
 
-![screenshot of encryption keys page with "customer managed" selected and key vault fields showing](media/draft-create-encryption.png)
+![screenshot of encryption keys page with "customer managed" selected and key vault fields showing](media/create-encryption.png)
 
-Select **Customer managed** to choose customer-managed key encryption. The key vault specification fields appear.<!-- double check --> Select the Azure Key Vault to use, then select the key and version to use for this cache. The key must be a 2048-bit RSA key. You can create a new key vault, key, or key version from this page.
-<!-- + screenshot of key create/select page -->
+Select **Customer managed** to choose customer-managed key encryption. The key vault specification fields appear. Select the Azure Key Vault to use, then select the key and version to use for this cache. The key must be a 2048-bit RSA key. You can create a new key vault, key, or key version from this page.
 
 After you create the cache, you must authorize it to use the key vault service. Read [Authorize Azure Key Vault encryption from the cache](customer-keys.md#3-authorize-azure-key-vault-encryption-from-the-cache) for details.
 
@@ -82,10 +81,12 @@ Cache creation takes about 10 minutes. You can track the progress in the Azure p
 ![screenshot of cache creation "deployment underway" and "notifications" pages in portal](media/hpc-cache-deploy-status.png)
 
 When creation finishes, a notification appears with a link to the new Azure HPC Cache instance, and the cache appears in your subscription's **Resources** list.
-<!-- double check on notification -->
 
 ![screenshot of Azure HPC Cache instance in Azure portal](media/hpc-cache-new-overview.png)
 
+> [!NOTE]
+> If your cache uses customer-managed encryption keys, the cache might appear in the resources list before the deployment status changes to complete. As soon as the cache's status is **Waiting for key** you can [authorize it](customer-keys.md#3-authorize-azure-key-vault-encryption-from-the-cache) to use the key vault.
+
 ## Next steps
 
 After your cache appears in the **Resources** list, you can move to the next step.

articles/hpc-cache/hpc-cache-ingest.md

@@ -16,7 +16,7 @@ This article explains the best ways to move data to Blob storage for use with Az
 
 Keep these facts in mind:
 
-* Azure HPC Cache uses a specialized storage format to organize data in Blob storage. This is why a Blob storage target must either be a new, empty container, or a Blob container that was previously used for Azure HPC Cache data. <!--([Avere vFXT for Azure](https://azure.microsoft.com/services/storage/avere-vfxt/) also uses this cloud file system.)-->
+* Azure HPC Cache uses a specialized storage format to organize data in Blob storage. This is why a Blob storage target must either be a new, empty container, or a Blob container that was previously used for Azure HPC Cache data.
 
 * Copying data through the Azure HPC Cache to a back-end storage target is more efficient when you use multiple clients and parallel operations. A simple copy command from one client will move data slowly.
 
@@ -26,13 +26,13 @@ If you don't want to use the loading utility, or if you want to add content to a
 
 ## Pre-load data in Blob storage with CLFSLoad
 
-You can use the <!--[Avere CLFSLoad](https://aka.ms/avere-clfsload)--> Avere CLFSLoad utility to copy data to a new Blob storage container before you add it as a storage target. This utility runs on a single Linux system and writes data in the proprietary format needed for Azure HPC Cache. CLFSLoad is the most efficient way to populate a Blob storage container for use with the cache.
+You can use the Avere CLFSLoad utility to copy data to a new Blob storage container before you add it as a storage target. This utility runs on a single Linux system and writes data in the proprietary format needed for Azure HPC Cache. CLFSLoad is the most efficient way to populate a Blob storage container for use with the cache.
 
 The Avere CLFSLoad utility is available by request from your Azure HPC Cache team. Ask your team contact for it, or open a [support ticket](hpc-cache-support-ticket.md) to request assistance.
 
 This option works with new, empty containers only. Create the container before using Avere CLFSLoad.
 
-Detailed information is included in the Avere CLFSLoad distribution, which is available on request from the Azure HPC Cache team. <!-- [Avere CLFSLoad readme](https://github.com/microsoft/Avere-CLFSLoad/blob/master/README.md). --><!-- caution literal link -->
+Detailed information is included in the Avere CLFSLoad distribution, which is available on request from the Azure HPC Cache team.
 
 A general overview of the process:
 
@@ -47,8 +47,6 @@ The Avere CLFSLoad utility needs the following information:
 * A shared access signature (SAS) token that allows the utility to write to the container
 * A local path to the data source - either a local directory that contains the data to copy, or a local path to a mounted remote system with the data
 
-<!-- The requirements are explained in detail in the [Avere CLFSLoad readme](https://aka.ms/avere-clfsload). -->
-
 ## Copy data through the Azure HPC Cache
 
 If you don't want to use the Avere CLFSLoad utility, or if you want to add a large amount of data to an existing Blob storage target, you can copy it through the cache. Azure HPC Cache is designed to serve multiple clients simultaneously, so to copy data through the cache, you should use parallel writes from multiple clients.

articles/hpc-cache/hpc-cache-manage.md

@@ -83,13 +83,6 @@ The back-end storage volumes used as storage targets are unaffected when you del
 > Azure HPC Cache does not automatically write changed data from the cache to the back-end storage systems before deleting the cache.
 >
 > To make sure that all data in the cache has been written to long-term storage, [stop the cache](#stop-the-cache) before you delete it. Make sure that it shows the status **Stopped** before clicking the delete button.
-<!--... written to long-term storage, follow this procedure:
->
-> 1. [Remove](hpc-cache-edit-storage.md#remove-a-storage-target) each storage target from the Azure HPC Cache by using the delete button on the Storage targets page. The system automatically writes any changed data from the cache to the back-end storage system before removing the target.
-> 1. Wait for the storage target to be completely removed. The process can take an hour or longer if there is a lot of data to write from the cache. When it is done, a portal notification says that the delete operation was successful, and the storage target disappears from the list.
-> 1. After all affected storage targets have been deleted, it is safe to delete the cache.
->
-> Alternatively, you can use the [flush](#flush-cached-data) option to save cached data, but there is a small risk of losing work if a client writes a change to the cache after the flush completes but before the cache instance is destroyed.-->
 
 ## Cache metrics and monitoring
 
@@ -101,6 +94,5 @@ These charts are part of Azure's built-in monitoring and analytics tools. Additi
 
 ## Next steps
 
-<!-- * Learn more about metrics and statistics for hpc cache -->
 * Learn more about [Azure metrics and statistics tools](../azure-monitor/index.yml)
 * Get [help with your Azure HPC Cache](hpc-cache-support-ticket.md)

articles/hpc-cache/hpc-cache-overview.md

@@ -4,8 +4,8 @@ description: Describes Azure HPC Cache, a file access accelerator solution for h
 author: ekpgh
 ms.service: hpc-cache
 ms.topic: overview
-ms.date: 03/09/2020
-ms.author: rohogue
+ms.date: 04/15/2020
+ms.author: v-erkel
 ---
 
 # What is Azure HPC Cache?

articles/hpc-cache/hpc-cache-prereqs.md

@@ -76,7 +76,6 @@ To create a compatible storage account, use these settings:
 * Access tier (default): **Hot**
 
 It's a good practice to use a storage account in the same location as your cache.
-<!-- clarify location - same region or same resource group or same virtual network? -->
 
 You also must give the cache application access to your Azure storage account as mentioned in [Permissions](#permissions), above. Follow the procedure in [Add storage targets](hpc-cache-add-storage.md#add-the-access-control-roles-to-your-account) to give the cache the required access roles. If you are not the storage account owner, have the owner do this step.
 

articles/hpc-cache/hpc-region-recovery.md

@@ -53,4 +53,3 @@ All clients will need to mount the new cache, even if the clients were not affec
 ## Learn more
 
 The Azure application architecture guide includes more information about how to [recover from a region-wide service disruption](<https://docs.microsoft.com/azure/architecture/resiliency/recovery-loss-azure-region>).
-<!-- this should be an internal link instead of a URL but I can't find the tree  -->

articles/hpc-cache/media/change-key-click.png

@@ -52,5 +52,7 @@
     href: troubleshoot-nas.md
   - name: Recover from a regional outage
     href: hpc-region-recovery.md
+  - name: Use customer-managed encryption keys
+    href: customer-keys.md
   - name: Use Azure NetApp Files with Azure HPC Cache
     href: hpc-cache-netapp.md