Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

Discover secure, future-ready cloud solutions—on-premises, hybrid, multicloud, or at the edge

Learn about sustainable, trusted cloud infrastructure with more regions than any other provider

Build your business case for the cloud with key financial and technical guidance from Azure

Plan a clear path forward for your cloud journey with proven tools, guidance, and resources

See examples of innovation from successful companies of all sizes and from all industries

Azure Data Manager for Agriculture extends the Microsoft Intelligent Data Platform with industry-specific data connectors and capabilities to bring together farm data from disparate sources, enabling organizations to leverage high quality datasets and accelerate the development of digital agriculture solutions

Build, manage, and continuously deliver cloud apps—with any platform or language

Analyze images, comprehend speech, and make predictions using data

Simplify and accelerate your migration and modernization with guidance, tools, and resources

Gather, store, process, analyze, and visualize data of any variety, volume, or velocity

Bring the agility and innovation of the cloud to your on-premises workloads

Connect, monitor, and control devices with secure, scalable, and open edge-to-cloud solutions

Help protect data, apps, and infrastructure with trusted security services

Transform customer experience, build trust, and optimize risk management

Build, quickly launch, and reliably scale your games across platforms

Implement remote government access, empower collaboration, and deliver secure services

Boost patient engagement, empower provider collaboration, and improve operations

Improve operational efficiencies, reduce costs, and generate new revenue opportunities

Create content nimbly, collaborate remotely, and deliver seamless customer experiences

Personalize customer experiences, empower your employees, and optimize supply chains

Find reference architectures, example scenarios, and solutions for common workloads on Azure

Do more with less—explore resources for increasing efficiency, reducing costs, and driving innovation

Search from a rich catalog of more than 17,000 certified apps and services

Plan a clear path forward for your cloud journey with proven tools, guidance, and resources

Find the latest content, news, and guidance to lead customers to the cloud

Build, extend, and scale your apps on a trusted cloud platform

Reach more customers—sell directly to over 4M users a month in the commercial marketplace

Block blob storage is used for streaming and storing documents, videos, pictures, backups, and other unstructured text or binary data.

Total cost of block blob storage depends on:

• Volume of data stored per month.
• Quantity and types of operations performed, along with any data transfer costs.
• Data redundancy option selected.

Prices are estimates only and are not intended as actual price quotes. Actual pricing may vary depending on the type of agreement entered with Microsoft, date of purchase, and the currency exchange rate. Prices are calculated based on US dollars and converted using Thomson Reuters benchmark rates refreshed on the first day of each calendar month. Sign in to the Azure pricing calculator to see pricing based on your current program/offer with Microsoft. Contact an Azure sales specialist for more information on pricing or to request a price quote. For more information on Azure pricing see frequently asked questions .

US government entities are eligible to purchase Azure Government services from a licensing solution provider with no upfront financial commitment, or directly through a pay-as-you-go online subscription.

Learn more

US government entities are eligible to purchase Azure Government services from a licensing solution provider with no upfront financial commitment, or directly through a pay-as-you-go online subscription.

Learn more

Azure Storage Reserved Capacity

Azure Storage Reserved Capacity helps you lower your data storage cost by committing to one-year or three-years of Azure Storage. Reserved capacity can be purchased in increments of 100 TB and 1 PB sizes for 1-year and 3-year commitment duration. All prices are per month. For more information, please see documentation .

Cool and Archive early deletion

In addition to the per-GB, per-month charge, any blob that is moved to the Archive tier is subject to an Archive early deletion period of 180 days. Additionally, for general-purpose v2 storage accounts, any blob that is moved to the Cool tier is subject to a Cool tier early deletion period of 30 days. This charge is prorated. For example, if a blob is moved to the Archive tier and then deleted or moved to the Hot tier after 45 days, the customer is charged an early deletion fee for 135 (180 minus 45) days of storage in the Archive tier.

Operations and data transfer

¹ The following API calls are considered write operations: PutBlob, PutBlock, PutBlockList, AppendBlock, SnapshotBlob, CopyBlob, and SetBlobTier (when it moves a Blob from Hot to Cool, Cool to Archive, or Hot to Archive. Learn more ).

² The following API calls are considered list and create container operations: ListBlobs, ListContainers, FindBlobsByTags, and CreateContainer.

³ The following API calls are considered read operations: GetBlob and SetBlobTier (when it moves a Blob from Archive to Cool, Cool to Hot, or Archive to Hot. Learn more ).

⁴ Network costs are charged separately.

⁵ High Priority requests are for Archive only and can be used to rehydrate small objects in under 1 hour. Learn more about High Priority Archive rehydrate .

For blobs in Archive, the only valid operations are GetBlobProperties, GetBlobMetadata, ListBlobs, SetBlobTier, SetBlobTags, GetBlobTags, FindBlobsByTags, DeleteBlob, and CopyBlob. Setting the tier from Archive to Hot or Cool typically takes up to 15 hours to complete. Learn more .

¹ The following API calls are considered write operations: PutBlob, PutBlock, PutBlockList, AppendBlock, SnapshotBlob, CopyBlob, and SetBlobTier (when it moves a Blob from Hot to Cool, Cool to Archive, or Hot to Archive. Learn more ).

² The following API calls are considered list and create container operations: ListBlobs, ListContainers, FindBlobsByTags, and CreateContainer.

