Skip to content

Commit eedcc92

Browse files
Stacyrch140Stacyrch140
authored
Merge pull request #299502 from normesta/cost-scenario-prototype
Cost estimates
2 parents 8bf3503 + b9977e0 commit eedcc92

6 files changed

+224
-14
lines changed

‎articles/storage/blobs/TOC.yml

Lines changed: 16 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -513,12 +513,22 @@ items:
513513
href: map-rest-apis-transaction-categories.md
514514
- name: Estimate costs
515515
items:
516-
- name: Estimate the cost of Azure Blob Storage
517-
href: blob-storage-estimate-costs.md
518-
- name: Estimate the cost of AzCopy transfers
519-
href: azcopy-cost-estimation.md
520-
- name: Estimate the cost to archive data
521-
href: archive-cost-estimation.md
516+
- name: Guides
517+
items:
518+
- name: Estimate the cost of Azure Blob Storage
519+
href: blob-storage-estimate-costs.md
520+
- name: Estimate the cost of AzCopy transfers
521+
href: azcopy-cost-estimation.md
522+
- name: Estimate the cost to archive data
523+
href: archive-cost-estimation.md
524+
- name: Estimates
525+
items:
526+
- name: Rehydrate from archive by setting tiers
527+
href: cost-estimate-archive-retrieval-set-tier.md
528+
- name: Rehydrate from archive by copying blobs
529+
href: cost-estimate-archive-retrieval-copy-blob.md
530+
- name: Cross region data access
531+
href: cost-estimate-multi-region-access.md
522532
- name: Optimize costs
523533
items:
524534
- name: Access tiers

