How to Create an Azure Storage Account

You are currently viewing How to Create an Azure Storage Account

How to Create an Azure Storage Account

azure storage account

The name of your Azure Storage account is unique and cannot be the same as any other account. The endpoints for the Azure Storage services use different format, so you may need to choose one of them. You can create a key expiration policy for your blobs by using the CLI. The az storage account update command accepts a number of parameters, including key-expiration-days. The keyCreationTime property indicates when the account access keys were created. For example, if your account is over a year old, this property will not be set, and you cannot create a policy until you rotate your keys.

Once you have added your storage account to your resource group, you can configure the access keys. The access keys are used to authenticate your access to the data in your account. You will receive two access keys. You should regenerate them regularly for security reasons. Once you have generated the access keys, you can add them to your account. You can find out which of them you have generated by searching for them in the Azure portal.

When creating a storage account, you can specify whether you want your storage account to be accessible by all networks by default. You can restrict access to a specific network, an existing one, or a new virtual network. You can also specify whether you want to access your storage account via a specific IP address or a CIDR range. When you’ve created your account, you can then start managing your objects.

An Azure Storage account consists of several services that store data in the cloud. Each of these services has their own APIs, so monitoring the API availability is essential. Each of these services is monitored by Blue Matador, which automatically monitors each one to ensure that it’s available. If the Availability drops below 100%, the service will be unavailable to your applications. You can also make use of the azure Storage Explorer to manage the access to your data in the cloud.

When you create a storage account, you can define where it is located and select the type of storage you want. By default, the storage account is accessible by all networks, but you can control the access by specifying a location, replication, and access tier. Then, you can create the resource group that contains the resources you need. You can also choose to add a new one. Once the deployment has completed, you can access the files from the new storage account.

What is an Azure Storage Account?

A storage account is a container which combines a number of Azure Storage services. A storage account can only contain data services from Azure Storage. The user can manage data services as a group by integrating them into a storage account. All settings, including those that were set up or modified after creating an account, are applicable. All data in the storage account will be deleted once it is deleted.

Consider a machine-making industry, which produces machines and tools such as screws, pulleys, and wedges. These products are then sold to consumers by stores.

Trade secrets protect the designs and manufacturing processes used in the industry. These data are important to the business and require redundant storage. The data is mainly retrieved from the main factory so it would be preferable to store it at a nearby datacentre. This storage expense should be billed to manufacturing.

A sales group is also part of the industry that produces demonstration and advertisement videos to promote consumer products. This data should be stored at a low cost to avoid redundancy and geographic relocation. The sales team should be billed for this storage. These business deals require multiple Azure storage accounts. Each storage account will include the necessary settings to store the data.

Types of Azure Storage Accounts

Azure Storage offers different types of storage accounts. Each type has unique features and a different pricing model. These differences should be considered before you create a storage account. This will help you choose the right account for your applications. These are the types of storage accounts:

  • General-purpose HTML2 accounts Basic storage account type that can store files, blobs and tables. This is recommended for all scenarios that use Azure Storage.
  • General-purpose accounts v1: Legacy account type to store files, blobs and tables. If possible, use general-purpose accounts v2 instead.
  • Block Blob Storage Accounts: Storage account with premium performance for block blobs or appends. This account is best for situations with high transaction rates, smaller objects, or that require consistent low storage latency.
  • File Storage accounts are Files storage accounts that offer premium performance. This is recommended for high-performance applications or enterprises.
  • Blob Storage account Legacy Blob storage accounts. If possible, you should instead use general-purpose V2 accounts.

Core Storage Services

Core storage services offer a highly scalable object store for data objects. They also provide disk storage for Azure virtual machine (VMs), a cloud file system, a messaging store, and a NoSQL storage.

These data services are part of the Azure Storage platform:

  • Azure Blobs are a highly scalable object store for binary and text data.
  • Azure files are file shares that can be used to deploy cloud services or on-premises applications.
  • Azure Queue provides consistent messaging between components of an application.
  • Azure tables can be used to store structured data in a schema-less way.
  • Azure Disks are block-level storage volumes for Azure Virtual Machines.

Azure Blob Storage

