Storage account

What it is

A storage account is the Azure resource that provides a named home for Azure Storage data services. It can contain blob containers, file shares, queues, and tables, while applying key settings such as redundancy, network access, encryption, and performance to the account or its supported services. Think of it as a securely managed storage facility, not as one folder or one hard disk.

Why it exists

Instead of managing disks or servers for data, a storage account is wholly managed: you choose a name, kind, redundancy, and these apply consistently across every data service inside it. It is the unit you deploy, secure, and pay for.

Key ideas

• The account name is globally unique in Azure Storage and appears in endpoints such as accountname.blob.core.windows.net. It is not an Azure user account.
• Standard general-purpose v2 is the common general-purpose account. Other account types target specific performance or service needs; choose from current service documentation rather than assuming every feature works with every type.
• The account is a shared boundary for important choices. For example, redundancy applies across storage services in an account, so resources with different recovery needs may need separate accounts.
• A blob container is inside a storage account. A file share, queue, and table are different Azure Storage services, not other names for the same thing.
• Access can use Microsoft Entra ID, shared keys, or narrowly scoped tokens depending on the service and scenario. Restrict network access separately through network rules or private connectivity.

Northwind example

Northwind creates northwindordersprod for order receipts. It stores uploaded receipt images in a blob container, chooses a redundancy option based on recovery needs, and limits access to the application identity and approved network path. It creates a separate account for disposable test data because test data has different cost, retention, and recovery needs.

Common confusion

• A storage account is a control-plane resource; a blob, file share, queue, or table is the data stored through it.
• An account’s redundancy copies data for infrastructure failures. It does not undo an application overwriting or deleting data.
• “Private storage account” normally describes its network-access design, not a different storage-account product.

How it fits (diagram)

Design tradeoffs

• Consolidating data in one account simplifies administration but couples its redundancy and networking choices.
• Separating accounts can improve isolation and fit different requirements, but adds operational overhead.
• Availability, supported regions, access tiers, and performance vary by account type and service. Verify the proposed combination before a production deployment.

Related

redundancy-lrs-zrs-grs · access-tier · storage-performance · blob-storage · azure-files · storage-network-rule · storage-access-keys · sas-token · northwind-traders-case-study

📘 Source: Microsoft Learn — Storage account overview, checked 2026-09-16.