³ The following API calls are considered read operations: GetBlob and SetBlobTier (when it moves a Blob from Archive to Cool, Cool to Hot, or Archive to Hot. Learn more ).

⁴ Network costs are charged separately.

⁵ High Priority requests are for Archive only and can be used to rehydrate small objects in under 1 hour. Learn more about High Priority Archive rehydrate .

For blobs in Archive, the only valid operations are GetBlobProperties, GetBlobMetadata, ListBlobs, SetBlobTier, SetBlobTags, GetBlobTags, FindBlobsByTags, DeleteBlob, and CopyBlob. Setting the tier from Archive to Hot or Cool typically takes up to 15 hours to complete. Learn more .

¹ The following API calls are considered write operations: PutBlob, PutBlock, PutBlockList, AppendBlock, SnapshotBlob, CopyBlob, and SetBlobTier (when it moves a Blob from Hot to Cool, Cool to Archive, or Hot to Archive. Learn more ).

² The following API calls are considered list and create container operations: ListBlobs, ListContainers, FindBlobsByTags, and CreateContainer.

³ The following API calls are considered read operations: GetBlob and SetBlobTier (when it moves a Blob from Archive to Cool, Cool to Hot, or Archive to Hot. Learn more ).

⁴ Network costs are charged separately.

⁵ High Priority requests are for Archive only and can be used to rehydrate small objects in under 1 hour. Learn more about High Priority Archive rehydrate .

For blobs in Archive, the only valid operations are GetBlobProperties, GetBlobMetadata, ListBlobs, SetBlobTier, SetBlobTags, GetBlobTags, FindBlobsByTags, DeleteBlob, and CopyBlob. Setting the tier from Archive to Hot or Cool typically takes up to 15 hours to complete. Learn more .

¹ The following API calls are considered write operations: PutBlob, PutBlock, PutBlockList, AppendBlock, SnapshotBlob, CopyBlob, and SetBlobTier (when it moves a Blob from Hot to Cool, Cool to Archive, or Hot to Archive. Learn more ).

² The following API calls are considered list and create container operations: ListBlobs, ListContainers, FindBlobsByTags, and CreateContainer.

³ The following API calls are considered read operations: GetBlob and SetBlobTier (when it moves a Blob from Archive to Cool, Cool to Hot, or Archive to Hot. Learn more ).

⁴ Network costs are charged separately.

⁵ High Priority requests are for Archive only and can be used to rehydrate small objects in under 1 hour. Learn more about High Priority Archive rehydrate .

For blobs in Archive, the only valid operations are GetBlobProperties, GetBlobMetadata, ListBlobs, SetBlobTier, SetBlobTags, GetBlobTags, FindBlobsByTags, DeleteBlob, and CopyBlob. Setting the tier from Archive to Hot or Cool typically takes up to 15 hours to complete. Learn more .

¹ The following API calls are considered write operations: PutBlob, PutBlock, PutBlockList, AppendBlock, SnapshotBlob, CopyBlob, and SetBlobTier (when it moves a Blob from Hot to Cool, Cool to Archive, or Hot to Archive. Learn more ).

² The following API calls are considered list and create container operations: ListBlobs, ListContainers, FindBlobsByTags, and CreateContainer.

³ The following API calls are considered read operations: GetBlob and SetBlobTier (when it moves a Blob from Archive to Cool, Cool to Hot, or Archive to Hot. Learn more ).

⁴ Network costs are charged separately.

⁵ High Priority requests are for Archive only and can be used to rehydrate small objects in under 1 hour. Learn more about High Priority Archive rehydrate .

For blobs in Archive, the only valid operations are GetBlobProperties, GetBlobMetadata, ListBlobs, SetBlobTier, SetBlobTags, GetBlobTags, FindBlobsByTags, DeleteBlob, and CopyBlob. Setting the tier from Archive to Hot or Cool typically takes up to 15 hours to complete. Learn more .

¹ The following API calls are considered write operations: PutBlob, PutBlock, PutBlockList, AppendBlock, SnapshotBlob, CopyBlob, and SetBlobTier (when it moves a Blob from Hot to Cool, Cool to Archive, or Hot to Archive. Learn more ).

² The following API calls are considered list and create container operations: ListBlobs, ListContainers, FindBlobsByTags, and CreateContainer.

³ The following API calls are considered read operations: GetBlob and SetBlobTier (when it moves a Blob from Archive to Cool, Cool to Hot, or Archive to Hot. Learn more ).

⁴ Network costs are charged separately.

⁵ High Priority requests are for Archive only and can be used to rehydrate small objects in under 1 hour. Learn more about High Priority Archive rehydrate .

For blobs in Archive, the only valid operations are GetBlobProperties, GetBlobMetadata, ListBlobs, SetBlobTier, SetBlobTags, GetBlobTags, FindBlobsByTags, DeleteBlob, and CopyBlob. Setting the tier from Archive to Hot or Cool typically takes up to 15 hours to complete. Learn more .

¹ The following API calls are considered write operations: AppendFile, CreateFilesystem, CreatePath, CreatePathFile, FlushFile, SetFileProperties, SetFilesystemProperties, RenameFile, RenamePathFile, CopyFile

² The following API calls are considered read operations: ReadFile, ListFilesystemFile

³ The following API calls are considered iterative read operations: List Filesystem & List Path

