Q60. Capacity of a single storage account?

You can create up to 100 uniquely named storage accounts with a single Azure subscription.

  • Total account capacity for a single storage account - 500TB.
  • Transactions - upto 20,000 entities/messages/blobs per second assuming 1 KB object size.
  • Bandwidth Scalability Target for storage account.


Ingress: upto 5 gigabits per second bandwidth for a Geo-redundant storage account. Ingress is the data sent to a storage account.
Egress: upto 10 gigabits per second bandwidth for Geo-redundant storage account. Egress is the data being received from a storage account.


Ingress: upto 10 gigabits per second bandwidth for local-redundant storage account.
Egress: upto 15 gigabits per second bandwidth for local-redundant storage account.


Each of the Azure Storage services has scalability targets for capacity (GB), transaction rate, and bandwidth.


Scalability limit for Table storage




Let us now see the scalability limit for a table.

In a single partition, the maximum scalability limit to access tables is 2,000 entities.
For an account, the scalability limit to access tables is 20,000 entities.
Both the above measures are per second.


Note that, transaction which inserts an entity, updates, scans or delete will be counted towards the maximum scalability limit.
Scalability limit for Queue storage

The common operations of a queue are AddMessage, GetMessage, and DeleteMessage and all of these count as a message. A queue can process 2,000 messages. Note this measure is also per second.

Scalability limit for Blob storage


Blob supports up to 500 requests per second which includes both read and write operations with a maximum of 60 MB/second. It is recommended to use a CDN service when you use blob storage.