Skip to content

Commit b95f1ac

Browse files
committed
reorder bullets
1 parent 2b527e6 commit b95f1ac

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-netapp-files/application-volume-group-considerations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,8 @@ This article describes the requirements and considerations you need to be aware
1414

1515
## Requirements and considerations
1616

17+
* You need to use the [manual QoS capacity pool](manage-manual-qos-capacity-pool.md) functionality.
1718
* Application volume group supports Basic and Standard network features. To use features including availability zone volume placement, use [Standard network features](azure-netapp-files-network-topologies.md).
18-
* You need to use the [manual QoS capacity pool](manage-manual-qos-capacity-pool.md) functionality.
1919
* Application volume group supports [availability zone volume placement](use-availability-zones.md) as the new default method for placement. This upgrade mitigates the need for AVset pinning and eliminates the need for proximity placement groups. With support for availability zone volume placement, you only need to select the same availability zone as the database servers. Using availability zone volume placement aligns with the Microsoft recommendation on how to deploy SAP HANA infrastructures to achieve best performance with high-availability, maximum flexibility, and simplified deployment.
2020
* If regions don't support availability zones, you can select a regional deployment or choose proximity placement groups (PPG).
2121

0 commit comments

Comments
 (0)