
Many admins grab one number and treat it as truth. Then the Azure bill disagrees with the script, and the script disagrees with the portal.
This guide covers four ways to check usage: Storage Account Insights, Azure Monitor Metrics, Azure CLI or PowerShell, and Azure Storage Explorer. You'll get the steps, the permissions, and a safe way to read the results.
Key Takeaways
- Insights and Azure Monitor give account-level visibility and trends.
- CLI, PowerShell, and Storage Explorer suit container-level digging.
- A manual blob total rarely matches the bill.
- Verify current limits and metric availability before capacity decisions.
What You Need to Check Azure Storage Account Usage
Pick the method by goal: a quick overview, a historical trend, a container breakdown, or an object-level estimate.
Tools and Indicators Required
Tools covered in this guide:
- Azure portal
- Storage Account Insights
- Azure Monitor Metrics
- Azure CLI and Azure PowerShell
- Storage Explorer
Collect these details first:
- Account name and resource ID
- Account kind (
StorageV2,BlockBlobStorage, orFileStorage) - Region and redundancy setting (LRS, ZRS, GRS, GZRS)
- Services in use
- Current used capacity and trend
- Any relevant limit
Portal labels and command syntax change, so check current Microsoft Learn pages before relying on exact names.
Preconditions and Setup
Management-plane and data-plane access are different things:
- Viewing metrics needs read access at the resource scope
- Monitoring Reader can query metrics through REST, CLI, and PowerShell
- Listing blobs needs a data-plane role such as Storage Blob Data Reader
- Reader alone does not authorize blob-data access
Sign in with Microsoft Entra ID and least-privilege roles. Microsoft recommends Entra ID with managed identities where possible, since account keys grant full data access. Never paste keys or connection strings into scripts or shared notebooks.
Define scope before measuring: a subscription, one account, one service, or one container. Decide whether you need a current reading, a trend, or a detailed inventory.
Four Ways to Check Azure Storage Account Usage
No single method answers everything. Portal metrics are fast and scale well. Scripts and Storage Explorer give detail but must enumerate objects.
Method 1: Use Storage Account Insights in the Azure Portal
Insights gives a visual account-level view of capacity. It shows total storage and breaks it down by Blob, Files, Queue, and Table, plus object counts, without listing a single object.
You need: the portal, the target account, read and monitoring permissions.
- Sign in to the Azure portal, open Storage accounts, and choose the account.
- Go to Monitoring > Insights (or Monitor > Insights > Storage Accounts) and select Capacity. Check the time range.
- Record the account and service values, compare them with the expected workload, and note the date.

Pros: fastest high-level review, multiple services in one view. Cons: breakdown, refresh timing, and history vary by account type and the current portal experience.
Method 2: Use Azure Monitor Metrics for Capacity Trends
Metrics suit tracking growth and building alerts. Account-level UsedCapacity sums Blob, Files, Queue, and Table capacity for standard accounts. Service metrics such as BlobCapacity and BlobCount add dimensions like blob type and tier.
You need: the storage account resource, a supported capacity metric, a time range, and Average aggregation.
- Open Metrics from the storage account or Azure Monitor and select the account.
- Choose
UsedCapacityor a service metric. Review granularity (hourly or coarser), dimensions, and range. - Compare the trend with application activity. Configure an alert only after confirming what the metric means.
Blob capacity is emitted hourly, but Microsoft's blob metrics reference notes background recalculation happens several times a day at variable times. Fresh-looking points aren't necessarily fresh numbers.
For per-container figures, Microsoft documents opt-in advanced metrics (ContainerUsedSize, ContainerBlobCount). They carry charges, and rule changes can take up to six hours to appear.
Pros: efficient for monitoring, trends, and alerts. Cons: not every object or detail is exposed, and it isn't an exact billing calculation.
Method 3: Calculate Detailed Usage with Azure CLI or PowerShell
Scripts enumerate blobs and total content length by container, prefix, or tier. This is the most flexible option.
You need: Azure CLI or Az PowerShell, Entra authentication (--auth-mode login in CLI), and the account and container names.
- Authenticate, select the right subscription and account, and test on a small or nonproduction container first.
- List objects and sum sizes. Decide whether to include versions, snapshots, and deleted blobs. In CLI,
--includetakess,v, andd; in PowerShell, use-IncludeVersionand-IncludeDeleted. Both are excluded by default. - Group or export by container, prefix, or tier. Compare the total with the portal metric and investigate large gaps.

