How To Add A Storage Account in Azure Resource Group Using Azure Market Place

Introduction

The first approach is the default path for adding Azure resources and usually best in most cases. This is our second approach, part of a three-article series to add a resource into the resource group. It is applicable for all types of Azure resources but was originally intended for offers from third-party companies. Let's have a look.

To add a storage account to your Azure resource group, perform the following steps:

Open your Azure management portal here.
In the portal, click on the side blade click on the Resource groups
On the Resource groups blade, click on Resource group in my case name rh-AzureTraining field.
On the Resource groups dashboard, click on the Add option.
Now the Azure marketplace opens, click on Storage, then click on Storage Account.
Once you click the Create storage account blade, there are some fields that need to be filled, then click the button Review + Create.

Subscription
Select your Microsoft subscription from the drop-down

Resource Group
Select the existing resource group that we have created in our previous article or you can create a new resource group by clicking on Create new link. If you are creating a new resource group note enter a unique name for your new resource group. A resource group name can include alphanumeric characters, periods (.), underscores (_), hyphens (-), and parenthesis (), but the name cannot end with a period.

Storage Account Name
Type a unique name for the storage account you are creating in the Name textbox. If the name is unique, you will see a green tick.

Location
In the Location list, select the same location you have been using for the Azure resource group.

Performance
Depending on the type of storage account you create; you can choose between standard and premium performance tiers.

Standard
A standard performance tier for storing blobs, files, tables, queues, and Azure virtual machine disks.
Premium
A premium performance tier for storing unmanaged virtual machine disks. Microsoft recommends using managed disks with Azure virtual machines instead of unmanaged disks.

Account kind
Select the account type in my case I have to choose General-purpose v2 accounts,

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.
BlobStorage accounts
Legacy Blob-only storage accounts. Use general-purpose v2 accounts instead when possible.

Replication
Replication determines how many copies of your data are maintained at one time, and in what locations.

Access Tier (Default)
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. I chose the default Hot access tier.
The available access tiers are,

Hot access tier
This tier 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.
Cool access tier
This tier 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.

Once you click the Review + Create it will pop up the new screen which shows the validation passed message with a green tick, then click the Create button.
It will take Some time Seconds or Minutes then click on the Notification icon and you will see the Storage account deployment succeeded

Finally, we complete our second approach to added the resource into a resource group.