⁴ The following API calls are considered iterative write operations: RenameDirectory, RenamePath, RenamePathDir

⁵ Additional cross-region data transfer network changes may apply based on source/destination of each storage access. Learn more at the Bandwidth pricing page

For blobs in Archive, the only valid operations are GetBlobProperties, GetBlobMetadata, ListBlobs, SetBlobTier, SetBlobTags, GetBlobTags, FindBlobsByTags, DeleteBlob, and CopyBlob. Setting the tier from Archive to Hot or Cool typically takes up to 15 hours to complete. Learn more .

¹ The following API calls are considered write operations: AppendFile, CreateFilesystem, CreatePath, CreatePathFile, FlushFile, SetFileProperties, SetFilesystemProperties, RenameFile, RenamePathFile, CopyFile

² The following API calls are considered read operations: ReadFile, ListFilesystemFile

³ The following API calls are considered iterative read operations: List Filesystem & List Path

⁴ The following API calls are considered iterative write operations: RenameDirectory, RenamePath, RenamePathDir

⁵ Additional cross-region data transfer network changes may apply based on source/destination of each storage access. Learn more at the Bandwidth pricing page

For blobs in Archive, the only valid operations are GetBlobProperties, GetBlobMetadata, ListBlobs, SetBlobTier, SetBlobTags, GetBlobTags, FindBlobsByTags, DeleteBlob, and CopyBlob. Setting the tier from Archive to Hot or Cool typically takes up to 15 hours to complete. Learn more .

¹ The following API calls are considered write operations: AppendFile, CreateFilesystem, CreatePath, CreatePathFile, FlushFile, SetFileProperties, SetFilesystemProperties, RenameFile, RenamePathFile, CopyFile

² The following API calls are considered read operations: ReadFile, ListFilesystemFile

³ The following API calls are considered iterative read operations: List Filesystem & List Path

⁴ The following API calls are considered iterative write operations: RenameDirectory, RenamePath, RenamePathDir

⁵ Additional cross-region data transfer network changes may apply based on source/destination of each storage access. Learn more at the Bandwidth pricing page

For blobs in Archive, the only valid operations are GetBlobProperties, GetBlobMetadata, ListBlobs, SetBlobTier, SetBlobTags, GetBlobTags, FindBlobsByTags, DeleteBlob, and CopyBlob. Setting the tier from Archive to Hot or Cool typically takes up to 15 hours to complete. Learn more .

¹ The following API calls are considered write operations: AppendFile, CreateFilesystem, CreatePath, CreatePathFile, FlushFile, SetFileProperties, SetFilesystemProperties, RenameFile, RenamePathFile, CopyFile

² The following API calls are considered read operations: ReadFile, ListFilesystemFile

³ The following API calls are considered iterative read operations: List Filesystem & List Path

⁴ The following API calls are considered iterative write operations: RenameDirectory, RenamePath, RenamePathDir

⁵ Additional cross-region data transfer network changes may apply based on source/destination of each storage access. Learn more at the Bandwidth pricing page

For blobs in Archive, the only valid operations are GetBlobProperties, GetBlobMetadata, ListBlobs, SetBlobTier, SetBlobTags, GetBlobTags, FindBlobsByTags, DeleteBlob, and CopyBlob. Setting the tier from Archive to Hot or Cool typically takes up to 15 hours to complete. Learn more .

¹ The following API calls are considered write operations: AppendFile, CreateFilesystem, CreatePath, CreatePathFile, FlushFile, SetFileProperties, SetFilesystemProperties, RenameFile, RenamePathFile, CopyFile

² The following API calls are considered read operations: ReadFile, ListFilesystemFile

³ The following API calls are considered iterative read operations: List Filesystem & List Path

⁴ The following API calls are considered iterative write operations: RenameDirectory, RenamePath, RenamePathDir

⁵ Additional cross-region data transfer network changes may apply based on source/destination of each storage access. Learn more at the Bandwidth pricing page

For blobs in Archive, the only valid operations are GetBlobProperties, GetBlobMetadata, ListBlobs, SetBlobTier, SetBlobTags, GetBlobTags, FindBlobsByTags, DeleteBlob, and CopyBlob. Setting the tier from Archive to Hot or Cool typically takes up to 15 hours to complete. Learn more .

¹ The following API calls are considered write operations: AppendFile, CreateFilesystem, CreatePath, CreatePathFile, FlushFile, SetFileProperties, SetFilesystemProperties, RenameFile, RenamePathFile, CopyFile

² The following API calls are considered read operations: ReadFile, ListFilesystemFile

³ The following API calls are considered iterative read operations: List Filesystem & List Path

⁴ The following API calls are considered iterative write operations: RenameDirectory, RenamePath, RenamePathDir

⁵ Additional cross-region data transfer network changes may apply based on source/destination of each storage access. Learn more at the Bandwidth pricing page

For blobs in Archive, the only valid operations are GetBlobProperties, GetBlobMetadata, ListBlobs, SetBlobTier, SetBlobTags, GetBlobTags, FindBlobsByTags, DeleteBlob, and CopyBlob. Setting the tier from Archive to Hot or Cool typically takes up to 15 hours to complete. Learn more .

Blob Index

Blob Index is an intelligent data sub-resource for blob; consisting of user-defined key/value tag attributes that are automatically indexed for querying. This provides a managed multi-dimensional classification for your blob objects, allowing for quick, simple, and cost-effective data discovery capabilities beyond listing by prefix filters on blob name. Learn more about the feature at blob documentation .

