Merge pull request #238377 from MicrosoftDocs/main

huypub · web-flow · commit f379f5175e47 · 2023-05-16T10:14:59.000-07:00
5/16 AM Publish again
diff --git a/articles/azure-netapp-files/azure-government.md b/articles/azure-netapp-files/azure-government.md
@@ -32,10 +32,11 @@ All [Azure NetApp Files features](whats-new.md) available on Azure public cloud
 | Azure NetApp Files features | Azure public cloud availability |  Azure Government availability |
 |:--- |:--- |:--- |
 | Azure NetApp Files backup | Public preview | No |
-| Standard network features | Generally available (GA) | No |
 | Azure NetApp Files datastores for AVS | Generally available (GA) | No | 
 | Azure NetApp Files customer-managed keys | Public preview | No |
 | Azure NetApp Files large volumes | Public preview | No |
+| Edit network features for existing volumes | Public preview | No |
+| Standard network features | Generally available (GA) | No |
 
 ## Portal access
 
@@ -81,7 +82,7 @@ When connecting to Azure Government through PowerShell, you must specify an envi
 | --- | --- | 
 | [Azure](/powershell/module/az.accounts/Connect-AzAccount) commands |`Connect-AzAccount -EnvironmentName AzureUSGovernment` | 
 | [Azure Active Directory](/powershell/module/azuread/connect-azuread) commands |`Connect-AzureAD -AzureEnvironmentName AzureUSGovernment` | 
-| [Azure (Classic deployment model)](/powershell/module/servicemanagement/azure.service/add-azureaccount) commands |`Add-AzureAccount -Environment AzureUSGovernment` | 
+| [Azure (Classic deployment model)](/powershell/module/servicemanagement/azure/add-azureaccount) commands |`Add-AzureAccount -Environment AzureUSGovernment` | 
 | [Azure Active Directory (Classic deployment model)](/previous-versions/azure/jj151815(v=azure.100)) commands |`Connect-MsolService -AzureEnvironment UsGovernment` | 
 
 See [Connect to Azure Government with PowerShell](../azure-government/documentation-government-get-started-connect-with-ps.md) for details.
diff --git a/articles/azure-netapp-files/azure-netapp-files-network-topologies.md b/articles/azure-netapp-files/azure-netapp-files-network-topologies.md
@@ -24,7 +24,7 @@ Azure NetApp Files volumes are designed to be contained in a special purpose sub
 
 ## Configurable network features  
 
