rename Std. storage with cool access

Author: b-ahibbard

articles/azure-netapp-files/TOC.yml

@@ -77,7 +77,7 @@
     items:
     - name: Cost model for Azure NetApp Files
       href: azure-netapp-files-cost-model.md
-    - name: Azure NetApp Files storage with cool access
+    - name: Standard storage with cool access
       href: cool-access-introduction.md
   - name: Quotas 
     items:
@@ -299,7 +299,7 @@
         href: dynamic-change-volume-service-level.md
       - name: Manage default and individual user and group quotas for a volume
         href: manage-default-individual-user-group-quotas.md
-      - name: Manage storage with cool access 
+      - name: Manage standard storage with cool access 
         href: manage-cool-access.md
     - name: Update Terraform-managed volume
       href: terraform-manage-volume.md

articles/azure-netapp-files/azure-netapp-files-create-volumes-smb.md

@@ -75,7 +75,7 @@ Before creating an SMB volume, you need to create an Active Directory connection
         If the volume is created in an auto QoS capacity pool, the value displayed in this field is (quota x service level throughput).   
 
     * **Enable Cool Access**, **Coolness Period**, and **Cool Access Retrieval Policy**      
-        These fields configure [storage with cool access in Azure NetApp Files](cool-access-introduction.md). For descriptions, see [Manage Azure NetApp Files storage with cool access](manage-cool-access.md). 
+        These fields configure [standard storage with cool access in Azure NetApp Files](cool-access-introduction.md). For descriptions, see [Manage Azure NetApp Files standard storage with cool access](manage-cool-access.md). 
 
     * **Virtual network**  
         Specify the Azure virtual network (VNet) from which you want to access the volume.  

articles/azure-netapp-files/azure-netapp-files-create-volumes.md