Azure Blob storage, an object storage solution for the cloud, is a storage solution. For large amounts of unstructured data, Blob storage can be augmented. Unstructured data refers to data that doesn’t adhere to any particular data model or definition. For example, binary or text data. Client applications and users can access Blob storage objects via HTTP/HTTPS anywhere in the world. Azure Storage Rest API and Azure PowerShell are used to access Blob Storage objects. Azure CLI or an Azure Storage Client Library is also used. Below is an illustration of the flow and resources for a Blob Storage.

Blob Storage is a storage account that has a container. The containers contain the respective blobs.

Azure Storage supports the following types of blobs:

Block Blobs

Block blobs can store binary and text data. Block blobs can store blocks of data that are easily managed. It can store approximately 4.75 TiB data. Block blobs with larger storage capacities are in preview. They can store up to 190.7 TiB.

Append Blobs

Append Blobs can be created using blocks similar to block blobs, but they are optimized for append operations. Append Blobs are best for situations such as logging data from virtual machine.

Page Blobs

Page Blobs are storage locations for random access files up to 8 TB. These blobs stock virtual hard drives (VHD) files that can be used as disks in Azure virtual machines.

Azure Blob Use case

Let’s take a look at an amplified reality gaming company. The game works on all mobile platforms without any restrictions. This scenario allows users to capture video clips of their gameplay, and then upload them to the servers. The clips can be viewed in-game or on the game’s website. To benefit analytics and traceability, a log can be kept of every upload and view.

A storage solution that can handle thousands of simultaneous uploads, large amounts of video data and growing log files would meet the user’s requirements. Access to APIs from different languages and platforms is required for the user to view functionality on all mobile apps and websites. This application could benefit from Azure Blob storage.

Azure Blob Storage was created to meet specific requirements. This option is recommended for businesses that need to store unstructured data such as audio, video, and images. Blob objects do not need an extension.

These are the possible use cases.

  • Images and documents can be sent directly to a browser
  • Storing files for distributed access
  • Streaming audio and video
  • Log Files
  • Data storage for disaster recovery, backup, restoration, and archiving
  • Data storage for analysis using an Azure-hosted or on-premises service

Azure Blob Pricing

Azure storage provides several access tiers that allow you to store blob objects data in a cost-effective way. These are the available access tiers:

  • Hot – Augmented to store frequently accessed data.
  • Cool Designed to store less frequently used data and lasts at least 30 calendar days.
  • Archive– Enhanced to store rarely used data. The storage period lasts at least 180 days and has flexible latency requirements.

Hot Access Tiers

Hot access tier storage access costs are comparatively higher than those of archive and cool tiers. However, hot access tiers have a low access cost. The hot access tier’s real-time usage includes:

  • Data that is used or expected to be accessed frequently, in detail, data that is read from, and written to often.
  • Hot access Tiers cover data that is staged to be processed and eventually moved to the cool acces tier.

Cool Access Tiers

The cool access tier is more affordable than hot access tiers and has higher access costs. This tier is intended for data that will be kept in the cool Tier for at least 30 calendar days. The cool access tier’s real-time usage includes:

  • Disaster recovery and short-term backup
  • Although older media content is unlikely to be accessed often, it is likely that they will still be available when needed.
  • When more data is being collected, it is necessary to store large data sets cost-effectively. Long-term storage for scientific data and raw telemetry data is one example.

Archive Access Tiers

Archive access has a low storage cost, but retrieval costs are higher than those of the cool and hot tiers. The archive tier must keep data for at least 180 calendar days, or the charge will be applied to your account. Retrieval time for data stored in the archive access tier may take longer depending on the priority of the request. The Archive Access Tier has real-time usage.

  • Backup, secondary, long-term, and archive data
  • Preservation of original raw data, even after it is processed into final usable form
  • Long-term storage of compliance and archive data, which is rarely accessed

Data Storage prices

First 50 Terabytes (TB) per month$0.18 per GB$0.022 per GB$0.01 per GB$0.00099 per GB
Next 450 TB/Month$0.18 per GB$0.0212 per GB$0.01 per GB$0.00099 per GB
More than 500 TB per Month$0.18 per GB$0.0203 per GB$0.01 per GB$0.00099 per GB

Data Transfer Prices and Operations

