Merge pull request #302981 from b-ahibbard/edit-net-features

Edit net features - portal/cli/api

Author: v-dirichards

articles/azure-netapp-files/azure-netapp-files-configure-nfsv41-domain.md

@@ -44,7 +44,7 @@ You can specify a desired NFSv4.1 ID domain for all non-LDAP volumes using the A
 
 Azure NetApp Files supports the ability to set the NFSv4.1 ID domain for all non-LDAP volumes in a subscription using the Azure portal. This feature is currently in preview. You need to register the feature before using it for the first time. After registration, the feature is enabled and works in the background.
 
-1.  Register the feature
+1.  Register the feature:
 
     ```azurepowershell-interactive
     Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFNFSV4IDDomain
@@ -53,7 +53,7 @@ Azure NetApp Files supports the ability to set the NFSv4.1 ID domain for all non
 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.
+    > The **RegistrationState** can remain 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 ANFNFSV4IDDomain

articles/azure-netapp-files/configure-network-features.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 03/04/2025
+ms.date: 08/08/2025
 ms.custom: references_regions
 ms.author: anfdocs
 # Customer intent: As an Azure NetApp Files administrator, I want to configure network features for my volumes, so that I can optimize resource allocation and leverage VNet capabilities based on my workload requirements.
@@ -19,12 +19,12 @@ The **Network Features** functionality enables you to indicate whether you want
 Two settings are available for network features: 
 
 * ***Standard***  
-    This setting enables VNet features for the volume. Standard network features is the default and preferred setting. 
+    This setting enables VNet features for the volume. The default and preferred setting is Standard network features. 
 
     If you need higher IP limits or VNet features such as [network security groups (NSGs)](../virtual-network/network-security-groups-overview.md), [user-defined routes](../virtual-network/virtual-networks-udr-overview.md#user-defined), or additional connectivity patterns, set **Network Features** to *Standard*.
 
 * ***Basic***  
-    This setting provides reduced IP limits (<1000) and no additional VNet features for the volumes.
+    This setting provides reduced IP limits (less than 1,000 IP addresses) and no additional VNet features for the volumes.
 
     You should set **Network Features** to *Basic* if you don't require VNet features.  
 
@@ -59,52 +59,144 @@ This section shows you how to set the network features option when you create a
 
     [ ![Screenshot that shows the Volumes page displaying the network features setting.](./media/configure-network-features/network-features-volume-list.png)](./media/configure-network-features/network-features-volume-list.png#lightbox)
 
-## Edit network features option for existing volumes
+## Edit network features for existing volumes
 
 You can edit the network features option of existing volumes from *Basic* to *Standard* network features. The change you make applies to all volumes in the same *network sibling set* (or *siblings*). Siblings are determined by their network IP address relationship. They share the same network interface card (NIC) for mounting the volume to the client or connecting to the remote share of the volume. At the creation of a volume, its siblings are determined by a placement algorithm that aims for reusing the IP address where possible.
 
->[!IMPORTANT]
->It's not recommended that you use the edit network features option with Terraform-managed volumes due to risks. You must follow separate instructions if you use Terraform-managed volumes. For more information see, [Update Terraform-managed Azure NetApp Files volume from Basic to Standard](#update-terraform-managed-azure-netapp-files-volume-from-basic-to-standard).
-
-
 ### Considerations when editing networking features 
 
-* If you enabled both the `ANFStdToBasicNetworkFeaturesRevert` and `ANFBasicToStdNetworkFeaturesUpgrade` AFECs and are using 1 or 2-TiB capacity pools, see [Resize a capacity pool or a volume](azure-netapp-files-resize-capacity-pools-or-volumes.md) for information about sizing your capacity pools. 
 * <a name="no-downtime"></a> Azure NetApp Files supports a non-disruptive upgrade to Standard network features and a revert to Basic network features. This operation is expected to take at least 15 minutes. You can't create a regular or data protection volume or application volume group in the targeted network sibling set while the operation completes.    
+* If you revert from Standard to Basic network features, considerations apply and require careful planning. See [Guidelines for Azure NetApp Files network planning](azure-netapp-files-network-topologies.md#constraints) for constraints and supported network topologies about Standard and Basic network features. 
 
-> [!NOTE]
-> You need to submit a waitlist request for accessing the feature through the **[Azure NetApp Files standard networking features (edit volumes) Request Form](https://aka.ms/anfeditnetworkfeaturespreview)**. The feature can take approximately one week to be enabled after you submit the waitlist request. You can check the status of feature registration by using the following command: 
->
-> ```azurepowershell-interactive
-> Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFBasicToStdNetworkFeaturesUpgrade                                                      
-> 
-> FeatureName                         ProviderName     RegistrationState   
-> -----------                         ------------     -----------------   
-> ANFBasicToStdNetworkFeaturesUpgrade Microsoft.NetApp Registered
-> ```
+### Register the feature
 
-> [!NOTE]
-> You can also revert the option from *Standard* back to *Basic* network features. Before performing the revert operation, you must submit a waitlist request through the **[Azure NetApp Files standard networking features (edit volumes) Request Form](https://aka.ms/anfeditnetworkfeatures)**. The revert capability can take approximately one week to be enabled after you submit the waitlist request. You can check the status of the registration by using the following command: 
+Before editing network features on an existing volume, you need to register the feature. Ensure you are using the correct feature name for the change in network features you want to perform.
+
+* To upgrade to Standard network features from Basic, use the feature name `ANFBasicToStdNetworkFeaturesUpgrade`.
+
+1.  Register the feature:
+
+    ```azurepowershell-interactive
+    Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFBasicToStdNetworkFeaturesUpgrade 
+    ```
+
+2. Check the status of the feature registration: 
+
+    > [!NOTE]
+    > The **RegistrationState** can remain 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 ANFBasicToStdNetworkFeaturesUpgrade 
+    ```
 
