Skip to content

Commit 99e35dc

Browse files
committed
Clarifying data transfer meter
1 parent c6a5722 commit 99e35dc

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/storage/common/storage-plan-manage-costs.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: storage
55
author: normesta
66
ms.service: azure-storage
77
ms.topic: concept-article
8-
ms.date: 09/10/2024
8+
ms.date: 06/12/2025
99
ms.author: normesta
1010
ms.subservice: storage-common-concepts
1111
ms.custom: subject-cost-optimization
@@ -80,7 +80,9 @@ The price that appears beside an operation type isn't the price you pay for each
8080

8181
#### Data transfer meter
8282

83-
Any data that leaves the Azure region incurs data transfer and network bandwidth charges. These charges commonly appear in scenarios where an account is configured for geo-redundant storage or when an object replication policy is configured to copy data to an account in another region. However, these charges also apply to data that is downloaded to an on-premises client. The price of network bandwidth doesn't appear in the Azure Storage pricing pages. To find the price of network bandwidth, see [Bandwidth pricing](https://azure.microsoft.com/pricing/details/data-transfers/).
83+
Any data that leaves the Azure region incurs either a data transfer or network bandwidth charge. The data transfer meter appears when an account is configured for geo-redundant storage.
84+
85+
Network bandwidth fees apply when a workload or object replication policy copies data to an account in another region. Network bandwidth fees can also appear when data that is downloaded to an on-premises client. The price of network bandwidth doesn't appear in the Azure Storage pricing pages. To find the price of network bandwidth, see [Bandwidth pricing](https://azure.microsoft.com/pricing/details/data-transfers/).
8486

8587
#### Feature-related meters
8688

0 commit comments

Comments
 (0)