hpc-cache: update for start/stop UI

Author: ekpgh

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

@@ -34,8 +34,6 @@ To define an Azure Blob container, enter this information.
 
 ![screenshot of the add storage target page, populated with information for a new Azure Blob storage target](media/hpc-cache-add-blob.png)
 
-<!-- need to replace screenshot after note text is updated with both required RBAC roles and also with correct search term -->
-
 * **Storage target name** - Set a name that identifies this storage target in the Azure HPC Cache.
 * **Target type** - Choose **Blob**.
 * **Storage account** - Select the account that you want to use.

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

@@ -4,27 +4,44 @@ description: How to manage and update Azure HPC Cache using the Azure portal
 author: ekpgh
 ms.service: hpc-cache
 ms.topic: conceptual
-ms.date: 1/08/2020
+ms.date: 1/29/2020
 ms.author: rohogue
 ---
 
 # Manage your cache from the Azure portal
 
-The cache overview page in the Azure portal shows project details, cache status, and basic statistics for your cache. It also has controls to delete the cache, flush data to long-term storage, or update software.
+The cache overview page in the Azure portal shows project details, cache status, and basic statistics for your cache. It also has controls to stop or start the cache, delete the cache, flush data to long-term storage, and update software.
 
 To open the overview page, select your cache resource in the Azure portal. For example, load the **All resources** page and click the cache name.
 
 ![screenshot of an Azure HPC Cache instance's Overview page](media/hpc-cache-overview.png)
 
 The buttons at the top of the page can help you manage the cache:
 
+* **Start** and [**Stop**](#stop-the-cache) - Suspends cache operation
 * [**Flush**](#flush-cached-data) - Writes changed data to storage targets
 * [**Upgrade**](#upgrade-cache-software) - Updates the cache software
 * **Refresh** - Reloads the overview page
 * [**Delete**](#delete-the-cache) - Permanently destroys the cache
 
 Read more about these options below.
 
+## Stop the cache
+
+You can stop the cache to reduce costs during an inactive period. You are not charged for throughput while the cache is stopped, but you still must pay the cache disk fee for the allocated storage. (See the [pricing](https://aka.ms/hpc-cache-pricing) page for details.)
+
+A stopped cache does not respond to client requests.
+
+The **Stop** button suspends an active cache. The **Stop** button is available only when a cache is active and its status is **Healthy**.
+
+![screenshot of the top buttons with Stop highlighted and a pop-up message describing the stop action and asking 'do you want to continue?' with Yes (default) and No buttons](media/stop-cache.png)
+
+After you click Yes to confirm stopping the cache, the cache automatically flushes its contents to the storage targets. This process might take some time, but it ensures data consistency. Finally, the cache status changes to **Stopped**.
+
+To re-activate a stopped cache, click the **Start** button. No confirmation is needed.
+
+![screenshot of the top buttons with Start highlighted](media/start-cache.png)
+
 ## Flush cached data
 
 The **Flush** button on the overview page tells the cache to immediately write all changed data that is stored in the cache to the back-end storage targets. The cache routinely saves data to the storage targets, so it's not necessary to do this manually unless you want to make sure the back-end storage system is up to date. For example, you might use **Flush** before taking a storage snapshot or checking the data set size.
@@ -63,13 +80,14 @@ The back-end storage volumes used as storage targets are unaffected when you del
 > [!NOTE]
 > 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, follow this procedure:
+> 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.
+> 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