Data transfer prices for block blobs (per GB)

When you write data to a GRS, RA-GRS, GZRS, or RA-GZRS account, the data is replicated to another Azure region. The geo-replication data transfer charge is for bandwidth used to replicate data to the second Azure region. This charge also applies when you change the storage account's replication setting from LRS to GRS or RA-GRS or from ZRS to GZRS or RA-GZRS.

GZRS, or RA-GZRS are not currently available for Premium Block Blobs

Blob storage accounts provide access to the latest features, but not to page blobs, files, queues, or tables. Using general-purpose v2 storage accounts is recommended for most users.

Data storage prices pay-as-you-go

All prices are per GB per month.

Azure Storage Reserved Capacity

Azure Storage Reserved Capacity helps you lower your data storage cost by committing to one-year or three-years of Azure Storage. Reserved capacity can be purchased in increments of 100 TB and 1 PB sizes for 1-year and 3-year commitment duration. All prices are per month. For more information, please see documentation .

Archive early deletion

In addition to the per-GB, per-month charge, any blob that is moved to Archive is subject to an Archive early deletion period of 180 days. This charge is prorated. For example, if a blob is moved to Archive and then deleted or moved to the Hot tier after 45 days, the customer is charged an early deletion fee equivalent to 135 (180 minus 45) days of storing that blob in Archive.

Operations and data transfer

¹ The following API calls are considered write operations: PutBlob, PutBlock, PutBlockList, AppendBlock, SnapshotBlob, CopyBlob, and SetBlobTier (when it moves a Blob from Hot to Cool, Cool to Archive, or Hot to Archive. Learn more ).

² The following API calls are considered list and create container operations: ListBlobs, ListContainers, FindBlobsByTags, and CreateContainer.

³ The following API calls are considered read operations: GetBlob and SetBlobTier (when it moves a Blob from Archive to Cool, Cool to Hot, or Archive to Hot. Learn more ).

⁴ Network costs are charged separately.

⁵ High Priority requests are for Archive only and can be used to rehydrate small objects in under 1 hour. Learn more about High Priority Archive rehydrate .

For blobs in Archive, the only valid operations are GetBlobProperties, GetBlobMetadata, ListBlobs, SetBlobTier, SetBlobTags, GetBlobTags, FindBlobsByTags, DeleteBlob, and CopyBlob. Setting the tier from Archive to Hot or Cool typically takes up to 15 hours to complete. Learn more .

¹ The following API calls are considered write operations: PutBlob, PutBlock, PutBlockList, AppendBlock, SnapshotBlob, CopyBlob, and SetBlobTier (when it moves a Blob from Hot to Cool, Cool to Archive, or Hot to Archive. Learn more ).

² The following API calls are considered list and create container operations: ListBlobs, ListContainers, FindBlobsByTags, and CreateContainer.

³ The following API calls are considered read operations: GetBlob and SetBlobTier (when it moves a Blob from Archive to Cool, Cool to Hot, or Archive to Hot. Learn more ).

⁴ Network costs are charged separately.

⁵ High Priority requests are for Archive only and can be used to rehydrate small objects in under 1 hour. Learn more about High Priority Archive rehydrate .

For blobs in Archive, the only valid operations are GetBlobProperties, GetBlobMetadata, ListBlobs, SetBlobTier, SetBlobTags, GetBlobTags, FindBlobsByTags, DeleteBlob, and CopyBlob. Setting the tier from Archive to Hot or Cool typically takes up to 15 hours to complete. Learn more .

¹ The following API calls are considered write operations: PutBlob, PutBlock, PutBlockList, AppendBlock, SnapshotBlob, CopyBlob, and SetBlobTier (when it moves a Blob from Hot to Cool, Cool to Archive, or Hot to Archive. Learn more ).

² The following API calls are considered list and create container operations: ListBlobs, ListContainers, FindBlobsByTags, and CreateContainer.

³ The following API calls are considered read operations: GetBlob and SetBlobTier (when it moves a Blob from Archive to Cool, Cool to Hot, or Archive to Hot. Learn more ).

⁴ Network costs are charged separately.

⁵ High Priority requests are for Archive only and can be used to rehydrate small objects in under 1 hour. Learn more about High Priority Archive rehydrate .

For blobs in Archive, the only valid operations are GetBlobProperties, GetBlobMetadata, ListBlobs, SetBlobTier, SetBlobTags, GetBlobTags, FindBlobsByTags, DeleteBlob, and CopyBlob. Setting the tier from Archive to Hot or Cool typically takes up to 15 hours to complete. Learn more .

¹ The following API calls are considered write operations: PutBlob, PutBlock, PutBlockList, AppendBlock, SnapshotBlob, CopyBlob, and SetBlobTier (when it moves a Blob from Hot to Cool, Cool to Archive, or Hot to Archive. Learn more ).

² The following API calls are considered list and create container operations: ListBlobs, ListContainers, FindBlobsByTags, and CreateContainer.

³ The following API calls are considered read operations: GetBlob and SetBlobTier (when it moves a Blob from Archive to Cool, Cool to Hot, or Archive to Hot. Learn more ).

⁴ Network costs are charged separately.

