Merge pull request #268253 from b-ahibbard/3-6

cmk no afec. cool access scanning consideration revision

Author: prmerger-automator[bot]

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

@@ -90,7 +90,6 @@ Before creating your first customer-managed key volume, you must set up:
     * The key must be of type RSA.
 * The key vault must have an [Azure Private Endpoint](../private-link/private-endpoint-overview.md).
     * The private endpoint must reside in a different subnet than the one delegated to Azure NetApp Files. The subnet must be in the same VNet as the one delegated to Azure NetApp.
-* You must register the feature before you can use customer-managed keys. 
 
 For more information about Azure Key Vault and Azure Private Endpoint, refer to:
 * [Quickstart: Create a key vault ](../key-vault/general/quick-create-portal.md)
@@ -100,26 +99,6 @@ For more information about Azure Key Vault and Azure Private Endpoint, refer to:
 * [Network security groups](../virtual-network/network-security-groups-overview.md)
 * [Manage network policies for private endpoints](../private-link/disable-private-endpoint-network-policy.md)
 
-## Register the feature 
-
-You must register customer-managed keys before using it for the first time. 
-
-1. Register the feature: 
-
-    ```azurepowershell-interactive
-    Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFAzureKeyVaultEncryption
-    ```
-
-2. Check the status of the feature registration: 
-
-    > [!NOTE]
-    > The **RegistrationState** may be in the `Registering` state for up to 60 minutes before changing to `Registered`. Wait until the status is **Registered** before continuing.
-
-    ```azurepowershell-interactive
-    Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFAzureKeyVaultEncryption
-    ```
-You can also use [Azure CLI commands](/cli/azure/feature) `az feature register` and `az feature show` to register the feature and display the registration status. 
-
 ## Configure a NetApp account to use customer-managed keys
 
 ### [Portal](#tab/azure-portal)

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

@@ -24,7 +24,7 @@ The standard storage with cool access feature provides options for the “coolne
 * Although cool access is available for the Standard service level, how you're billed for using the feature differs from the Standard service level charges. See the [Billing section](cool-access-introduction.md#billing) for details and examples. 
 * You can convert an existing Standard service-level capacity pool into a cool-access capacity pool to create cool access volumes. However, once the capacity pool is enabled for cool access, you can't convert it back to a non-cool-access capacity pool.  
 * A cool-access capacity pool can contain both volumes with cool access enabled and volumes with cool access disabled.
-* Antivirus and file scanning are not recommended for files that are archived to cool access.
+* To prevent data retrieval from the cool tier to the hot tier during sequential read operations (for example, antivirus or other file scanning operations), set the cool access retrieval policy to "Default" or "Never." For more information, see [Enable cool access on a new volume](#enable-cool-access-on-a-new-volume).
 * After the capacity pool is configured with the option to support cool access volumes, the setting can't be disabled at the _capacity pool_ level. However, you can turn on or turn off the cool access setting at the volume level anytime. Turning off the cool access setting at the _volume_ level stops further tiering of data.  
 * Standard storage with cool access is supported only on capacity pools of the **auto** QoS type.   
     * An auto QoS capacity pool enabled for standard storage with cool access cannot be converted to a capacity pool using manual QoS.

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

@@ -54,8 +54,6 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
 * [Customer-managed keys](configure-customer-managed-keys.md) is now generally available (GA).
 
-    You still must register the feature before using it for the first time.
-
 ## November 2023
 
 * [Capacity pool enhancement:](azure-netapp-files-set-up-capacity-pool.md) New lower limits

articles/virtual-machines/workloads/oracle/oracle-reference-architecture.md

@@ -233,7 +233,7 @@ Patching your virtual machine operating system can be automated using [Azure Aut
 - Consider using ultra disks when available or premium disks for your Oracle database.
 - Consider setting up a standby Oracle database in another Azure region using Oracle Data Guard.
 - Consider using [proximity placement groups](../../co-location.md#proximity-placement-groups) to reduce the latency between your application and database tier.
-- Azure VMs throttle network bandwidth at higher throughput levels than managed disk. You can achieve higher throughput on the same VM SKU or use a smaller VM SKU for the same throughput using networked storage for the database such as [Azure NetApp Files](../../../azure-netapp-files/azure-netapp-files-introduction.md).
+- Azure VMs maximum network bandwidth is (typically) higher than the maximum disk throughput on the same SKU. You can achieve higher throughput on the same VM SKU or use a smaller VM SKU by using high-performance, low-latency networked storage such as [Azure NetApp Files](../../../azure-netapp-files/azure-netapp-files-introduction.md). for the database.
 - Set up [Oracle Enterprise Manager](https://docs.oracle.com/en/enterprise-manager/) for management, monitoring, and logging.
 - Consider using Oracle Automatic Storage Management for streamlined storage management for your database.
 - Use [Azure Pipelines](/azure/devops/pipelines/get-started/what-is-azure-pipelines) to manage patching and updates to your database without any downtime.