‎articles/storage/blobs/archive-rehydrate-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -106,9 +106,9 @@ For more information on handling events in Blob Storage, see [Reacting to Azure
106106

107107
## Pricing and billing
108108

109-
A rehydration operation with [Set Blob Tier](/rest/api/storageservices/set-blob-tier) is billed for data read transactions and data retrieval size. A high-priority rehydration has higher operation and data retrieval costs compared to standard priority. High-priority rehydration shows up as a separate line item on your bill. If a high-priority request to return an archived blob that is less than 10 GB in size takes more than five hours, you won't be charged the high-priority retrieval rate. However, standard retrieval rates still apply.
109+
A rehydration operation with [Set Blob Tier](/rest/api/storageservices/set-blob-tier) is billed for data read transactions and data retrieval size. A high-priority rehydration has higher operation and data retrieval costs compared to standard priority. High-priority rehydration shows up as a separate line item on your bill. If a high-priority request to return an archived blob that is less than 10 GB in size takes more than five hours, you won't be charged the high-priority retrieval rate. However, standard retrieval rates still apply. For a sample cost estimate, see [Cost estimate: Move data out of archive storage](cost-estimate-archive-retrieval-set-tier.md).
110110

111-
Copying an archived blob to an online tier with [Copy Blob](/rest/api/storageservices/copy-blob) is billed for data read transactions and data retrieval size. Creating the destination blob in an online tier is billed for data write transactions. Early deletion fees don't apply when you copy to an online blob because the source blob remains unmodified in the archive tier. High-priority retrieval charges do apply if selected.
111+
Copying an archived blob to an online tier with [Copy Blob](/rest/api/storageservices/copy-blob) is billed for data read transactions and data retrieval size. Creating the destination blob in an online tier is billed for data write transactions. Early deletion fees don't apply when you copy to an online blob because the source blob remains unmodified in the archive tier. High-priority retrieval charges do apply if selected. For a sample estimate, see [Cost estimate: Retrieve data from archive storage for analysis](cost-estimate-archive-retrieval-copy-blob.md).
112112

113113
Blobs in the archive tier should be stored for a minimum of 180 days. Deleting or changing the tier of an archived blob before the 180-day period elapses incurs an early deletion fee. For example, if a blob is moved to the archive tier and then deleted or moved to the hot tier after 45 days, you'll be charged an early deletion fee equivalent to 135 (180 minus 45) days of storing that blob in the archive tier. For more information, see [Archive access tier](access-tiers-overview.md#archive-access-tier).
114114

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

Lines changed: 68 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
---
2+
title: 'Cost estimate: Analyze archived data (Azure Blob Storage)'
3+
description: This article shows an example of what it costs to retrieve and analyze archived data in Azure Blob Storage.
4+
services: storage
5+
author: normesta
6+
7+
ms.service: azure-blob-storage
8+
ms.date: 06/13/2025
9+
ms.topic: concept-article
10+
ms.author: normesta
11+
---
12+
13+
# Cost estimate: Retrieve data from archive storage for analysis
14+
15+
This sample estimates the cost to retrieve a portion of data from the archive tier before the 180 day limit.
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+
Your company stores 20 TB of data in the archive tier for long term retention. However, after only three months in archive storage, 20% of that data must be retrieved for analysis. You're asked to estimate the cost to get that data from archive storage and then download that data to clients.
23+
24+
Because the data is needed only temporarily, you decide not to rehydrate blobs by changing their tier. That way, your company avoids the early deletion fee. You already estimated the cost of that approach by reviewing the [Cost estimate: Move data out of archive storage](cost-estimate-archive-retrieval-set-tier.md) article. Instead, you decide that it's more cost-effective to copy blobs into the hot tier for analysis. You know that data in the hot tier can be deleted at no charge when the analysis is complete.
25+
26+
The storage account is located in the West US region, is configured for locally-redundant storage (LRS), and doesn't have hierarchical namespaces.
27+
28+
## Costs
29+
30+
The following table describes each cost.
31+
32+
| Cost | Description |
33+
|----|----|
34+
| **Copy blobs to the hot tier** | First, blobs must be moved out of archive storage for analysis. All tools and SDKs use the [Copy Blob](/rest/api/storageservices/copy-blob) operation to accomplish this task. The [Copy Blob](/rest/api/storageservices/copy-blob) operation is billed as a read operation on the source account and a write operation on the destination account. |
35+
| **Data retrieval fee** | This meter applies to each GB moved from the archive tier and into an online tier such as the hot tier. |
36+
| **Read from the hot tier** | Once data is moved into the hot tier, clients need to download that data. Each download is billed as a read operation. |
37+
38+
## Estimate
39+
40+
Based on [these sample prices](blob-storage-estimate-costs.md#sample-prices), the following table shows how each cost component is calculated. 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+
| Cost | Cost factor | Calculation | Value |
43+
|--------------------------------|--------------------------------------------|---------------------------------------|-------------|
44+
| **Copy blobs to the hot tier** | Number of Copy Blob operations | 2000 blobs * 20% | 400 |
45+
| | Price of an archive read operation | | $0.00055 |
46+
| | Cost to read from the archive | 400 operations * $0.00055 | $0.22 |
47+
| | Price of a hot tier write operation | | $0.0000055 |
48+
| | Cost to write to the hot tier | 400 operations * $0.0000055 | $0.0022 |
49+
| | **Cost to copy blobs to hot tier**<br><br> | $0.22 + $0.0022 | **$0.22** |
50+
| **Data retrieval fee** | Total file size | | 20,000 GB |
51+
| | Data retrieval size | 20,000 GB * 20% | 4,000 |
52+
| | Price of data retrieval (per GB) | | $0.0220 |
53+
| | **Cost to retrieve**<br></br> | 4,000 blobs * $0.0220 | **$88.00** |
54+
| **Read from hot tier** | Number of read operations on hot tier | The number of blobs moved to hot tier | 400 |
55+
| | Price of a read operation on the hot tier | | $0.00000044 |
56+
| | **Cost to read from hot tier**<br></br> | 400 operations * $0.00000044 | **$0.0002** |
57+
| **Total cost** | | $0.22 + $88 + $24 + $0.0002 | **$88.22** |
58+
59+
> [!TIP]
60+
> This scenario doesn't model the amount of time that data exists in the storage, so the table doesn't include [cost of data storage](blob-storage-estimate-costs.md#the-cost-to-store-data) which is billed per GB. You can estimate the cost storage and the cost of transactions in your environment by using [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator/).
61+
62+
## See also
63+
64+
- [Cost estimate: Move data out of archive storage](cost-estimate-archive-retrieval-set-tier.md)
65+
- [Estimate the cost of archiving data](archive-cost-estimation.md)
66+
- [Estimate the cost of using Azure Blob Storage](blob-storage-estimate-costs.md)
67+
- [Estimate the cost of using AzCopy to transfer blobs](azcopy-cost-estimation.md)
68+
- [Plan and manage costs for Azure Blob Storage](../common/storage-plan-manage-costs.md)

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

Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
---
2+
title: 'Cost estimate: Move data from archive (Azure Blob Storage)'
3+
description: This article shows an example of what it costs to move data out of archive storage.
4+
services: storage
5+
author: normesta
6+
7+
ms.service: azure-blob-storage
8+
ms.date: 06/13/2025
9+
ms.topic: concept-article
10+
ms.author: normesta
11+
---
12+
13+
# Cost estimate: Move data out of archive storage
14+
15+
This sample estimates the cost to move a portion of data from the archive tier to the hot tier before the 180 day limit.
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+
Your company stores 20 TB of data in the archive tier for long term retention. However, after only three months in archive storage, 20% of that data must be moved back to the hot tier. You are asked to estimate the cost to get that data from archive storage.
23+
24+
The storage account is located in the West US region, is configured for locally-redundant storage (LRS), and doesn't have hierarchical namespaces.
25+
26+
## Costs
27+
28+
The following table describes each cost.
29+
30+
| Cost | Description |
31+
|----|----|
32+
| **Change tier to hot** | First, blobs must be moved out of archive storage. To do this, administrators change the tier of each blob from `archive` to `hot`. All tools and SDKs use the [Set Blob Tier](/rest/api/storageservices/set-blob-tier) operation to accomplish this task. That operation is billed as a read operation on the archive tier. |
33+
| **Data retrieval fee** | This meter applies to each GB moved from the archive tier and into an online tier such as the hot tier. |
34+
| **Early deletion fee** | If data is moved out of the archive tier before 180 days have transpired, a prorated early deletion fee is applied to the bill. |
35+
36+
## Estimate
37+
38+
Based on [these sample prices](blob-storage-estimate-costs.md#sample-prices), the following table shows how each cost component is calculated.
39+
40+
| Cost | Cost factor | Calculation | Value |
41+
|------------------------|---------------------------------------------|--------------------------------|-------------|
42+
| **Change tier to hot** | Number of Set Blob Tier operations | 2000 blobs * 20% | 400 |
43+
| | Price of an archive read operation | | $0.00055 |
44+
| | **Cost to change tier to hot**<br></br> | 400 operations * $0.00055 | **$0.22** |
45+
| **Data retrieval fee** | Total file size | | 20,000 GB |
46+
| | Data retrieval size | 20,000 GB * 20% | 4,000 |
47+
| | Price of data retrieval (per GB) | | $0.0220 |
48+
| | **Cost to retrieve**<br></br> | 4,000 blobs * $0.0220 | **$88.00** |
49+
| **Early deletion fee** | Rough number of months penalty | (180 days - 90 days) / 30 days | 3 |
50+
| | Price per month of archive storage (per GB) | | $0.0020 |
51+
| | **Cost of early deletion**<br></br> | (4,000 blobs * $0.0020) * 3 | **$24.00** |
52+
| **Total cost** | | $0.22 + $88 + $24 | **$112.22** |
53+
54+
> [!TIP]
55+
> This scenario doesn't model the amount of time that data exists in storage, so the table doesn't include [cost of data storage](blob-storage-estimate-costs.md#the-cost-to-store-data) which is billed per GB. You can estimate the cost storage and the cost of transactions in your environment by using [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator/).
56+
57+
## See also
58+
59+
- [Cost estimate: Retrieve data from archive storage for analysis](cost-estimate-archive-retrieval-copy-blob.md)
60+
- [Estimate the cost of archiving data](archive-cost-estimation.md)
61+
- [Estimate the cost of using Azure Blob Storage](blob-storage-estimate-costs.md)
62+
- [Estimate the cost of using AzCopy to transfer blobs](azcopy-cost-estimation.md)
63+
- [Plan and manage costs for Azure Blob Storage](../common/storage-plan-manage-costs.md)

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

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
---
2+
title: 'Cost estimate: Cross region 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: 06/13/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 cost to upload and download 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+
Your company plans to distribute a new client application to users located in multiple Azure regions across the continent. This application is used to upload log files and download them for diagnostic analysis. Files are stored as blobs in the hot access tier. Based on expected usage patterns, you've been asked to create a rough estimate of costs.
23+
24+
The storage account is located in the West US region, is configured for Geo-redundant storage (GRS) and doesn't have hierarchical namespaces enabled.
25+
26+
## Costs
27+
28+
The following table describes each cost.
29+
30+
| Cost | Description |
31+
|----|----|
32+
| **Cost to write** | During this quarter, clients upload an estimated **50,000** log files (roughly **1 GB** each in size). Clients are configured to upload those log files in 8-MiB blocks. Each block is billed as a write operation with one additional operation to commit those blocks. A smaller block size is performant, but you know that a larger block size results in fewer write operations so you plan to include that suggestion along with your estimate. |
33+
| **Cost of replication** | Because the account is configured for geo-redundant storage, all blobs are replicated to a secondary region. This replication process adds a data transfer fee per GB replicated.|
34+
| **Cost to read** | Any blob that is downloaded for diagnostic analysis is billed as a read operation. You believe that client applications will download about half of the files uploaded for diagnostic analysis. You also learn that **75%** of client applications aren't located in the same region as the storage account. Therefore, blobs downloaded by those clients incur a network bandwidth fee. |
35+
36+
## Estimate
37+
38+
Based on [these sample prices](blob-storage-estimate-costs.md#sample-prices), the following table shows how each cost component is calculated.
39+
40+
| Cost | Cost factor | Calculation | Value |
41+
|-------------------------|-----------------------------------------------|----------------------------------|---------------|
42+
| **Cost to write** | PutBlock operations per blob | 1 GiB / 8-MiB block | 155 |
43+
| | PutBlockList operations per blob | 1 per blob | 1 |
44+
| | Price of a write operation on the hot tier | | $0.000021 |
45+
| | **Cost to upload log files**<br></br> | (50,000 blobs * 156) * $0.000021 | **$163.80** |
46+
| **Cost of replication** | Price of data transfer (per GB) | | $0.02 |
47+
| | **Cost to replicate**<br><br> | 50,000 GB * $0.02 | **$1,000.00** |
48+
| **Cost to read** | Number of read operations | 50,000 / 2 | 25,000 |
49+
| | Price a read operation on the hot tier | | $0.00440 |
50+
| | Cost of read operations<br></br> | 25,000 GB * $0.00440 | $110.00 |
51+
| | Number of blobs downloaded from other regions | 25,000 * 75% | 1875 |
52+
| | Network bandwidth fee | 1875 * $0.02 | $375.00 |
53+
| | **Cost to read**<br><br> | $110 + $375 | **$485** |
54+
| **Total cost** | | $163.80 + $1,000 + $485 | **$1,648.80** |
55+
56+
> [!TIP]
57+
> This scenario doesn't model the amount of time that data exists in storage, so the table doesn't include [cost of data storage](blob-storage-estimate-costs.md#the-cost-to-store-data) which is billed per GB. You can estimate the cost storage and the cost of transactions in your environment by using [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator/).
58+
59+
## See also
60+
61+
- [Estimate the cost of using Azure Blob Storage](blob-storage-estimate-costs.md)
62+
- [Estimate the cost of using AzCopy to transfer blobs](azcopy-cost-estimation.md)
63+
- [Estimate the cost of archiving data](archive-cost-estimation.md)
64+
- [Plan and manage costs for Azure Blob Storage](../common/storage-plan-manage-costs.md)

0 commit comments

Comments
 (0)