Skip to content

Commit 72717ab

Browse files
committed
issue #100369
1 parent 0748e50 commit 72717ab

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-netapp-files/manage-availability-zone-volume-placement.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
1212
ms.workload: storage
1313
ms.tgt_pltfrm: na
1414
ms.topic: how-to
15-
ms.date: 10/20/2022
15+
ms.date: 10/24/2022
1616
ms.author: anfdocs
1717
---
1818
# Manage availability zone volume placement for Azure NetApp Files
@@ -29,7 +29,7 @@ Azure NetApp Files lets you deploy new volumes in the logical availability zone
2929

3030
* NetApp accounts and capacity pools are not bound by the availability zone. A capacity pool can contain volumes in different availability zones.
3131

32-
* This feature provides zonal volume placement, with latency within the zonal latency envelopes. It does not provide proximity placement towards compute. As such, it doesn’t provide lowest latency guarantee.
32+
* This feature provides zonal volume placement, with latency within the zonal latency envelopes. It ***does not*** provide proximity placement towards compute. As such, it ***does not*** provide lowest latency guarantee.
3333

3434
* Each data center is assigned to a physical zone. Physical zones are mapped to logical zones in your Azure subscription. Azure subscriptions are automatically assigned this mapping at the time a subscription is created. This feature aligns with the generic logical-to-physical availability zone mapping for the subscription.
3535

0 commit comments

Comments
 (0)