Skip to content

Commit 9cc7b71

Browse files
normestanormesta
committed
Adding cost article
1 parent 5532224 commit 9cc7b71

File tree

3 files changed

+126
-7
lines changed

3 files changed

+126
-7
lines changed

‎articles/storage-actions/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,8 @@ items:
2323
href: storage-tasks/storage-task-authorization-roles.md
2424
- name: Reliability in Azure Storage Actions
2525
href: ../reliability/reliability-storage-actions.md?toc=/azure/storage-actions/toc.json
26+
- name: Costs and billing
27+
href: storage-actions-plan-manage-costs.md
2628
expanded: true
2729
- name: How-to
2830
items:

‎articles/storage-actions/overview.md

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -112,13 +112,7 @@ Azure Storage tasks are supported in the following public regions:
112112

113113
Pricing is based on the execution of storage task assignments. Each time your storage task assignment executes, you are billed a task execution instance charge. You also incur a charge based on the count of objects scanned and evaluated against the conditions of the storage task. That charge is based on a single price per million objects scanned. The final meter applies to the count of operations performed on objects in the storage account. This charge is also based on a single price per million objects. Meters are applied to each executing instance. If a storage task assignment is scheduled to execute repeatedly, then you're billed for each separate instance.
114114

115-
At the end of your billing cycle, the charges for each meter are summed. Your bill or invoice shows a section for all Azure Storage Actions costs. There's a separate line item for each meter. These charges appear in the subscription of the storage account where the task assignment is configured. To find the price of each meter, see [Azure Storage Actions Preview pricing](https://azure.microsoft.com/pricing/details/storage-actions/).
116-
117-
You can use the following formula to estimate the cost of a **each** storage task assignment execution:
118-
119-
Task execution instance charge + (Objects targeted charge * Objects targeted in millions) + (Operations invoked charge * Operations on objects in millions).
120-
121-
In addition to the Azure Storage Actions charges for the task assignment execution, you might also be billed for the cost of operations performed on the storage account. For example, if a storage task adds an index tag to a blob, then you'll incur the cost of a [Set Blob Tags](/rest/api/storageservices/set-blob-tags) operation on the target storage account.
115+
At the end of your billing cycle, the charges for each meter are summed. Your bill or invoice shows a section for all Azure Storage Actions costs. There's a separate line item for each meter. These charges appear in the subscription of the storage account where the task assignment is configured. To learn more about Azure Storage Actions billing meters along with example calculations for common scenarios, see [Plan to manage costs for Azure Storage Actions](storage-actions-plan-manage-costs.md)
122116

123117
> [!NOTE]
124118
> Pricing for Azure Storage Actions will start rolling out across the different preview regions starting from April 1, 2025. Charges for Azure Storage Actions might appear on your subscription if a task assignment was executed after the effective date. During the roll out period, charges for objects targeted and operations executed might not appear on your bill until later in the cycle. Because of this delay, your bill might seem lower than expected during the first part of the month.

‎articles/storage-actions/storage-actions-plan-manage-costs.md