⁵ High Priority requests are for Archive only and can be used to rehydrate small objects in under 1 hour. Learn more about High Priority Archive rehydrate .

For blobs in Archive, the only valid operations are GetBlobProperties, GetBlobMetadata, ListBlobs, SetBlobTier, SetBlobTags, GetBlobTags, FindBlobsByTags, DeleteBlob, and CopyBlob. Setting the tier from Archive to Hot or Cool typically takes up to 15 hours to complete. Learn more .

¹ The following API calls are considered write operations: PutBlob, PutBlock, PutBlockList, AppendBlock, SnapshotBlob, CopyBlob, and SetBlobTier (when it moves a Blob from Hot to Cool, Cool to Archive, or Hot to Archive. Learn more ).

² The following API calls are considered list and create container operations: ListBlobs, ListContainers, FindBlobsByTags, and CreateContainer.

³ The following API calls are considered read operations: GetBlob and SetBlobTier (when it moves a Blob from Archive to Cool, Cool to Hot, or Archive to Hot. Learn more ).

⁴ Network costs are charged separately.

⁵ High Priority requests are for Archive only and can be used to rehydrate small objects in under 1 hour. Learn more about High Priority Archive rehydrate .

For blobs in Archive, the only valid operations are GetBlobProperties, GetBlobMetadata, ListBlobs, SetBlobTier, SetBlobTags, GetBlobTags, FindBlobsByTags, DeleteBlob, and CopyBlob. Setting the tier from Archive to Hot or Cool typically takes up to 15 hours to complete. Learn more .

¹ The following API calls are considered write operations: PutBlob, PutBlock, PutBlockList, AppendBlock, SnapshotBlob, CopyBlob, and SetBlobTier (when it moves a Blob from Hot to Cool, Cool to Archive, or Hot to Archive. Learn more ).

² The following API calls are considered list and create container operations: ListBlobs, ListContainers, FindBlobsByTags, and CreateContainer.

³ The following API calls are considered read operations: GetBlob and SetBlobTier (when it moves a Blob from Archive to Cool, Cool to Hot, or Archive to Hot. Learn more ).

⁴ Network costs are charged separately.

⁵ High Priority requests are for Archive only and can be used to rehydrate small objects in under 1 hour. Learn more about High Priority Archive rehydrate .

For blobs in Archive, the only valid operations are GetBlobProperties, GetBlobMetadata, ListBlobs, SetBlobTier, SetBlobTags, GetBlobTags, FindBlobsByTags, DeleteBlob, and CopyBlob. Setting the tier from Archive to Hot or Cool typically takes up to 15 hours to complete. Learn more .

¹ The following API calls are considered write operations: AppendFile, CreateFilesystem, CreatePath, CreatePathFile, FlushFile, SetFileProperties, SetFilesystemProperties, RenameFile, RenamePathFile, CopyFile

² The following API calls are considered read operations: ReadFile, ListFilesystemFile

³ The following API calls are considered iterative read operations: List Filesystem & List Path

⁴ The following API calls are considered iterative write operations: RenameDirectory, RenamePath, RenamePathDir

⁵ Additional cross-region data transfer network changes may apply based on source/destination of each storage access. Learn more at the Bandwidth pricing page

For blobs in Archive, the only valid operations are GetBlobProperties, GetBlobMetadata, ListBlobs, SetBlobTier, SetBlobTags, GetBlobTags, FindBlobsByTags, DeleteBlob, and CopyBlob. Setting the tier from Archive to Hot or Cool typically takes up to 15 hours to complete. Learn more .

¹ The following API calls are considered write operations: AppendFile, CreateFilesystem, CreatePath, CreatePathFile, FlushFile, SetFileProperties, SetFilesystemProperties, RenameFile, RenamePathFile, CopyFile

² The following API calls are considered read operations: ReadFile, ListFilesystemFile

³ The following API calls are considered iterative read operations: List Filesystem & List Path

⁴ The following API calls are considered iterative write operations: RenameDirectory, RenamePath, RenamePathDir

⁵ Additional cross-region data transfer network changes may apply based on source/destination of each storage access. Learn more at the Bandwidth pricing page

For blobs in Archive, the only valid operations are GetBlobProperties, GetBlobMetadata, ListBlobs, SetBlobTier, SetBlobTags, GetBlobTags, FindBlobsByTags, DeleteBlob, and CopyBlob. Setting the tier from Archive to Hot or Cool typically takes up to 15 hours to complete. Learn more .

¹ The following API calls are considered write operations: AppendFile, CreateFilesystem, CreatePath, CreatePathFile, FlushFile, SetFileProperties, SetFilesystemProperties, RenameFile, RenamePathFile, CopyFile

² The following API calls are considered read operations: ReadFile, ListFilesystemFile

³ The following API calls are considered iterative read operations: List Filesystem & List Path

⁴ The following API calls are considered iterative write operations: RenameDirectory, RenamePath, RenamePathDir

⁵ Additional cross-region data transfer network changes may apply based on source/destination of each storage access. Learn more at the Bandwidth pricing page

For blobs in Archive, the only valid operations are GetBlobProperties, GetBlobMetadata, ListBlobs, SetBlobTier, SetBlobTags, GetBlobTags, FindBlobsByTags, DeleteBlob, and CopyBlob. Setting the tier from Archive to Hot or Cool typically takes up to 15 hours to complete. Learn more .

