An Azure storage account is a container that holds all your Azure Storage data objects, including blobs, files, queues, and tables.
Azure Storage offers several types of storage accounts, Standard and Premium. Each type supports different features and has its own pricing model.
Azure Storage always stores multiple copies of your data to protect it from planned and unplanned events.
Redundancy models can replicate data in the primary and secondary regions. We will see all these in few minutes following these guided steps.
A. Create a resource group and a storage account.
1. Create and deploy a resource group to hold all your project resources. Learn more about resource groups-- https://learn.microsoft.com/en-gb/azure/azure-resource-manager/management/manage-resource-groups-portal
There are at least three ways to do it as indicated by the boxes.
In the Azure portal, follow the arrow, search for and select Resource groups.
Select + Create.
Give your resource group a name. For example, storemyfilesrg.
Select a region. Use this region throughout the project.
Select Review and create to validate the resource group.
Select Create to deploy the resource group.
Select Refresh to view your new Resource group.
2.Create and deploy a storage account to support testing and training. Learn more about the types of storage accounts--https://learn.microsoft.com/en-gb/azure/storage/common/storage-account-overview#types-of-storage-accounts
In the Azure portal, search for and select Storage accounts.
Select + Create.
On the Basics tab, select your Resource group.
Provide a Storage account name. The storage account name must be unique in Azure.
Set the Performance to Standard.
Select Review, and then Create.
Wait for the storage account to deploy and then Go to resource.
B.Configure simple settings in the storage account.
The data in this storage account doesn’t require high availability or durability. A lowest cost storage solution is desired. Learn more about storage account redundancy ---https://learn.microsoft.com/en-gb/azure/storage/common/storage-redundancy#locally-redundant-storage.
In your storage account, in the Data management section, select the Redundancy blade.
Select Locally-redundant storage (LRS) in the Redundancy drop-down.
Be sure to Save your changes.
Refresh the page and notice the content only exists in the primary location.
2.The storage account should only accept requests from secure connections. Learn more about requiring secure transfer from secure connections-- https://learn.microsoft.com/azure/storage/common/storage-require-secure-transfer
In the Settings section, select the Configuration blade.
Ensure Secure transfer required is Enabled.
3.Developers would like the storage account to use at least TLS version 1.2. Learn more about transport layer security (TLS)-- https://learn.microsoft.com/en-gb/azure/storage/common/transport-layer-security-configure-minimum-version?tabs=portal.
In the Settings section, select the Configuration blade.
Ensure the Minimal TLS version is set to Version 1.2.
4.Until the storage is needed again, disable requests to the storage account. Learn more about disabling shared keys-- https://learn.microsoft.com/en-gb/azure/storage/common/shared-key-authorization-prevent?tabs=portal#disable-shared-key-authorization.
In the Settings section, select the Configuration blade.
Ensure Allow storage account key access is Disabled.
Be sure to Save your changes.
Ensure the storage account allows public access from all networks.
In the Security + networking section, select the Networking blade.
5.Ensure Public network access is set to Enabled from all networks.
Be sure to Save your changes.