Lines changed: 123 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,123 @@
1+
---
2+
title: Plan to manage costs for Azure Storage Actions
3+
description: Learn how to plan for and manage costs for Azure Storage Actions.
4+
author: normesta
5+
ms.author: normesta
6+
ms.custom: subject-cost-optimization
7+
ms.service: azure-storage-actions
8+
ms.topic: how-to
9+
ms.date: 04/01/2025
10+
---
11+
12+
# Plan to manage costs for Azure Storage Actions
13+
14+
This article describes how you plan for and manage costs for Azure Storage Actions.
15+
16+
Costs for Azure Storage Actions are only a portion of the monthly costs in your Azure bill. Although this article explains how to plan for and manage costs for Azure Storage Actions, you're billed for all Azure services and resources used in your Azure subscription, including the third-party services.
17+
18+
> [!IMPORTANT]
19+
> Azure Storage Actions is currently in PREVIEW and is available in these [regions](#supported-regions).
20+
> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
21+
22+
## Understand the full billing model for Azure Storage Actions
23+
24+
Your charged the billing meters for Storage Actions as well as the cost of operations performed on storage accounts.
25+
26+
### Azure Storage Actions meters
27+
28+
Meters apply only when a storage task assignment is executed. Validating a storage task by using the preview capability is free.
29+
30+
| Meter | Unit | Description |
31+
|---|---|---|
32+
| Task execution instance charge | Per run / per instance | This meter is applied to each storage task assignment execution. If you've schedule an assignment to run repeatedly, then this charge is incurred for each run. |
33+
| Objects targeted | Per million objects scanned and evaluated / per condition | Objects targeted are determined by the count of objects scanned and evaluated against the specified condition. This is based on the configuration of the task assignment, specifically the count of objects in the storage account under the optional prefixes selected, minus the objects under the excluded prefixes.|
34+
| Operations performed | Per million operations performed. | Operations performed are counted based on the number of API calls made on objects, including actions such as deleting, setting immutability, tagging, tiering, setting a legal hold, and other operations supported by Storage Actions.|
35+
36+
For official prices, see [Azure Storage Actions pricing](https://azure.microsoft.com/pricing/details/storage-actions/).
37+
38+
At the end of your billing cycle, the charges for each meter are summed. Your bill or invoice shows a section for all Azure Storage Actions costs. There's a separate line item for each meter. These charges appear in the subscription of the storage account where the task assignment is configured.
39+
40+
### Azure Storage account meters
41+
42+
Most actions incur charges for operations on the storage account. For example, if a storage task adds an index tag to a blob, then you'll incur the cost of a [Set Blob Tags](/rest/api/storageservices/set-blob-tags) operation on the target storage account. For information about how each Blob Storage operation maps to a price, see [Map each REST operation to a price](../storage/blobs/map-rest-apis-transaction-categories.md). To learn more about Blob Storage costs, see [Plan and manage costs for Azure Blob Storage](../storage/common/storage-plan-manage-costs.md).
43+
44+
### Examples
45+
46+
The examples in this section assume the following sample prices:
47+
48+
| Storage Action meter | price |
49+
|-----------------------------------------------------------------|---------|
50+
| Task execution instance charge | $0.25 |
51+
| Objects targeted | $.10 |
52+
| Operations performed | $1.00 |
53+
| Cost of the Set Blob Immutability Policy operation (per 10,000) | $0.0044 |
54+
| Cost of the Set Blob Tier operation (per 10,000) | $0.10 |
55+
56+
> [!IMPORTANT]
57+
> These prices are meant only as examples, and shouldn't be used to calculate your costs. For official prices, see the appropriate pricing pages.
58+
59+
#### Example: Applying an immutability policy to blobs
60+
61+
In this example, the [Set Blob Immutability Policy](/rest/api/storageservices/set-blob-immutability-policy) operation is applied to blobs that meet the conditions defined in the storage task.
62+
63+
A prefix filter narrows the scope of blobs to a single container which contains **1,000,000** blobs, but only **10%** of those blobs meet the conditions of the storage task.
64+
65+
Using sample prices, the following table estimates the cost of this storage task assignment run.
66+
67+
| Price factor | Value |
68+
|---------------------------------------------------------------------------|-------------|
69+
| **Cost of executing the storage task assignment** | **$0.25** |
70+
| Cost of targeting an individual blob (price / .10) | $0.0000001 |
71+
| **Cost to target 1,000,000 blobs** | **$0.10** |
72+
| Cost of performing a single operation (price / 1,000,000) | $0.000001 |
73+
| **Cost to perform operations on 100,000 blobs** | **$0.10** |
74+
| Price of a single Set Blob Immutability Policy operation (price / 10,000) | $0.00000044 |
75+
| **Cost to write (100,000 * price of a single write operation)** | **$0.044** |
76+
| **Total cost** | **$0.49** |
77+
78+
> [!IMPORTANT]
79+
> These prices are meant only as examples, and shouldn't be used to calculate your costs. For official prices, see the appropriate pricing pages.
80+
81+
#### Example: Transition blobs to a cooler tier
82+
83+
In this example, the [Set Blob Tier](/rest/api/storageservices/set-blob-tier) operation is applied to blobs that meet the conditions defined in the storage task.
84+
85+
The prefix filter narrows the scope of blobs to a single container which holds **100,000,000** blobs, but only **1%** of those blobs meet the conditions of the storage task.
86+
87+
The following table estimates the cost incurred by a storage task assignment instance that moves blobs from the hot tier to the cool tier.
88+
89+
| Price factor | Value |
90+
|-------------------------------------------------------------------|------------|
91+
| **Cost of executing the storage task assignment** | **$0.25** |
92+
| Cost of targeting an individual blob (price / .10) | $0.0000001 |
93+
| **Cost to target 100,000,000 blobs** | **$10.00** |
94+
| Cost of performing a single operation (price / 1,000,000) | $0.000001 |
95+
| **Cost to perform operations on 1,000,000 blobs** | **$1.00** |
96+
| Price of a single Set Blob Tier operation (price / 10,000) | $0.00001 |
97+
| **Cost to write (1,000,000 * price of a single write operation)** | **$10.00** |
98+
| **Total cost** | **$21.25** |
99+
100+
> [!IMPORTANT]
101+
> These prices are meant only as examples, and shouldn't be used to calculate your costs. For official prices, see the appropriate pricing pages.
102+
103+
### Using Azure Prepayment with Azure Storage Actions
104+
105+
You can pay for Azure Storage Actions charges with your Azure Prepayment credit. However, you can't use Azure Prepayment credit to pay for charges for third party products and services including those from the Azure Marketplace.
106+
107+
## Create budgets
108+
109+
You can create [budgets](../cost-management/tutorial-acm-create-budgets.md?WT.mc_id=costmanagementcontent_docsacmhorizontal_-inproduct-learn) to manage costs and create [alerts](../cost-management-billing/costs/cost-mgt-alerts-monitor-usage-spending.md?WT.mc_id=costmanagementcontent_docsacmhorizontal_-inproduct-learn) that automatically notify stakeholders of spending anomalies and overspending risks. Alerts are based on spending compared to budget and cost thresholds. Budgets and alerts are created for Azure subscriptions and resource groups, so they're useful as part of an overall cost monitoring strategy.
110+
111+
Budgets can be created with filters for specific resources or services in Azure if you want more granularity present in your monitoring. Filters help ensure that you don't accidentally create new resources that cost you additional money. For more information about the filter options available when you create a budget, see [Group and filter options](../cost-management-billing/costs/group-filter.md?WT.mc_id=costmanagementcontent_docsacmhorizontal_-inproduct-learn).
112+
113+
## Export cost data
114+
115+
You can also [export your cost data](../cost-management-billing/costs/tutorial-export-acm-data.md?WT.mc_id=costmanagementcontent_docsacmhorizontal_-inproduct-learn) to a storage account. This is helpful when you need or others to do additional data analysis for costs. For example, a finance teams can analyze the data using Excel or Power BI. You can export your costs on a daily, weekly, or monthly schedule and set a custom date range. Exporting cost data is the recommended way to retrieve cost datasets.
116+
117+
## Next steps
118+
119+
- Learn more about Azure Blob Storage costs meters, see [Plan and manage costs for Azure Blob Storage](../storage//common/storage-plan-manage-costs.md)
120+
- Learn [how to optimize your cloud investment with Azure Cost Management](../cost-management-billing/costs/cost-mgt-best-practices.md?WT.mc_id=costmanagementcontent_docsacmhorizontal_-inproduct-learn).
121+
- Learn more about managing costs with [cost analysis](../cost-management-billing/costs/quick-acm-cost-analysis.md?WT.mc_id=costmanagementcontent_docsacmhorizontal_-inproduct-learn).
122+
- Learn about how to [prevent unexpected costs](../cost-management-billing/understand/analyze-unexpected-charges.md?WT.mc_id=costmanagementcontent_docsacmhorizontal_-inproduct-learn).
123+

0 commit comments

Comments
 (0)