¹ The following API calls are considered write operations: AppendFile, CreateFilesystem, CreatePath, CreatePathFile, FlushFile, SetFileProperties, SetFilesystemProperties, RenameFile, RenamePathFile, CopyFile

² The following API calls are considered read operations: ReadFile, ListFilesystemFile

³ The following API calls are considered iterative read operations: List Filesystem & List Path

⁴ The following API calls are considered iterative write operations: RenameDirectory, RenamePath, RenamePathDir

⁵ Additional cross-region data transfer network changes may apply based on source/destination of each storage access. Learn more at the Bandwidth pricing page

For blobs in Archive, the only valid operations are GetBlobProperties, GetBlobMetadata, ListBlobs, SetBlobTier, SetBlobTags, GetBlobTags, FindBlobsByTags, DeleteBlob, and CopyBlob. Setting the tier from Archive to Hot or Cool typically takes up to 15 hours to complete. Learn more .

¹ The following API calls are considered write operations: AppendFile, CreateFilesystem, CreatePath, CreatePathFile, FlushFile, SetFileProperties, SetFilesystemProperties, RenameFile, RenamePathFile, CopyFile

² The following API calls are considered read operations: ReadFile, ListFilesystemFile

³ The following API calls are considered iterative read operations: List Filesystem & List Path

⁴ The following API calls are considered iterative write operations: RenameDirectory, RenamePath, RenamePathDir

⁵ Additional cross-region data transfer network changes may apply based on source/destination of each storage access. Learn more at the Bandwidth pricing page

For blobs in Archive, the only valid operations are GetBlobProperties, GetBlobMetadata, ListBlobs, SetBlobTier, SetBlobTags, GetBlobTags, FindBlobsByTags, DeleteBlob, and CopyBlob. Setting the tier from Archive to Hot or Cool typically takes up to 15 hours to complete. Learn more .

¹ The following API calls are considered write operations: AppendFile, CreateFilesystem, CreatePath, CreatePathFile, FlushFile, SetFileProperties, SetFilesystemProperties, RenameFile, RenamePathFile, CopyFile

² The following API calls are considered read operations: ReadFile, ListFilesystemFile

³ The following API calls are considered iterative read operations: List Filesystem & List Path

⁴ The following API calls are considered iterative write operations: RenameDirectory, RenamePath, RenamePathDir

⁵ Additional cross-region data transfer network changes may apply based on source/destination of each storage access. Learn more at the Bandwidth pricing page

For blobs in Archive, the only valid operations are GetBlobProperties, GetBlobMetadata, ListBlobs, SetBlobTier, SetBlobTags, GetBlobTags, FindBlobsByTags, DeleteBlob, and CopyBlob. Setting the tier from Archive to Hot or Cool typically takes up to 15 hours to complete. Learn more .

Blob Index

Blob Index is an intelligent data sub-resource for blob; consisting of user-defined key/value tag attributes that are automatically indexed for querying. This provides a managed multi-dimensional classification for your blob objects, allowing for quick, simple, and cost-effective data discovery capabilities beyond listing by prefix filters on blob name. Learn more about the feature at blob documentation .

Data transfer prices for block blobs (per GB)

When you write data to a GRS, RA-GRS, GZRS, or RA-GZRS account, the data is replicated to another Azure region. The geo-replication data transfer charge is for bandwidth used to replicate data to the second Azure region. This charge also applies when you change the storage account's replication setting from LRS to GRS or RA-GRS or from ZRS to GZRS or RA-GZRS.

GZRS, or RA-GZRS are not currently available for Premium Block Blobs

General-purpose v1 storage accounts enable access to block blobs, page blobs, files, queues, and tables, offering low transaction prices but with higher storage prices. General-purpose v1 accounts do not provide access to Cool or Archive storage.

Data storage

Note: General-purpose v1 accounts don’t have access to Hot, Cool, or Archive tiered storage. For access to tiered storage, upgrade to a general-purpose v2 account.

*The following API calls are considered write operations: AbortCopyBlob, AppendBlock, BreakBlobLease, BreakContainerLease, ChangeBlobLease, ChangeContainerLease, CopyBlob, CreateContainer, IncrementalCopyBlob, PutBlob, PutBlock, PutBlockList, PutGeoMessage, PutGeoRepairMessageMeasurementEvent, PutGeoVerificationMessageMeasurementEvent, SetBlobMetadata, SetBlobProperties, SetBlobServiceProperties, SetContainerACL, SetContainerMetadata, SnapshotBlob, and UndeleteBlob.

**The following API calls are considered read operations: AcquireBlobLease, AcquireContainerLease, BlobPreflightRequest, GeoBootstrap, GetBlob, GetBlobLeaseInfo, GetBlobMetadata, GetBlobProperties, GetBlobServiceProperties, GetBlobServiceStats, GetBlockList, GetContainerACL, GetContainerMetadata, GetContainerProperties, GetCopyInformation, GetEncryptionKey, ReleaseBlobLease. ReleaseContainerLease, RenewBlobLease, and RenewContainerLease.

Data transfer prices for block blobs (per GB)

When you write data to a GRS, RA-GRS, GZRS, or RA-GZRS account, the data is replicated to another Azure region. The geo-replication data transfer charge is for bandwidth used to replicate data to the second Azure region. This charge also applies when you change the storage account's replication setting from LRS to GRS or RA-GRS or from ZRS to GZRS or RA-GZRS.