@@ -69,7 +69,7 @@ This article shows you how to create an NFS volume. For SMB volumes, see [Create
         If the volume is created in an auto QoS capacity pool, the value displayed in this field is (quota x service level throughput).   
 
     * **Enable Cool Access**, **Coolness Period**, and **Cool Access Retrieval Policy**      
-        These fields configure [storage with cool access in Azure NetApp Files](cool-access-introduction.md). For descriptions, see [Manage Azure NetApp Files storage with cool access](manage-cool-access.md). 
+        These fields configure [standard storage with cool access in Azure NetApp Files](cool-access-introduction.md). For descriptions, see [Manage Azure NetApp Files standard storage with cool access](manage-cool-access.md). 
 
     * **Virtual network**  
         Specify the Microsoft Azure Virtual Network from which you want to access the volume.  

articles/azure-netapp-files/azure-netapp-files-introduction.md

@@ -45,7 +45,7 @@ Azure NetApp Files is designed to provide high-performance file storage for ente
 | Virtual machine (VM) networked storage performance | Higher VM network throughput compared to disk IO limits enable more demanding workloads on smaller Azure VMs. | Improve application performance at a smaller VM footprint, improving overall efficiency and lowering application license cost.
 | Deep workload readiness | Seamless deployment and migration of any-size workload with well-documented deployment guides. | Easily migrate any workload of any size to the platform. Enjoy a seamless, cost-effective deployment and migration experience.
 | Datastores for Azure VMware Solution | Use Azure NetApp Files as a storage solution for VMware workloads in Azure, reducing the need for superfluous compute nodes normally included with Azure VMware Solution expansions. | Save money by eliminating the need for unnecessary compute nodes when you expand storage, resulting in significant cost savings.
-| Storage with cool access | Use the cool access option to move inactive data transparently from Azure NetApp Files storage (the hot tier) to an Azure Storage account (the cool tier). | Save money by transitioning data that resides within Azure NetApp Files volumes (the hot tier) by moving blocks to the lower-cost storage (the cool tier). |
+| Standard storage with cool access | Use the cool access option of Azure NetApp Files Standard service level to move inactive data transparently from Azure NetApp Files Standard service-level storage (the hot tier) to an Azure Storage account (the cool tier). | Save money by transitioning data that resides within Azure NetApp Files volumes (the hot tier) by moving blocks to the lower-cost storage (the cool tier). |
 
 These features work together to provide a high-performance file storage solution for the demands of enterprise workloads. They help to ensure that your workloads experience optimal (low) storage latency, cost, and scale.
 

articles/azure-netapp-files/azure-netapp-files-network-topologies.md

@@ -217,5 +217,5 @@ In the topology illustrated above, the on-premises network is connected to a hub
 * [Configure network features for an Azure NetApp Files volume](configure-network-features.md) 
 * [Virtual network peering](../virtual-network/virtual-network-peering-overview.md)
 * [Configure Virtual WAN for Azure NetApp Files](configure-virtual-wan.md)
-* [Storage with cool access in Azure NetApp Files](cool-access-introduction.md)
-* [Manage Azure NetApp Files storage with cool access](manage-cool-access.md)
+* [Standard storage with cool access in Azure NetApp Files](cool-access-introduction.md)
+* [Manage Azure NetApp Files standard storage with cool access](manage-cool-access.md)

articles/azure-netapp-files/azure-netapp-files-service-levels.md

@@ -19,20 +19,14 @@ Azure NetApp Files supports three service levels: *Ultra*, *Premium*, and *Stand
     The Standard service level provides up to 16 MiB/s of throughput per 1 TiB of capacity provisioned.   
 
     * Standard storage with cool access:      
-        The throughput experience for this service level is the same as the Standard service level for data that is in the hot tier. It may differ when data that resides in the cool tier is accessed. For more information, see [storage with cool access in Azure NetApp Files](cool-access-introduction.md#effects-of-cool-access-on-data). 
+        The throughput experience for this service level is the same as the Standard service level for data that is in the hot tier. It may differ when data that resides in the cool tier is accessed. For more information, see [Standard storage with cool access in Azure NetApp Files](cool-access-introduction.md#effects-of-cool-access-on-data). 
 
 * <a name="Premium"></a>Premium storage:   
     The Premium service level provides up to 64 MiB/s of throughput per 1 TiB of capacity provisioned. 
 
-    * Premium storage with cool access:      
-        The throughput experience for this service level is the same as the Premium service level for data that is in the hot tier. It may differ when data that resides in the cool tier is accessed. For more information, see [storage with cool access in Azure NetApp Files](cool-access-introduction.md#effects-of-cool-access-on-data). 
-
 * <a name="Ultra"></a>Ultra storage:   
     The Ultra service level provides up to 128 MiB/s of throughput per 1 TiB of capacity provisioned. 
 
-    * Ultra storage with cool access:      
-        The throughput experience for this service level is the same as the Ultra service level for data that is in the hot tier. It may differ when data that resides in the cool tier is accessed. For more information, see [storage with cool access in Azure NetApp Files](cool-access-introduction.md#effects-of-cool-access-on-data). 
-
 ## Throughput limits
 
 The throughput limit for a volume is determined by the combination of the following factors:
@@ -73,4 +67,3 @@ The following diagram illustrates the scenarios for the SAP HANA volumes:
 - [Service Level Agreement (SLA) for Azure NetApp Files](https://azure.microsoft.com/support/legal/sla/netapp/)
 - [Dynamically change the service level of a volume](dynamic-change-volume-service-level.md) 
 - [Service-level objectives for cross-region replication](cross-region-replication-introduction.md#service-level-objectives)
-- [Azure NetApp Files storage with cool access](cool-access-introduction.md) 

articles/azure-netapp-files/azure-netapp-files-set-up-capacity-pool.md

@@ -56,8 +56,8 @@ Creating a capacity pool enables you to create volumes within it.
     >[!NOTE]
     >[!INCLUDE [Limitations for capacity pool minimum of 1 TiB](includes/2-tib-capacity-pool.md)]
 
-    * **Enable cool access** 
-        This option specifies whether volumes in the capacity pool support cool access. For details about using this option, see [Manage Azure NetApp Files storage with cool access](manage-cool-access.md). 
+    * **Enable cool access**  *(for Standard service level only)*   
+        This option specifies whether volumes in the capacity pool support cool access. This option is currently supported for the Standard service level only. For details about using this option, see [Manage Azure NetApp Files standard storage with cool access](manage-cool-access.md). 
 
     * **QoS**   
         Specify whether the capacity pool should use the **Manual** or **Auto** QoS type.  See [Storage Hierarchy](azure-netapp-files-understand-storage-hierarchy.md) and [Performance Considerations](azure-netapp-files-performance-considerations.md) to understand the QoS types.  

articles/azure-netapp-files/azure-netapp-files-understand-storage-hierarchy.md

@@ -41,7 +41,7 @@ Understanding how capacity pools work helps you select the right capacity pool t
 - You can't move a capacity pool across NetApp accounts.   
   For example, in the [Conceptual diagram of storage hierarchy](#conceptual_diagram_of_storage_hierarchy), you can't move Capacity Pool 1 US East NetApp account to US West 2 NetApp account.  
 - You can't delete a capacity pool until you delete all volumes within the capacity pool. 
-- You can configure a Standard service-level capacity pool with the cool access option. For more information about cool access, see [Azure NetApp Files storage with cool access](cool-access-introduction.md). 
+- You can configure a Standard service-level capacity pool with the cool access option. For more information about cool access, see [Standard storage with cool access](cool-access-introduction.md). 
 
 ### <a name="qos_types"></a>Quality of Service (QoS) types for capacity pools
 

articles/azure-netapp-files/backup-requirements-considerations.md

@@ -44,7 +44,7 @@ Azure NetApp Files backup in a region can only protect an Azure NetApp Files vol
 
 * If you need to delete a parent resource group or subscription that contains backups, you should delete any backups first. Deleting the resource group or subscription won't delete the backups.
 
-* If you use the storage with cool access, see [Manage Azure NetApp Files storage with cool access](manage-cool-access.md#considerations) for more considerations.
+* If you use the standard storage with cool access, see [Manage Azure NetApp Files standard storage with cool access](manage-cool-access.md#considerations) for more considerations.
 
 ## Next steps
 

articles/azure-netapp-files/cool-access-introduction.md

@@ -1,6 +1,6 @@
 ---
-title: Azure NetApp Files storage with cool access
-description: Explains how to use storage with cool access to configure inactive data to move from the hot tier to an Azure storage account (the cool tier).
+title: Standard storage with cool access in Azure NetApp Files
+description: Explains how to use standard storage with cool access to configure inactive data to move from Azure NetApp Files Standard service-level storage (the hot tier) to an Azure storage account (the cool tier).
 services: azure-netapp-files
 author: b-ahibbard
 ms.service: azure-netapp-files
@@ -10,13 +10,13 @@ ms.author: anfdocs
 ms.custom: references_regions
 ---
 
-# Azure NetApp Files storage with cool access 
+# Standard storage with cool access in Azure NetApp Files 
 
-Using Azure NetApp Files storage with cool access, you can configure inactive data to move from any Azure NetApp Files storage (the *hot tier*) to an Azure storage account (the *cool tier*). Enabling cool access moves inactive data blocks from the volume and the volume's snapshots to the cool tier, resulting in cost savings.
+Using Azure NetApp Files standard storage with cool access, you can configure inactive data to move from Azure NetApp Files Standard service-level storage (the *hot tier*) to an Azure storage account (the *cool tier*). Enabling cool access moves inactive data blocks from the volume and the volume's snapshots to the cool tier, resulting in cost savings.
 
 Most cold data is associated with unstructured data. It can account for more than 50% of the total storage capacity in many storage environments. Infrequently accessed data associated with productivity software, completed projects, and old datasets are an inefficient use of a high-performance storage. 
 
-Azure NetApp Files supports three [service levels](azure-netapp-files-service-levels.md) that can be configured at capacity pool level (Standard, Premium and Ultra).
+Azure NetApp Files supports three [service levels](azure-netapp-files-service-levels.md) that can be configured at capacity pool level (Standard, Premium and Ultra). Cool access is an additional service only on the Standard service level.
 
 The following diagram illustrates an application with a volume enabled for cool access.
 
@@ -25,6 +25,7 @@ The following diagram illustrates an application with a volume enabled for cool
 In the initial write, data blocks are assigned a "warm" temperature value (in the diagram, red data blocks) and exist on the "hot" tier. As the data resides on the volume, a temperature scan monitors the activity of each block. When a data block is inactive, the temperature scan decreases the value of the block until it has been inactive for the number of days specified in the cooling period. The cooling period can be between 2 and 183 days; it has a default value of 31 days. Once marked "cold,"  the tiering scan collects blocks and packages them into 4-MB objects, which are moved to Azure storage fully transparently. To the application and users, those cool blocks still appear online. Tiered data appears to be online and continues to be available to users and applications by transparent and automated retrieval from the cool tier.
 
 By `Default` (unless cool access retrieval policy is configured otherwise), data blocks on the cool tier that are read randomly again become "warm" and are moved back to the hot tier. Once marked as _warm_, the data blocks are again subjected to the temperature scan. However, large sequential reads (such as index and antivirus scans) on inactive data in the cool tier don't "warm" the data nor do they trigger inactive data to be moved back to the hot tier. Additionally, sequential reads for Azure NetApp Files, cross-region replication, or cross-zone replication do ***not*** "warm" the data.
+<!-- confirm update with SMEs -->
 
 >[!IMPORTANT]
 >If you're using a third-party backup service, configure it to use NDMP instead of the CIFS or NFS protocols. NDMP reads do not affect the temperature of the data.
@@ -33,7 +34,7 @@ Metadata is never cooled and always remains in the hot tier. As such, the activi
 
 ## Supported regions 
 
-Azure NetApp Files storage with cool access is supported for the following regions: 
+Standard storage with cool access is supported for the following regions: 
 
 * Australia Central
 * Australia Central 2
@@ -166,9 +167,9 @@ Cool access offers [performance metrics](azure-netapp-files-metrics.md#cool-acce
 
 ## Billing 
 
-You can enable tiering at the volume level for a newly created capacity pool. How you're billed is based on the following factors: 
+You can enable tiering at the volume level for a newly created capacity pool that uses the Standard service level. How you're billed is based on the following factors: 
 
-* The capacity in the service level
+* The capacity in the Standard service level
 * Unallocated capacity within the capacity pool
 * The capacity in the cool tier (by enabling tiering for volumes in a Standard capacity pool)
 * Network transfer between the hot tier and the cool tier at the rate that is determined by the markup on top of the transaction cost (`GET` and `PUT` requests) on blob storage and private link transfer in either direction between the hot tiers.
@@ -330,9 +331,9 @@ Your first twelve-month savings:
 
 
 > [!TIP]     
-> You can use the [Azure NetApp Files storage with cool access cost savings estimator](https://aka.ms/anfcoolaccesscalc) to interactively estimate cost savings based on changeable input parameters.
+> You can use the [Azure NetApp Files standard storage with cool access cost savings estimator](https://aka.ms/anfcoolaccesscalc) to interactively estimate cost savings based on changeable input parameters.
 
 ## Next steps
 
-* [Manage Azure NetApp Files storage with cool access](manage-cool-access.md)
+* [Manage Azure NetApp Files standard storage with cool access](manage-cool-access.md)
 * [Metrics for Azure NetApp Files](azure-netapp-files-metrics.md)