+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. 
 
+
+> [!NOTE]
+> To revert from *Standard* to *Basic* network features, you must also register the feature. 
+> Submit a waitlist request through the **[Azure NetApp Files standard networking features (edit volumes) Request Form](https://aka.ms/anfeditnetworkfeatures)**. The revert capability can take approximately one week to be enabled after you submit the waitlist request. Check the status of the registration with the following command. 
 >
 > ```azurepowershell-interactive
-> Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFStdToBasicNetworkFeaturesRevert                                                      
+> Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFStdToBasicNetworkFeaturesRevert   
+>```                                                   
 > 
-> FeatureName                         ProviderName     RegistrationState   
-> -----------                         ------------     -----------------   
-> ANFStdToBasicNetworkFeaturesRevert Microsoft.NetApp Registered
-> ```
+> When the `RegistrationState` displays Registered, the feature is approved for use. 
 >
 > If you revert, considerations apply and require careful planning. See [Guidelines for Azure NetApp Files network planning](azure-netapp-files-network-topologies.md#constraints) for constraints and supported network topologies about Standard and Basic network features. 
 
-### Edit network features 
+### <a name="edit"></a> Edit network features
+
+# [Portal](#tab/portal)
 
 1. Navigate to the volume for which you want to change the network features option. 
 1. Select **Change network features**. 
-1. The **Edit network features** window displays the volumes that are in the same network sibling set. Confirm whether you want to modify the network features option. 
+1. The Edit network features window displays the volumes that are in the same network sibling set. Select **Save** to proceed with the operation. 
+1. Select **Yes** to confirm you want to modify the network features option.
+
+# [Azure CLI](#tab/cli)
+
+You should be running the latest version of the Azure CLI. Confirm the version with the `az version` command. If necessary, see [How to update the Azure CLI](/cli/azure/update-azure-cli).
+
+1. List volumes in the capacity pool. Capture the network sibling set ID of the volume whose network features you want to update. 
+
+    ```azurecli-interactive
+    az netappfiles volume list --account-name <account> --resource-group <resourceGroup> --pool-name <capacityPool> 
+    ```
+
+1. Query the network sibling set. Capture the network sibling set state ID for the network sibling set you want to update. 
+
+    ```azurecli-interactive
+    az netappfiles query-network-sibling-set --network-sibling-set-id <networkSiblingSetID> --subnet-id <subnetID> 
+    ```
+
+1. Run the following command to update the network features on a volume:
+
+    ```azurecli-interactive
+    az netappfiles update-network-sibling-set --network-sibling-set-id <networkSiblingSetID> --network-sibling-set-state-id=<stateID> --subnet-id <subnetID> --location <location> --network-features Standard|Basic 
+    ```
+
+1. Confirm the operation succeeded by checking the network features of the volume:
+
+    ```azurecli
+    az netappfiles volume show -g <resourceGroup> --account-name <account> --pool-name <capacityPool> --name <volumeName>
+    ```
 
-### Update Terraform-managed Azure NetApp Files volume from Basic to Standard 
+# [PowerShell](#tab/powershell)
+
+1. List the volumes in the capacity pool. Capture the network sibling set ID of the volume whose network features you want to update. 
+
+    ```azurepowershell-interactive
+    Get-AzNetAppFilesVolume -ResourceGroupName "<resourceGroup> -AccountName "<accountName>" -PoolName "<capacityPool>" -Name "<volume>" 
+    ```
+
+1. Query the network sibling set. Capture the network sibling set state ID for the network sibling set you want to update. 
+
+    ```azurepowershell-interactive
+    Get-AzNetAppFilesNetworkSiblingSet -Location "<location>" -SubnetId "<subnetID>" -NetworkSiblingSetId "<networkSiblingSetID>"
+    ```
+
+1. Update the network sibling set.
+
+    ```azurepowershell-interactive
+    Update-AzNetAppFilesNetworkSiblingSet -Location "<location>" -SubnetId "<subscription>" -NetworkSiblingSetId "<networkSiblingSetID>" -NetworkSiblingSetStateId "<networkSiblingSetID>" -NetworkFeature "<Standard|Basic>" 
+    ```
+
+1. Confirm the volume has the correct network features setting.
+
+    ```azurepowershell-interactive
+    Get-AzNetAppFilesVolume -ResourceGroupName "<resourceGroup> -AccountName "<accountName>" -PoolName "<capacityPool>" -Name "<volume>" 
+    ```
+
+# [REST API](#tab/rest-api)
+
+You should be using the [latest version of the Azure NetApp Files REST API](/rest/api/netapp/operation-groups). 
+
+1. Query the network sibling set. Take note of the network sibling set ID and network sibling set state ID. 
+
+    ```http
+    GET https://management.azure.com/subscriptions/{subscriptionId}/providers/Microsoft.NetApp/locations/{location}/queryNetworkSiblingSet?api-version=2025-03-01
+    ```
+
+1. Send a PATCH request to update the network features. Set the "networkFeatures" property to Basic or Standard. 
+
+    ```http
+    PATCH https://management.azure.com/subscriptions/{subscriptionId}/providers/Microsoft.NetApp/locations/{location}/updateNetworkSiblingSet
+    ```
+
+    ```json
+    {
+        "networkSiblingSetId": "<networkSiblingSetID>",
+        "subnetId": "<subnetID>",
+        "networkSiblingSetStateId": "<siblingSetStateID>",
+        "networkFeatures": "<Basic|Standard>"
+    }
+    ```
+
+1. Confirm the network features changed with a GET request. 
+
+---
+<!-- terraform
+### <a name="terraform"></a> Update Terraform-managed Azure NetApp Files volume from Basic to Standard 
 
 If your Azure NetApp Files volume is managed using Terraform, editing the network features requires additional steps. Terraform-managed Azure resources store their state in a local file, which is in your Terraform module or in Terraform Cloud. 
 
@@ -122,8 +214,6 @@ The name of the state file in your Terraform module is `terraform.tfstate`. It c
 
 Do ***not*** manually update the `terraform.tfstate` file. Likewise, the `network_features` argument in the `*.tf` and `*.tf.json` configuration files should also not be updated until you follow the steps outlined here as this would cause a mismatch in the arguments of the remote volume and the local configuration file representing that remote volume. When Terraform detects a mismatch between the arguments of remote resources and local configuration files representing those remote resources, Terraform can destroy the remote resources and reprovision them with the arguments in the local configuration files. This can cause data loss in a volume.
 
-By following the steps outlined here, the `network_features` argument in the `terraform.tfstate` file is automatically updated by Terraform to have the value of "Standard" without destroying the remote volume, thus indicating the network features has been successfully updated to Standard.
-
 >[!NOTE]
 > It's recommended to always use the latest Terraform version and the latest version of the `azurerm` Terraform module.
 
@@ -148,11 +238,16 @@ All Terraform configuration files that define these volumes need to be updated,
 You must modify the configuration files for each affected volume managed by Terraform that you discovered. Failing to update the configuration file can destroy the volume or result in data loss. 
 
 >[!IMPORTANT]
->Depending on your volume’s lifecycle configuration block settings in your Terraform configuration file, your volume can be destroyed, including possible data loss upon running `terraform apply`. Ensure you know which affected volumes are managed by Terraform and which are not.
+>Depending on your volume’s lifecycle configuration block settings in your Terraform configuration file, your volume can be destroyed, including possible data loss upon running `terraform apply`. Ensure you know which affected volumes are managed by Terraform.
 
 1. Locate the affected Terraform-managed volumes configuration files.
-1. Add the `ignore_changes = [network_features]` to the volume's `lifecycle` configuration block. If the `lifecycle` block doesn't exist in that volume’s configuration, add it.
-
+1. Add or modify the `lifecycle` block in the volume’s configuration to include the `ignore_changes = [network_features]`. The `lifecycle` configuration block must include the following settings: 
+    ```
+    lifecycle {
+        prevent_destroy = true
+        ignore_changes = [network_features]
+    }
+    ```
     :::image type="content" source="./media/configure-network-features/terraform-lifecycle.png" alt-text="Screenshot of the lifecycle configuration." lightbox="./media/configure-network-features/terraform-lifecycle.png":::
 
 1. Repeat for each affected Terraform-managed volume. 
@@ -180,21 +275,10 @@ The `ignore_changes` feature is intended to be used when a resource’s referenc
 
     Repeat for all modules containing affected volumes.
 
-    Observe the change in the value of the `network_features` argument in the `terraform.tfstate` files, which changed from "Basic" to "Standard":
+    The terraform.tfstate file doesn't reflect the change. Don't change the `network_features` parameter in the configuration file. 
 
     :::image type="content" source="./media/configure-network-features/updated-terraform-module.png" alt-text="Screenshot of updated Terraform module." lightbox="./media/configure-network-features/updated-terraform-module.png":::
-
-#### Update Terraform-managed Azure NetApp Files volumes’ configuration file for configuration parity
-
-Once you've update the volumes' network features, you must also modify the `network_features` arguments and `lifecycle blocks` in all configuration files of affected Terraform-managed volumes. This update ensures that if you have to recreate or update the volume, it maintains its Standard network features setting. 
-
-1. In the configuration file, set `network_features` to "Standard" and remove the `ignore_changes = [network_features]` line from the `lifecycle` block. 
-
-    :::image type="content" source="./media/configure-network-features/terraform-network-features-standard.png" alt-text="Screenshot of Terraform module with Standard network features." lightbox="./media/configure-network-features/terraform-network-features-standard.png":::
-
-1. Repeat for each affected Terraform-managed volume. 
-1. Verify that the updated configuration files accurately represent the configuration of the remote resources by running `terraform plan`. Confirm the output reads "No changes."
-1. To complete the update, run `terraform apply`. 
+-->
 
 ## Next steps  
 

articles/azure-netapp-files/terraform-manage-volume.md

@@ -48,6 +48,6 @@ The following instructions are a high-level overview of the steps required to up
 
 ## Next steps 
 
-* [Update Terraform-Managed Azure NetApp Files Volume Network Feature from Basic to Standard](configure-network-features.md#update-terraform-managed-azure-netapp-files-volume-from-basic-to-standard)
+<!-- * [Update Terraform-Managed Azure NetApp Files Volume Network Feature from Basic to Standard](configure-network-features.md#terraform) -->
 * [Populate Availability Zone for Terraform-Managed Azure NetApp Files Volume](manage-availability-zone-volume-placement.md#populate-availability-zone-for-terraform-managed-volumes)
 * [Managing Azure NetApp Files preview features with Terraform Cloud and AzAPI Provider](https://techcommunity.microsoft.com/t5/azure-architecture-blog/managing-azure-netapp-files-preview-features-with-terraform/ba-p/3657714)