GZRS, or RA-GZRS are not currently available for Premium Block Blobs

Connect with us directly

Get a walkthrough of Azure pricing. Understand pricing for your cloud solution, learn about cost optimization and request a custom proposal.

Talk to a sales specialist

See ways to purchase

Purchase Azure services through the Azure website, a Microsoft representative, or an Azure partner.

Explore your options What is a Blob storage account, and how is it different from a general-purpose storage account?

A Blob Storage account is specialized for storing data as blobs, and allows users to specify an access tier based on the frequency of access to data in that account. General Purpose accounts can be used to store blobs as well as files, disks, tables, and queues.

When looking at my Azure statement, how can I tell whether I’m being charged for a Blob Storage account, or blobs in General Purpose storage accounts?

If you see “Hot,” “Cool,” or “Archive” in the resource name, this means the charge is associated with Blob Storage accounts. For example, if you see “Standard IO – Cool Block Blob (GB),” this means you’re using and being charged for Blob storage or general-purpose v2 accounts. “Standard IO – Block Blob (GB)” is the metric associated with the use of block blobs in general-purpose storage accounts.

What are Premium Hot, Cool, and Archive access tiers, and how can I determine which one to use?

Premium* Blob storage is available only to the premium block blob storage account type and is best suited for IO intensive workloads that require low and consistent storage latency.

Storage GB pricing increases from Archive to Cool, from Cool to Hot, and from Hot to Premium. And the cost of transactions increases, conversely, from Premium to Hot, from Hot to Cool, and from Cool to Archive. Archive and Cool tiers should be used for rarely and infrequently accessed data, respectively. The Cool tier has a lower availability SLA than the Hot tier.

Please note you can set the access tier of a blob as Hot, Cool, or Archive in Blob Storage and General Purpose v2 accounts. At present you cannot tier data from Premium into Hot, Cool or Archive and you cannot tier data from Hot, Cool or Archive to Premium. We are working on supporting object tiering for Premium in the future.

Will I be charged for data reads if I toggle my Blob Storage or General Purpose v2 account from Cool to Hot?

You’ll be charged for both read operations per 10,000 blobs and for data retrieval per GB when you toggle your Blob storage or general-purpose v2 account from Cool to Hot. For example, if you have 10,000 blobs equaling 100 GB of data in a Blob Storage or General Purpose v2 account, and you toggle that account from Cool to Hot, you’ll be charged 10,000 x ( $- /10,000) + 100 × $- = $- for data retrieval.

Will I be charged for data writes if I toggle my Blob Storage or General Purpose v2 account from Hot to Cool?

For general-purpose v2 accounts, you are charged for write operations (per 10,000). For Blob storage accounts, there is no charge for Write operations.

Load more FAQ What is the "Geo-Replication Data Transfer Charge"?

When you write data into GRS accounts, that data will be replicated to another Azure region. The Geo-Replication Data Transfer charge is the bandwidth cost of replicating that data to another Azure region. When you switch an account from RA-GRS to GRS or LRS (or from RA-GZRS to GZRS or ZRS), the account will be billed as RA-GRS (or RA-GZRS) for 30 more days from the conversion date.

What are the total charges incurred when retrieving and reading blobs in Archive?

A blob cannot be read directly from the Archive tier. To read a blob in the Archive tier, a user must first change the tier to Hot or Cool. For example, to retrieve and read a single 1,000-GB archived blob that has been in the Archive tier for 90 days, the following charges would apply:

Data retrieval (per GB) from the Archive tier: $- /GB-month x 1,000 GB = $- Rehydrate operation (SetBlobTier Archive to Hot): $- /10k = $- Early deletion charge: (180 - 90 days)/30 days x $- /GB-month x 1,000 = $- Read blob operation from Hot = $- /10k = $- Total = $- + $- + $- + $- = $- How is pricing for Blob storage accounts compare to general-purpose v2 accounts?

Pricing for Blob storage accounts and general-purpose v2 accounts is identical for block blob storage, except for data write (per GB) and early deletion charges in the Cool tier. Blob storage accounts charge for Cool tier data writes (per GB) but not Cool tier early deletion, whereas general-purpose v2 accounts charge for Cool tier early deletion but not Cool tier data writes (per GB).

What are the total charges incurred when changing my account replication setting from LRS to GRS or RA-GRS?

There will be a one-time fee equal to the sum of all data multiplied by the geo-replication fee in the primary region. For data stored in the Archive tier, there will also be a charge to read all the data (both read operations per 10,000 blobs and for data retrieval per GB) from the primary region and to write all the data (write operations per 10,000) into the secondary region.

Can I move data between premium block blob and other account types?

At present you cannot tier data from Premium into Hot, Cool or Archive and you cannot tier data from Hot, Cool or Archive to Premium. We are working on supporting object tiering for Premium in the future.

To move data, you can synchronously copy blobs from using the new Put Block From URL API ( sample code )or a version of AzCopy that supports this API. Put Block From URL synchronously copies data server side, which means that the data has finished copying when the call completes and all data movement happens inside the Azure Storage. How can I purchase Azure Storage Reserved Capacity?

