Azure Storage Account | Microsoft Azure

Storage Account

A storage account is a container that groups a set of Azure Storage services together. Only data services from Azure Storage can be included in a storage account (Azure Blobs, Azure Files, Azure Queues, and Azure Tables)

Storage Account is an Azure resource, so it can be grouped under a Resource Group. Under the same Resource Group you can have more than one Storage Account

Resource Group

A resource group is a container that holds related resources for an Azure solution. The resource group can include all the resources for the solution, or only those resources that you want to manage as a group. You decide how you want to allocate resources to resource groups based on what makes the most sense for your organization. Generally, add resources that share the same lifecycle to the same resource group so you can easily deploy, update, and delete them as a group

So we can describe the overall relationship as following, under the same resource group you can have multiple storage accounts, and under the same storage account you can have multiple storage services such as Blobs, Tables, Queues, and File share.

Create Storage Account

To create storage account follow the steps in the following demo, after the demo we will describe the different properties exist in storage account creation process

Basic Properties

PropertyDescription
Resource GroupChoose available resource group, or click on Create New and create a new resource group instantly
Storage account nametype you storage account name, it is recommended to be descriptive, and it must be between 3 to 24 lowercase letters and numbers only
LocationChoose the location (region) of your storage account, in which region you want to host this storage account and underlying services?
PerformanceStandard: A standard performance tier for storing blobs, files, tables, queues, and Azure virtual machine disks
Premium: A premium-performance page blob storage account is optimized for read/write operations. This type of storage account backs an unmanaged disk for an Azure virtual machine
Account KindGeneral-purpose v2 (Recommended)
General-purpose v2 storage accounts support the latest Azure Storage features and incorporate all of the functionality of general-purpose v1 and Blob storage accounts. General-purpose v2 accounts deliver the lowest per-gigabyte capacity prices for Azure Storage, as well as industry-competitive transaction prices. General-purpose v2 storage accounts support these Azure Storage services:
Blobs (all types: Block, Append, Page), Data Lake Gen2, Files, Disks, Queues, and Tables.
General-purpose v1
General-purpose v1 storage accounts provide access to all Azure Storage services, but may not have the latest features or the lowest per gigabyte pricing. General-purpose v1 storage accounts support these Azure Storage services:
Blobs (all types), Files, Disks, Queues, and Tables.
BlobStorage
A BlockBlobStorage account is a specialized storage account in the premium performance tier for storing unstructured object data as block blobs or append blobs. Compared with general-purpose v2 and BlobStorage accounts, BlockBlobStorage accounts provide low, consistent latency and higher transaction rates
ReplicationLocally-redundant storage (LRS): Locally redundant storage (LRS) replicates your data three times within a single physical location in the primary region
Zone-redundant storage (ZRS): Zone-redundant storage (ZRS) replicates your Azure Storage data synchronously across three Azure availability zones in the primary region
Geo-redundant storage (GRS): copies your data synchronously three times within a single physical location in the primary region using LRS. It then copies your data asynchronously to a single physical location in the secondary region
Geo-zone-redundant storage (GZRS): opies your data synchronously across three Azure availability zones in the primary region using ZRS. It then copies your data asynchronously to a single physical location in the secondary region
Access TierHot: for data that to be access frequently
Cold: for the data that we don’t need to access frequently, suitable for archiving and backup data

After setting the Basic properties, you can keep default setting for networking, and Advanced properties. You can add tagging so you can track your cost and usage by specific tag values, then click on Create after validation of the settings by Azure.

After successfully creating storage account you can access data services by Storage explorer, CLI, Python, or other available SDKs

In Coming articles, we will show by example how to connect and manage data services using available tools and SDKs.

Ahmed Ibrahem

Ahmed Ibrahem is working as Data Engineering Team lead, with a wide experience in data management projects and technical implementation using different technologies, and delivering end to end projects starting from business analysis to Data Warehouse modeling and implementation to BI design to customers in different industries.

guest
0 Comments
Inline Feedbacks
View all comments