Write operations (1 per 10,000)1$0.021$0.05$0.10$0.11
2 List and Create Container Operations (per 10,000).$0.06$0.05$0.05$0.05
3 Read operations per 10,000 Archive High Priority Read (per 10,000).5$0.0017$0.004$0.01$5.50 $30
All Other Operations (per 10,000), Except Delete which is free$0.0017$0.004$0.004$0.004
Data Retrieval (per GB)4 Archive High Priority Retrieval per GB5No costNo cost$0.01$0.022 $0.06
Data Write (per GB)4No costNo cost$0.0025No cost

For more information, see Azure Pageblobs Storage Pricing

Azure Storage Files

Azure Files provides fully managed File shares in cloud which can be accessed via industry-standard SMB. Azure File shares can also be attached by on-premises or cloud deployments of Windows, Linux and macOS. You can store it on Windows servers using Azure File Sync to make it easier to access. This allows the user to create network file shares easily accessible by using the standard Server Message Block protocol (SMB). Multiple VMs can share the same files with read and write permissions.

Azure Files is different from files on corporate file shares. Users can access files anywhere using URLs that point to the file and contain a shared access token (SAS). SAS tokens are able to be generated by the user. They allow for specific access to a private asset during a specified time period.

Azure Storage accounts can store file shares, which is one type data. File shares can be used in many real-time situations:

  • File shares are a key component of many on-premises applications. This feature allows you to move applications that share data to Azure. The file share must be mounted to the same drive letter as the application running on-premises. This will ensure that the application segment that has access to the file share works with minimum changes, if any.
  • The configuration files can be accessed from multiple VMs and are protected on a file sharing. Multiple developers can share the same file share to store tools and utilities.
  • Resource logs, metrics and crash dumps can all be written to a file sharing and can be used later.

Azure Storage File Use case

File sharing should be restricted to the end user. The file must be mapped locally on the computers and not accessible by the user. Azure File Storage is the best option for customers. If your business uses File Storage, such as *.docx or *.png, this option is best.

Let’s say that a financial company is migrating an app to Azure. This application creates reports and exports data for users and other systems. These reports and data exports are stored on both NAS devices as well as Windows file shares. These files can be shared easily between systems because they are stored in this manner. The company would like to consolidate these files storage to a native cloud service. The company wants to keep using the Server Message Block to secure access to the files. They want to minimize the impact on existing systems, applications, and users. The company plans to replace their SMB protocol shares with a drop-in replacement. They expect that no code modifications will be required to support the data being moved.

These are the Azure Files solutions for this use case scenario.

“Lift-and-shift” applications

The company’s biggest challenge is moving its application to Azure. Azure Files makes it easy to “lift and transfer” applications to Azure. The file application or user information is stored in the file sharing.

Replace on-premises or add to it File servers

The company plans to consolidate its files storage to a native cloud service after moving the application to the cloud. Azure Files can be used to replace or augment any on-premise file servers, NAS devices or other storage systems.

Simplify cloud development

The final request from the company is that they continue to use Server Message Block (SMB), to access their files securely. Azure Files allows users to store debugging and development tools that can be accessed from multiple virtual machines.

You can create a storage account by defining the name and location of the resource group. It can contain blobs, tables, queues, and files. The access key is what you use to authenticate your storage account. In order to prevent unauthorized access, you must make sure that the access key you created is a valid one. You can find an Azure storage account by searching its name and clicking on the “Add” button.

When creating an Azure Storage account, you can choose a public access level or private access level. You can then add blobs, tables, queues, and files to your resource group. To create a storage account, you must choose the name, location, replication, and access tier, and provide an access key. After establishing the resource group, you must validate the storage account and create a container.

If you need to create a storage account for SimpleBackup, the first step is to create the service. After establishing a storage account, you need to provide credentials to access SimpleBackups. Using the Key value under key1 as the access key, you should name the storage to reflect its owner. Once you have done this, you can add a name and password for it. If you have multiple Azure storage accounts, you can also limit the access privilege to specific resources.

In the resource group, you should provide the name and location of the storage account. The name of your Azure storage account should be in lower case and be globally unique. If you want to add a BlobStorage to a specific resource group, you should indicate the type of the resource in your storage group. You can create a new one if you need more space. You can change the name in any time to suit your needs.