Email: Password:       Forgot Password 
    .netCodeSG
A Saarsha Group Online Community for dot net codes group like C#, Asp.NET, VB.NET, Sharepoint, JavaScript, JQuery, Ajax, SQL, WCF, WPF.
 
TECHNOLOGIES:
 

Azure- Create Storage Account Step-By-Step

Article:
Viewed:  107 
Posted On:  22/09/2019 06:28:27 
What is Storage Account? what is the purpose of Account Account in Azure? 

 

In this article, I am going to explain how we can create a Storage account in Azure Step by step.

What is Storage Account?

An Azure storage account contains all of your Azure Storage data objects: blobs, files, queues, tables, and disks. The storage account provides a unique namespace for your Azure Storage data that is accessible from anywhere in the world over HTTP or HTTPS. Data in your Azure storage account is durable and highly available, secure, and massively scalable.

Types of storage accounts:

Azure Storage offers several types of storage accounts. Each type supports different features and has its own pricing model. Consider these differences before you create a storage account to determine the type of account that is best for your applications.

The types of storage accounts are:

  • General-purpose v2 accounts: Basic storage account type for blobs, files, queues, and tables. Recommended for most scenarios using Azure Storage.
  • General-purpose v1 accounts: Legacy account type for blobs, files, queues, and tables. Use general-purpose v2 accounts instead when possible.
  • Block blob storage accounts: Blob-only storage accounts with premium performance characteristics. Recommended for scenarios with high transactions rates, using smaller objects, or requiring consistently low storage latency.
  • FileStorage storage accounts: Files-only storage accounts with premium performance characteristics. Recommended for enterprise or high performance scale applications.

Access tiers for block blob data:

Azure Storage provides different options for accessing block blob data based on usage patterns. Each access tier in Azure Storage is optimized for a particular pattern of data usage. By selecting the right access tier for your needs, you can store your block blob data in the most cost-effective manner.

The available access tiers are:

The Hot access tier, which is optimized for frequent access of objects in the storage account. Accessing data in the hot tier is most cost-effective, while storage costs are higher. New storage accounts are created in the hot tier by default.

The Cool access tier, which is optimized for storing large amounts of data that is infrequently accessed and stored for at least 30 days. Storing data in the cool tier is more cost-effective, but accessing that data may be more expensive than accessing data in the hot tier.

The Archive tier, which is available only for individual block blobs. The archive tier is optimized for data that can tolerate several hours of retrieval latency and will remain in the Archive tier for at least 180 days. The archive tier is the most cost-effective option for storing data, but accessing that data is more expensive than accessing data in the hot or cool tiers. 

Replication :Replication options for a storage account include:

Locally-redundant storage (LRS): A simple, low-cost replication strategy. Data is replicated synchronously three times within the primary region.

Zone-redundant storage (ZRS): Replication for scenarios requiring high availability. Data is replicated synchronously across three Azure availability zones in the primary region.

Geo-redundant storage (GRS): Cross-regional replication to protect against regional outages. Data is replicated synchronously three times in the primary region, then replicated asynchronously to the secondary region. For read access to data in the secondary region, enable read-access geo-redundant storage (RA-GRS).

Geo-zone-redundant storage (GZRS) (preview): Replication for scenarios requiring both high availability and maximum durability. Data is replicated synchronously across three Azure availability zones in the primary region, then replicated asynchronously to the secondary region. For read access to data in the secondary region, enable read-access geo-zone-redundant storage (RA-GZRS).

Encryption

All data in your storage account is encrypted on the service side.

Storage account endpoints

A storage account provides a unique namespace in Azure for your data. Every object that you store in Azure Storage has an address that includes your unique account name. The combination of the account name and the Azure Storage service endpoint forms the endpoints for your storage account.

For example, if your general-purpose storage account is named mystorageaccount, then the default endpoints for that account are:

  • Blob storage: http://mystorageaccount.blob.core.windows.net
  • Table storage: http://mystorageaccount.table.core.windows.net
  • Queue storage: http://mystorageaccount.queue.core.windows.net
  • Azure Files: http://mystorageaccount.file.core.windows.net

Control access to account data

  • Azure Active Directory:
  • Shared Key authorization:
  • Shared access signature: 

Copying data into a storage account

  • AzCopy
  • Data movement library
  • REST API or client library
  • Azure Import/Export service 

Storage account billing

You are billed for Azure Storage based on your storage account usage. All objects in a storage account are billed together as a group.

Now Let's create  a Storage Account:

Step1: Open Azure portal: https://portal.azure.com

Search Storage Account

1.png

Image 1.

 

Click on +Add

2.png

Image 2.

Enter all required information
 

3.png

Image 3.

Make public or private endpoints. Public will be available for all. Private will be available with in a Virtual network. 

4.png

Image 4.

Click on Review + Create

5.png

Image 5. 

Click on Create.

6.png

Image 6.

Storage account has been created. Click on Go to resource.

7.png

Image 7.

  Comment:
         HOME   |   Submit Article   |   Contact Us   |   About Us   |   Terms & Condition   |   Advertise With us