- You can create new volumes choosing *Standard* or *Basic* network features in supported regions. In regions where the Standard network features aren't supported, the volume defaults to using the Basic network features. For more information, see [Configure network features](configure-network-features.md).
+ In supported regions, you can create new volumes or modify existing volumes to use *Standard* or *Basic* network features. In regions where the Standard network features aren't supported, the volume defaults to using the Basic network features. For more information, see [Configure network features](configure-network-features.md).
 
 * ***Standard***  
     Selecting this setting enables higher IP limits and standard VNet features such as [network security groups](../virtual-network/network-security-groups-overview.md) and [user-defined routes](../virtual-network/virtual-networks-udr-overview.md#user-defined) on delegated subnets, and additional connectivity patterns as indicated in this article.
@@ -34,7 +34,7 @@ Azure NetApp Files volumes are designed to be contained in a special purpose sub
 
 ### Supported regions 
 
-Azure NetApp Files Standard network features are supported for the following regions:
+<a name="regions-standard-network-features"></a>Azure NetApp Files *Standard network features* are supported for the following regions:
 
 *   Australia Central
 *   Australia Central 2
@@ -71,6 +71,25 @@ Azure NetApp Files Standard network features are supported for the following reg
 *   West US 2
 *	West US 3 
 
+<a name="regions-edit-network-features"></a>The option to *[edit network features for existing volumes](configure-network-features.md#edit-network-features-option-for-existing-volumes)* is supported for the following regions:
+
+*  Australia Central
+*  Australia Central 2
+*  Australia East
+*  Brazil South
+*  Canada Central
+*  East Asia
+*  Germany North
+*  Japan West
+*  Korea Central
+*  North Central US
+*  Norway East
+*  South Africa North
+*  South India
+*  Sweden Central
+*  UAE Central
+*  UAE North
+
 ## Considerations
 
 You should understand a few considerations when you plan for Azure NetApp Files network.
@@ -108,7 +127,7 @@ The following table describes the network topologies supported by each network f
 |     Connectivity to volume in a peered VNet (Same region)    |     Yes    |     Yes    |
 |     Connectivity to volume in a peered VNet (Cross region or global peering)    |     Yes*    |     No    |
 |     Connectivity to a volume over ExpressRoute gateway    |     Yes    |     Yes    |
-|     ExpressRoute (ER) FastPath    |     Yes    |     No    |
+|     [ExpressRoute (ER) FastPath](../expressroute/about-fastpath.md)    |     Yes    |     No    |
 |     Connectivity from on-premises to a volume in a spoke VNet over ExpressRoute gateway and VNet peering with gateway transit    |     Yes    |     Yes    |
 |     Connectivity from on-premises to a volume in a spoke VNet over VPN gateway    |     Yes    |     Yes    |
 |     Connectivity from on-premises to a volume in a spoke VNet over VPN gateway and VNet peering with gateway transit    |     Yes    |     Yes    |
diff --git a/articles/azure-netapp-files/configure-network-features.md b/articles/azure-netapp-files/configure-network-features.md
@@ -12,17 +12,17 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: how-to
-ms.date: 01/31/2023
+ms.date: 05/16/2023
 ms.custom: references_regions
 ms.author: anfdocs
 ---
 # Configure network features for an Azure NetApp Files volume
 
-The **Network Features** functionality enables you to indicate whether you want to use VNet features for an Azure NetApp Files volume. With this functionality, you can set the option to ***Standard*** or ***Basic***. You can specify the setting when you create a new NFS, SMB, or dual-protocol volume. See [Guidelines for Azure NetApp Files network planning](azure-netapp-files-network-topologies.md) for details about network features.
+The **Network Features** functionality enables you to indicate whether you want to use VNet features for an Azure NetApp Files volume. With this functionality, you can set the option to ***Standard*** or ***Basic***. You can specify the setting when you create a new NFS, SMB, or dual-protocol volume. You can also modify the network features option on existing volumes. See [Guidelines for Azure NetApp Files network planning](azure-netapp-files-network-topologies.md) for details about network features.
 
 This article helps you understand the options and shows you how to configure network features.
 
-The **Network Features** functionality is not available in Azure Government regions. See [supported regions](azure-netapp-files-network-topologies.md#supported-regions) for a full list. 
+The **Network Features** functionality isn't available in Azure Government regions. See [supported regions](azure-netapp-files-network-topologies.md#supported-regions) for a full list. 
 
 ## Options for network features 
 
@@ -36,29 +36,26 @@ Two settings are available for network features:
 * ***Basic***  
     This setting provides reduced IP limits (<1000) and no additional VNet features for the volumes.
 
-    You should set **Network Features** to *Basic* if you do not require VNet features.  
+    You should set **Network Features** to *Basic* if you don't require VNet features.  
 
 ## Considerations
 
-* Regardless of the Network Features option you set (*Standard* or *Basic*), an Azure VNet can only have one subnet delegated to Azure NetApp files. See [Delegate a subnet to Azure NetApp Files](azure-netapp-files-delegate-subnet.md#considerations). 
+* Regardless of the network features option you set (*Standard* or *Basic*), an Azure VNet can only have one subnet delegated to Azure NetApp files. See [Delegate a subnet to Azure NetApp Files](azure-netapp-files-delegate-subnet.md#considerations). 
  
-* Currently, you can specify the network features setting only during the creation process of a new volume. You cannot modify the setting on existing volumes. 
+* You can create or modify volumes with the Standard network features only if the corresponding [Azure region supports the Standard volume capability](azure-netapp-files-network-topologies.md#supported-regions). 
 
-* You can create volumes with the Standard network features only if the corresponding [Azure region supports the Standard volume capability](azure-netapp-files-network-topologies.md#supported-regions). 
     * If the Standard volume capability is supported for the region, the Network Features field of the Create a Volume page defaults to *Standard*. You can change this setting to *Basic*. 
-    * If the Standard volume capability is not available for the region, the Network Features field of the Create a Volume page defaults to *Basic*, and you cannot modify the setting.
+    * If the Standard volume capability isn't available for the region, the Network Features field of the Create a Volume page defaults to *Basic*, and you can't modify the setting.
 
-* The ability to locate storage compatible with the desired type of network features depends on the VNet specified. If you cannot create a volume because of insufficient resources, you can try a different VNet for which compatible storage is available.
+* The ability to locate storage compatible with the desired type of network features depends on the VNet specified. If you can't create a volume because of insufficient resources, you can try a different VNet for which compatible storage is available.
 
-* You can create Basic volumes from Basic volume snapshots and Standard volumes from Standard volume snapshots. Creating a Basic volume from a Standard volume snapshot is not supported. Creating a Standard volume from a Basic volume snapshot is not supported.
+* You can create Basic volumes from Basic volume snapshots and Standard volumes from Standard volume snapshots. Creating a Basic volume from a Standard volume snapshot isn't supported. Creating a Standard volume from a Basic volume snapshot isn't supported.
 
-* When restoring a backup to a new volume, the new volume can be configure with Basic or Standard network features. 
+* When you restore a backup to a new volume, you can configure the new volume with Basic or Standard network features. 
 
-* Conversion between Basic and Standard network features in either direction is not currently supported.
-  
-## Set the Network Features option
+## <a name="set-the-network-features-option"></a>Set network features option during volume creation
 
-This section shows you how to set the Network Features option. 
+This section shows you how to set the network features option when you create a new volume. 
 
 1. During the process of creating a new [NFS](azure-netapp-files-create-volumes.md), [SMB](azure-netapp-files-create-volumes-smb.md), or [dual-protocol](create-volumes-dual-protocol.md) volume, you can set the **Network Features** option to **Basic** or **Standard** under the Basic tab of the Create a Volume screen.
 
@@ -78,6 +75,34 @@ This section shows you how to set the Network Features option.
 
     [ ![Screenshot that shows the Volumes page displaying the network features setting.](../media/azure-netapp-files/network-features-volume-list.png)](../media/azure-netapp-files/network-features-volume-list.png#lightbox)
 
+## Edit network features option 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 NIC for mounting the volume to the client or connecting to the SMB 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.
+
+You can also revert the option from *Standard* back to *Basic* network features, but considerations apply and require careful planning. For example, you might need to change configurations for Network Security Groups (NSGs), user-defined routes (UDRs), and IP limits if you revert. 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.
+
+This feature currently doesn't support SDK.
+
+> [!IMPORTANT]
+> The option to edit network features is currently in preview. You need to submit a waitlist request for accessing the feature through the **[Azure NetApp Files standard networking features (edit volumes) Public Preview Request Form](https://aka.ms/anfeditnetworkfeaturespreview)**. This feature is expected to be enabled within a week 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
+> ```
+
+> [!IMPORTANT]
+> Updating the network features option might cause a network disruption on the volumes for up to 5 minutes. 
+
+1. Navigate to the volume that 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. 
+
+    :::image type="content" source="../media/azure-netapp-files/edit-network-features.png" alt-text="Screenshot showing the Edit Network Features window." lightbox="../media/azure-netapp-files/edit-network-features.png":::
+
 ## Next steps  
 
 * [Guidelines for Azure NetApp Files network planning](azure-netapp-files-network-topologies.md)
diff --git a/articles/azure-netapp-files/whats-new.md b/articles/azure-netapp-files/whats-new.md
@@ -21,14 +21,25 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
 ## May 2023 
 
+* [Standard network features - Edit volumes](configure-network-features.md#edit-network-features-option-for-existing-volumes) (Preview)
+
+    Azure NetApp Files volumes have been supported with Standard network features since [October 2021](#october-2021), but only for newly created volumes. This new *edit volumes* capability lets you change *existing* volumes that were configured with Basic network features to use Standard network features. This capability provides an enhanced, more standard, Azure Virtual Network (VNet) experience through various security and connectivity features that are available on Azure VNets to Azure services. When you edit existing volumes to use Standard network features, you can start taking advantage of networking capabilities, such as (but not limited to): 
+    * Increased number of client IPs in a virtual network (including immediately peered VNets) accessing Azure NetApp Files volumes - the [same as Azure VMs](azure-netapp-files-resource-limits.md#resource-limits)
+    * Enhanced network security with support for [network security groups](../virtual-network/network-security-groups-overview.md) on Azure NetApp Files delegated subnets
+    * Enhanced network control with support for [user-defined routes](../virtual-network/virtual-networks-udr-overview.md#user-defined) to and from Azure NetApp Files delegated subnets
+    * Connectivity over Active/Active VPN gateway setup
+    * [ExpressRoute FastPath](../expressroute/about-fastpath.md) connectivity to Azure NetApp Files   
+
+    This feature is now in public preview, currently available in [16 Azure regions](azure-netapp-files-network-topologies.md#regions-edit-network-features). It will roll out to other regions. Stay tuned for further information as more regions become available.
+
 * [Azure Application Consistent Snapshot tool (AzAcSnap) 8 (GA)](azacsnap-introduction.md)
 
-    Version 8 of the AzAcSnap tool is now generally available. [Azure Application Consistent Snapshot Tool](azacsnap-introduction.md) (AzAcSnap) is a command-line tool that enables customers to simplify data protection for third-party databases in Linux environments. AzAcSnap 8 introduces the following new capabilities and improvements: 
+    Version 8 of the AzAcSnap tool is now generally available. [Azure Application Consistent Snapshot Tool](azacsnap-introduction.md) (AzAcSnap) is a command-line tool that enables you to simplify data protection for third-party databases in Linux environments. AzAcSnap 8 introduces the following new capabilities and improvements: 
 
     * Restore change -  ability to revert volume for Azure NetApp Files 
-    * New global settings file (.azacsnaprc) to control behavior of azacsnap 
+    * New global settings file (`.azacsnaprc`) to control behavior of `azacsnap` 
     * Logging enhancements for failure cases and new "mainlog" for summarized monitoring 
-    * Backup (-c backup) and Details (-c details) fixes  
+    * Backup (`-c backup`) and Details (`-c details`) fixes  
 
     Download the latest release of the installer [here](https://aka.ms/azacsnapinstaller). 
 
diff --git a/articles/media/azure-netapp-files/edit-network-features.png b/articles/media/azure-netapp-files/edit-network-features.png