Azure Storage Reserved Capacity provides options to purchase standard storage capacity in units of 100 TB and 1 PB per month blocks for one-year or three-years terms. To purchase Azure Storage Reserved Capacity, you can choose the required number of units for Hot, Cool or Archive storage tier on any of the available storage redundancies (e.g. LRS, ZRS, GRS), and for a specific region (e.g., US West 2). Additionally, you can choose to pay with a single, upfront payment or monthly payments.

Get started in the Azure portal .

How will I be billed for Azure Storage Reservations?

For Enterprise Agreement (EA) customers, Azure Prepayment will be used first to purchase Azure Storage Reserved Capacity. In scenarios where EA customers have used all their Azure Prepayment, Azure Storage Reserved Capacity can still be purchased, and those purchases will be invoiced for the single, upfront payment on their next overage bill.

For customers purchasing via Azure.com, at the time of purchase, the credit card on file will be charged for the full upfront payment (or monthly fixed payments) of Azure Storage Reservations.

After making an Azure Storage Reserved Capacity purchase, how do I know which data storage object received the reservation discount?

Azure Storage Reserved Capacity is purchased at a single subscription or shared resource group scope. Therefore, reservation is applied to your usage aggregated to the purchased scope and cannot be limited to a specific storage account, container or object within the subscription.

Load more FAQ Can I restrict my Azure Storage Reserved Capacity so that it may be used on a specific storage account within a subscription?

No, all purchases are at the aggregate, subscription level only. Purchases cannot be split across multiple subscriptions.

What is covered under Azure Storage Reserved Capacity purchase?

Azure Storage Reserved Capacity allows you to purchase data storage capacity for Standard (GPv2) storage and Blob Storage accounts. The purchased capacity can be used for Block Blobs and Azure Data Lake Storage. Currently Premium Storage, other storage types (Managed Disks, Files, Queues, Page Blobs and Tables), early deletion charges, operations and data transfer are not included in Azure Storage Reserved Capacity.

Can I use my data storage purchased through Azure Storage Reserved Capacity across multiple regions and redundancies?

Azure Storage Reserved Capacity is purchased for a specific region (e.g., US West 2 or any other region of your choice), storage tier (e.g., Hot, Cool or Archive) and redundancy (e.g., LRS, GRS or ZRS), and therefore cannot be used outside these constructs. You can always purchase an additional Azure Storage Reserved Capacity for your data storage need in other regions or redundancies.

Where can I view the details associated with my purchased Azure Storage Reserved Capacity?

Select the ‘Reservations’ menu on the left side of the Azure portal to view all the Azure Reserved Storage Capacity details associated with your account. All the details associated with the Azure Storage Reserved Capacity that you have purchased will be displayed on the right.

What's the difference between an exchange and a cancellation?

An exchange allows you to receive a prorated refund based on the unused amount, which applies fully to the purchase price of a new Azure Storage Reserved Capacity. A cancellation terminates your Azure Storage Reserved Capacity and you'll receive a prorated refund based on the remaining term of the Azure Storage Reserved Capacity minus a 12 percent early termination fee.

Are there any restrictions on exchanges?

There's no limit on the number of exchanges you can make. Additionally, there's no fee associated with an exchange. The new Azure Storage Reserved Capacity purchased however must be of equal or greater value than the prorated credit from the original Azure Storage Reserved Capacity. Additionally, Azure Storage Reserved Capacity can only be exchanged with another Azure Storage Reserved Capacity.

Are there any restrictions on cancellations?

You can cancel Azure Storage Reserved Capacity at any time (up to $50000 per year). Cancelling allows you to return the remaining months of an Azure Storage Reserved Capacity back to Microsoft for an early termination fee of 12 percent. The remaining prorated balance, minus the fee, will be refunded to your original purchase.

How do I exchange or cancel my Azure Storage Reserved Capacity?

If you decide that you wish to exchange your Azure Storage Reserved Capacity (e.g., exchange a purchase 7 units of 100 TB block for 1 unit of 1 PB block ), you can initiate exchange from management portal and view the inventory of Azure Reserved Capacities. Click on a purchased capacity and two buttons will appear in the command bar stating “refund” or “exchange”. Once selected, a support ticket, prepopulated with all of the Azure Storage Reserved Capacity details, will open. Once submitted, the request will be processed, and an email will be sent to you to confirm completion of the request.

Can you please provide an example of how reserved pricing works?

Let’s assume you purchased 100 TB of reserved capacity for 1-year for LRS Hot Storage in US West 2.

100 TB reserved capacity pricing for Hot LRS Data Stored (US West 2) = $18540 .

You can pay the full amount upfront, or pay fixed monthly installments at $- every month for the next 12 months. Let’s assume you signed up for a monthly reservation payment plan.

Scenario 1 - If in any given month within the reservation period, you use 101 TB, your bill will include $- for 100 TB of reserved capacity and $19 for 1 TB at pay-go prices. Your total bill for data stored that month is now $1564 . Scenario 2 – If in any given month within the reservation period, you use 80 TB of capacity, your bill will include $- for 100 TB of reserved capacity. What happens to my bill when I change the account’s replication setting to GZRS/GRS/LRS/ZRS?

If you convert your storage account from RA-GRS to GRS/LRS, that account is billed as RA-GRS for an additional 30 days beyond the date that it was converted. If you convert your storage account from RA-GZRS to GZRS/ZRS, that account is billed as RA-GZRS for an additional 30 days beyond the date that it was converted.