You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/configure-network-features.md
-6Lines changed: 0 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,8 +15,6 @@ The **Network Features** functionality enables you to indicate whether you want
15
15
16
16
This article helps you understand the options and shows you how to configure network features.
17
17
18
-
See [supported regions](azure-netapp-files-network-topologies.md#supported-regions) for a full list.
19
-
20
18
## Options for network features
21
19
22
20
Two settings are available for network features:
@@ -35,8 +33,6 @@ Two settings are available for network features:
35
33
36
34
* 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).
37
35
38
-
* 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).
39
-
40
36
* 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*.
41
37
* 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.
42
38
@@ -77,8 +73,6 @@ This section shows you how to set the network features option when you create a
77
73
78
74
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.
79
75
80
-
The edit network features option is available in [all regions that support Standard network features](azure-netapp-files-network-topologies.md#supported-regions).
81
-
82
76
>[!IMPORTANT]
83
77
>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).
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/whats-new.md
+13-6Lines changed: 13 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,12 @@ ms.author: anfdocs
14
14
15
15
Azure NetApp Files is updated regularly. This article provides a summary about the latest new features and enhancements.
16
16
17
+
<<<<<<< HEAD
18
+
*[Astra Storage extension for Azure Kubernetes Service (AKS)](astra-storage-extension-manage.md)
19
+
20
+
Astra Storage is a first-party [AKS extension](../aks/cluster-extensions.md) and orchestrator to manage Kubernetes workloads with Azure NetApp Files.
21
+
22
+
=======
17
23
## May 2024
18
24
19
25
*[Azure NetApp Files backup](backup-introduction.md) is now generally available (GA).
@@ -36,6 +42,7 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
36
42
37
43
Application volume group for Oracle is supported in all Azure NetApp Files-enabled regions.
38
44
45
+
>>>>>>> 7b20951a863f4a9379661018f1365f3f5af75625
39
46
## March 2024
40
47
41
48
*[Large volumes (Preview) improvement:](large-volumes-requirements-considerations.md) new minimum size of 50 TiB
@@ -84,7 +91,7 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
84
91
85
92
## January 2024
86
93
87
-
*[Standard network features - Edit volumes available in US Gov regions](azure-netapp-files-network-topologies.md#supported-regions) (Preview)
94
+
*[Standard network features - Edit volumes available in US Gov regions](azure-netapp-files-network-topologies.md) (Preview)
88
95
89
96
Azure NetApp Files now supports the capability to edit network features of existing volumes in US Gov Arizona, US Gov Texas, and US Gov Texas. This capability provides an enhanced, more standard, Microsoft Azure Virtual Network experience through various security and connectivity features that are available on Virtual Networks to Azure services. This feature is in preview in commercial and US Gov regions.
90
97
@@ -102,7 +109,7 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
102
109
103
110
Azure NetApp Files now supports a "throughput limit reached" metric for volumes. The metric is a Boolean value that denotes the volume is hitting its QoS limit. With this metric, you know whether or not to adjust volumes so they meet the specific needs of your workloads.
104
111
105
-
*[Standard network features in US Gov regions](azure-netapp-files-network-topologies.md#supported-regions) is now generally available (GA)
112
+
*[Standard network features in US Gov regions](azure-netapp-files-network-topologies.md) is now generally available (GA)
106
113
107
114
Azure NetApp Files now supports Standard network features for new volumes in US Gov Arizona, US Gov Texas, and US Gov Virginia. Standard network features provide an enhanced virtual networking experience through various features for a seamless and consistent experience with security posture of all their workloads including Azure NetApp Files.
108
115
@@ -199,7 +206,7 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
199
206
* Connectivity over Active/Active VPN gateway setup
200
207
*[ExpressRoute FastPath](../expressroute/about-fastpath.md) connectivity to Azure NetApp Files
201
208
202
-
This feature is now in public preview, currently available in [16 Azure regions](azure-netapp-files-network-topologies.md#supported-regions). It will roll out to other regions. Stay tuned for further information as more regions become available.
209
+
This feature is now in public preview, currently available in [16 Azure regions](azure-netapp-files-network-topologies.md). It will roll out to other regions. Stay tuned for further information as more regions become available.
@@ -220,7 +227,7 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
220
227
221
228
## April 2023
222
229
223
-
*[Azure Virtual WAN](configure-virtual-wan.md) is now generally available in [all regions](azure-netapp-files-network-topologies.md#supported-regions) that support standard network features
230
+
*[Azure Virtual WAN](configure-virtual-wan.md) is now generally available in [all regions](azure-netapp-files-network-topologies.md#) that support standard network features
224
231
225
232
## March 2023
226
233
@@ -276,7 +283,7 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
276
283
277
284
Azure NetApp Files now supports a lower limit of 2 TiB for capacity pool sizing with Standard network features.
278
285
279
-
You can now choose a minimum size of 2 TiB when creating a capacity pool. Capacity pools smaller than 4 TiB in size can only be used with volumes using [standard network features](configure-network-features.md#options-for-network-features). This enhancement provides a more cost effective solution for running workloads such as SAP-shared files and VDI that require lower capacity pool sizes for their capacity and performance needs. When you have less than 2-4 TiB capacity with proportional performance, this enhancement allows you to start with 2 TiB as a minimum pool size and increase with 1-TiB increments. For capacities less than 3 TiB, this enhancement saves cost by allowing you to re-evaluate volume planning to take advantage of savings of smaller capacity pools. This feature is supported in all [regions with Standard network features](azure-netapp-files-network-topologies.md#supported-regions).
286
+
You can now choose a minimum size of 2 TiB when creating a capacity pool. Capacity pools smaller than 4 TiB in size can only be used with volumes using [standard network features](configure-network-features.md#options-for-network-features). This enhancement provides a more cost effective solution for running workloads such as SAP-shared files and VDI that require lower capacity pool sizes for their capacity and performance needs. When you have less than 2-4 TiB capacity with proportional performance, this enhancement allows you to start with 2 TiB as a minimum pool size and increase with 1-TiB increments. For capacities less than 3 TiB, this enhancement saves cost by allowing you to re-evaluate volume planning to take advantage of savings of smaller capacity pools. This feature is supported in all [regions with Standard network features](azure-netapp-files-network-topologies.md).
280
287
281
288
## December 2022
282
289
@@ -333,7 +340,7 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
333
340
334
341
## August 2022
335
342
336
-
*[Standard network features](configure-network-features.md) are now generally available [in supported regions](azure-netapp-files-network-topologies.md#supported-regions).
343
+
*[Standard network features](configure-network-features.md) are now generally available [in supported regions](azure-netapp-files-network-topologies.md).
337
344
338
345
Standard network features now includes Global virtual network peering.
0 commit comments