In this video, visit the Azure Portal to create a new storage account and explore the various options available. Begin to compare the general purpose storage account with a blob storage account and note the redundancy options available at the time of creation.
- [Narrator] In this video, we will create an Azure storage account, using the Azure portal. Once you are logged in to the Azure portal, click on the button with the green plus symbol. Here we see several resource types we can create using the Azure Marketplace. Select storage, and select storage account. This is the Azure storage account. Here I can see the subscription under which my storage account will be created, and the resource group in which it will be contained. In my case I will select an existing resource group.
You can of course create a new resource group. I scroll down to the instance details, and these are the details for our new storage account. First we specify a storage account name, and the name has to be globally unique. It is in fact a public DNS name. I will use learnazuretoday, but of course someone may have done this course before me, and so I may have to pick something to make the name unique. I need to select a location. The location we select for our storage account is relevant in the broader architecture, because the location will determine the distance from the applications and services using this particular storage account, and so if the applications and services are in West US, then I should place my storage account near those applications and services, preferably in the West US.
In my case, I'll select my default of West Europe, but you should consider the implications for the applications and services when you select a location. For the performance, we have two options, standard and premium, and standard is the traditional hard drives, and premium is SSDs. When you select premium, some of our other choices may be more limited, but the idea is that standard gives you reasonable cost, standard storage, and premium gives you premium performance for slightly higher cost. For the account kind, we can see there are two types of storage accounts.
There is the general purpose storage account, and the blob-specific storage account. Here we are going to create a general purpose storage account. In my case, I'll pick the latest version, v2. Under replication, we can determine how widely we would like to distribute our data, for high availability and DR, disaster recovery purposes. So locally-redundant storage is within the same data center, and geo-redundant is geographically distributed storage. Now do notice, when I select premium for the performance, my options for replication are limited to the local data center, and so this is a trade-off to consider.
With standard storage, you can have your data widely distributed, but with premium, it will be remaining in the same data center. For general purpose storage accounts, we can have blob storage, and so we have the cool, hot, and potentially archive tier options, for how we would like to store and ultimately pay for our blobs, and so the default here is being selected for new blobs when they are created. Do note that when I select the blob storage account type, we have the same options, but as I noted earlier, the general purpose storage account gives us the option to use blobs, tables, queues, files, and so forth.
However when we select just the blob storage account we only get the blob feature. So in summary I'm creating a storage account named learnazuretoday. My storage account will be created in the West Europe region. I will use standard performance, traditional magnetic disks. I'll use the general purpose storage account kind, so I get all the Azure storage account features. And I'll have locally-redundant storage. It's the cheapest, but doesn't provide really for DR, for disaster recovery options. And for the access tier for my blobs, by default, they'll be on the hot tier.
Click Next. In these advanced features, we can see here we have the option to require secure transfer. This means, when people access the Azure storage account through its APIs, we can require that all those API calls go over HTTPS. For compatibility and legacy reasons, you may need to allow non-HTTPS access, but the default is to enable secure transfer by default. For more advanced networking scenarios, you are also able to present your storage account onto a virtual network in Azure, and restrict access to the storage account based on the virtual network it is associated with.
Click Next. We often use tags, as name-value pairs of metadata, or additional information about resources, in a way to be able to find them later, when it comes to reporting, especially for billing, so we would tag a particular resource as production, or a particular project, billing code, or some mechanism that matters in terms of how we classify this resource for reporting purposes. Click Next. And here we can see the summary of the storage account we're about to create, and if that's satisfactory, click Create.
Once the deployment is completed, we will need to be able to find our storage account, and there's two easy ways. One is the search dialog at the top of the screen. We can just type the name of the storage account, or we can actually just type storage, and we'll find different kinds of storage, and storage accounts is one of them. Now that the storage account has been deployed, click on Go to resource. And because we created a general purpose storage account, you can see at the top left it says learnazuretoday, the name of our storage account, and on the right, we can see which resource group it is in, its status, its location, subscription, tags, performance, and access tiers, the replication types, and the account kind.
Because it's general purpose, when you scroll down, you will see we have access to the features of blobs, files, tables, and queues. We will use this storage account regularly throughout this course, and so I will pin it to the dashboard, so at the top right, I will click the pin, and then close the blade by clicking the X. And here we can see the storage account on the dashboard, easy to find for later. And so in this video we saw how to create an Azure storage account using the Azure portal.
- Creating a Blob storage account
- Stored access policies for granting privileges
- Shared access signatures
- Encrypting data at rest
- Connecting to blob containers
- Working with append and block blobs
- Azure Storage metadata
- Blob performance considerations