Skip to content

Commit af9c309

Browse files
normestanormesta
committed
Adding another cost article
1 parent b75c560 commit af9c309

File tree

3 files changed

+79
-3
lines changed

3 files changed

+79
-3
lines changed

‎articles/storage/blobs/TOC.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -513,7 +513,9 @@ items:
513513
- name: Estimates
514514
items:
515515
- name: Archive & retrieve
516-
href: cost-estimate-archive-retrieval.md
516+
href: cost-estimate-archive-retrieval.md
517+
- name: Data access from multiple regions
518+
href: cost-estimate-multi-region-access.md
517519
- name: Optimize costs
518520
items:
519521
- name: Access tiers

‎articles/storage/blobs/cost-estimate-archive-retrieval.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.author: normesta
1212

1313
# Cost estimate: Large-scale data archival and retrieval
1414

15-
This sample estimate shows the cost of to archive data and then retrieve some portion of that data before the 180 day limit.
15+
This sample estimates the cost to archive data and then retrieve some portion of that data before the 180 day limit.
1616

1717
> [!IMPORTANT]
1818
> This estimate is based on [these sample prices](blob-storage-estimate-costs.md#sample-prices). Sample prices shouldn't be used to calculate your production costs. To find official prices, see [Find the unit price for each meter](../common/storage-plan-manage-costs.md#find-the-unit-price-for-each-meter).
@@ -23,7 +23,7 @@ In this scenario you upload **2000** blobs to the archive access tier by using t
2323

2424
After **3** months, you must rehydrate **20%** of archived data for analysis. You choose to rehydrate data by setting the access tier of these blobs to the hot tier However, because that data is retrieved before 180 days, your assessed an early deletion fee.
2525

26-
The account is located in the East US region, and is configured for locally-redundant storage (LRS), and hierarchical namespaces are not enabled.
26+
The account is located in the West US region, and is configured for locally-redundant storage (LRS), and hierarchical namespaces are not enabled.
2727

2828
## Estimate
2929

‎articles/storage/blobs/cost-estimate-multi-region-access.md

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
---
2+
title: 'Cost estimate: Multiregion data access (Azure Blob Storage)'
3+
description: This article provides a sample estimate of what it might cost to ingest and access data in Azure Blob Storage from multiple Azure regions.
4+
services: storage
5+
author: normesta
6+
7+
ms.service: azure-blob-storage
8+
ms.date: 05/14/2025
9+
ms.topic: concept-article
10+
ms.author: normesta
11+
---
12+
13+
# Cost estimate: Upload and access data from multiple regions
14+
15+
This sample estimates the costs associated with uploading and downloading data from multiple Azure regions.
16+
17+
> [!IMPORTANT]
18+
> This estimate is based on [these sample prices](blob-storage-estimate-costs.md#sample-prices). Sample prices shouldn't be used to calculate your production costs. To find official prices, see [Find the unit price for each meter](../common/storage-plan-manage-costs.md#find-the-unit-price-for-each-meter).
19+
20+
## Scenario
21+
22+
In this scenario, client applications are located in different Azure regions across the continent. These client applications generate and upload **50,000** log files. Each file is **1 GB** in size. Because the account is configured for Geo-redundant storage (GRS), each file that is uploaded incurs a data transfer fee and a network bandwidth fee because data is replicated in a secondary region.
23+
24+
Client applications download about half of those log files for diagnostic analysis. However, **75%** of those client applications are not located in the same region as the storage account so they incur a data transfer fee and a network bandwidth fee for each download.
25+
26+
The account is located in the West US region and hierarchical namespaces are not enabled.
27+
28+
## Estimate
29+
30+
The following table shows the sample estimate at a glance.
31+
32+
| Cost component | Estimate |
33+
|---------------------------------------------------|-------------|
34+
| Cost of write operations | $163.80 |
35+
| Cost to transfer data out of region (replication) | $2,000 |
36+
| Cost of read operations | $110.00 |
37+
| Cost to transfer data out of region (downloads) | $750.00 |
38+
| **Total cost** | **$860.00** |
39+
40+
This sample estimate doesn't include the [cost of data storage](blob-storage-estimate-costs.md#the-cost-to-store-data) which is billed per GB.
41+
42+
## Breakdown
43+
44+
The following table shows how each cost component is calculated.
45+
46+
| Cost factor | Calculation | Value |
47+
|-------------------------------------------------------|----------------------------------------------|-------------|
48+
| PutBlock operations per blob | 1 GiB / 8-MiB block | 155 |
49+
| PutBlockList operations per blob | 1 per blob | 1 |
50+
| **Cost of write operations** | (50,000 blobs * 156) * write operation price | **$163.80** |
51+
| Data transfer fee (replication) | 50,000 GB * data transfer fee | $1,000.00 |
52+
| Network bandwidth fee (replication) | 50,000 GB * network bandwidth fee | $1,000.00 |
53+
| **Cost to transfer data out of region (replication)** | data transfer fee + network bandwidth fee | **$2,000** |
54+
| Number of read operations | 50,000 / 2 | 25,000 |
55+
| **Cost of read operations** | 25,000 GB * read operation price | **$110.00** |
56+
| Number of blobs downloaded from other regions | 25,000 * 75% | 1875 |
57+
| Data transfer fee (downloads) | 1875 * data transfer fee | $375.00 |
58+
| Network bandwidth fee (downloads) | 1875 * network bandwidth fee | $375.00 |
59+
| **Cost to transfer data out of region (download)** | data transfer fee + network bandwidth fee | **$750.00** |
60+
61+
## Factors that can impact the cost
62+
63+
The following table describes factors that can impact the cost of this scenario.
64+
65+
| Factor | Impact | Learn more |
66+
|---|---|----|
67+
| Block size | Larger block size reduces the number of write operations required to upload data. | [The cost to upload data](blob-storage-estimate-costs.md) |
68+
| Uploading data by using the Data Lake Storage endpoint | Smaller fixed block sizes of 4 MiB increases the number of write operations. | [Cost of uploading to the Data Lake Storage endpoint](azcopy-cost-estimation.md#cost-of-uploading-to-the-data-lake-storage-endpoint) |
69+
| Redundancy configuration of the account | Storage redundancy configuration impacts the cost of certain operations. For example, you could configure your account for read-access geo-zone-redundant storage (RA-GZRS) which enables clients to download from either the primary or secondary regions. However, moving the RA-GZRS changes the price of certain operations. | [Azure Storage redundancy](../common/storage-redundancy.md) |
70+
71+
## See also
72+
73+
- [Estimate the cost of archiving data](archive-cost-estimation.md)
74+
- [Plan and manage costs for Azure Blob Storage](../common/storage-plan-manage-costs.md)

0 commit comments

Comments
 (0)