Handle pagination. List Blobs returns at most 5,000 items per request, and a page can hold fewer than that while still returning a continuation marker. Microsoft's own CLI sample warns its result is an estimate, not a billing figure.
You can also pull metrics without enumeration using az monitor metrics list.
Pros: repeatable, customizable, exportable. Cons: slow on large containers, generates billable list transactions, and yields a logical total, not a billing total.
Method 4: Inspect Containers with Azure Storage Explorer
Storage Explorer gives a visual way to browse containers and check folder or container statistics without code.
You need: the current Storage Explorer app, a secure sign-in, and access to the target container.
- Sign in with Microsoft Entra ID and open the storage account.
- Expand Blob Containers, pick the container or folder, and run the statistics or folder-size action.
- Record the object count and size. Repeat per container for an account-wide estimate.
Microsoft's current documentation doesn't spell out whether these statistics include snapshots, versions, or deleted blobs, or how long large containers take. Treat results as a container-level estimate and cross-check against a script or metric.
Pros: approachable, good for visual container analysis. Cons: no complete account-wide billing view, and it can be slow when enumerating many objects.
How to Interpret the Results
A reading only means something if you know what it measures, when it was taken, and whether it reflects account capacity, logical object size, service usage, or billing.
- Normal: usage matches your workload, growth pattern, tier, and redundancy. Record a baseline and watch the trend instead of judging one snapshot.
- Minor differences: refresh timing, aggregation, metadata, versions, snapshots, soft-delete retention, or tools that measure different services. Soft-deleted data stays billed for 1 to 365 days.
- Out of spec: rapid growth, one service dominating, failed writes, throttling, or alert breaches. Find the largest containers, review lifecycle and retention policies, and check current limits before deleting anything.

Standard GPv2 accounts default to 5 PiB maximum capacity (Microsoft docs, October 2025), with increases available by request. Limits differ by account kind, service, and region, so confirm yours.
Follow-up Optimization
Separate cleanup from retention and recovery requirements. Then consider:
- Lifecycle policies (can take up to 24 hours to run)
- Access-tier changes (standard charges apply)
- Redundancy review or archiving
Cool, Cold, and Archive have early-deletion periods of 30, 90, and 180 days.

If you also run managed disks across clouds, Lucidity offers real-time visibility into block storage across AWS, Azure, and Google Cloud. Its AutoScaler expands and shrinks disks with zero downtime. It doesn't cover Blob, File, Queue, or Table usage. For those, stick with the native Azure tools above.
Common Errors and Safety Best Practices
Misleading readings usually come from a few mistakes:
- Confusing limits with used capacity
- Comparing a current metric with an old script result
- Assuming a blob-content total equals the bill
- Selecting the wrong scope or unsupported account type
- Ignoring pagination, versions, or snapshots
- Using the wrong metric aggregation
- Running scripts that silently skip access-denied objects

Don't scan every object unnecessarily. Use portal metrics for routine monitoring and save enumeration for targeted investigation.
Safety and Best Practices
- Use Entra ID and least privilege. Keep keys and connection strings out of notebooks, repositories, and screenshots.
- Confirm the subscription, account, and container before running anything. Avoid delete or lifecycle actions until usage is validated.
- Protect exported reports, since object names and paths can reveal sensitive information. Record the date, scope, method, and assumptions.
Conclusion
You can check Azure Storage usage through Insights, Azure Monitor Metrics, CLI or PowerShell, and Storage Explorer. Each gives a different level of detail.
Reliable analysis starts with defining what "size" means, comparing like-for-like measurements, and confirming current limits. Use the results to guide monitoring, retention, and tiering decisions.
Frequently Asked Questions
What is the use of storage accounts in Azure?
A storage account is the top-level Azure resource that provides access to Blob Storage, Azure Files, Queue Storage, and Table Storage. It also holds settings for security, redundancy, performance, and access.
What is the difference between an Azure storage account and blob storage?
The storage account is the management and security boundary. Blob Storage is one service inside it, built for unstructured objects such as files, images, backups, and logs.
What is the maximum size of an Azure storage account?
It depends on account kind, service, and configuration. Standard GPv2 defaults to 5 PiB with increases by request, but per-share, container, and blob limits differ. Check current Microsoft documentation.
How do I check the size of an Azure Storage Account?
Use Insights for a quick view, Azure Monitor for trends, CLI or PowerShell for scripted detail, and Storage Explorer for visual container inspection.
What is the difference between Azure Storage Account capacity and actual usage?
Logical data size is only part of the picture. Monitored or billed consumption can differ because of metadata, snapshots, versions, soft delete, tier changes, and other enabled features.
Can I check Azure Storage Account usage with Azure CLI or PowerShell?
Yes. Both can query metrics and enumerate blobs. Use secure authentication, handle pagination, expect slow runs on large containers, and don't treat an object-size total as a billing figure.