Learn about using the Azure portal to create new storage accounts and explore the various options available. Compare the general-purpose storage account with a Blob storage account, and note the redundancy options available at the time of creation.
- [Instructor] We will create our first two Azure Storage accounts using the Azure Portal. Click on the green plus icon. Here we see the Marketplace and we will search for storage accounts. In the search results, click on the Storage Account by Microsoft, review the information, and click Create. Here in the Create storage account blade, we provide the name for our storage account, which is a DNS name. This has to be all lowercase and no special characters.
Notice the domain suffix core.windows.net, all of our storage endpoints will end with that DNS suffix. We will almost always use the Resource Manager Deployment Model, Classic is essentially deprecated. The first choice to make about your storage account is the account kind. We have General Purpose, which supports all kind of storage, blobs, tables, queues, et cetera, and Blob Storage, which is dedicated to blobs only. Notice what changes in the UI. Here we have the General Purpose kind, and for that we choose Standard or Premium Performance, whereas when I choose Blob Storage, that choice is locked to Standard and we get a new choice down here called Access Tier, Cool, Hot, or in the future, Archive.
The first storage account we'll make General Purpose, Standard Performance, and for Replication, this depends on the high availability solution you want. We will select Locally-redundant Storage, meaning there will be three copies of our data in the local datacenter, and of course, it is possible to choose higher redundancy and do review the documentation in this regard. We can choose to force all traffic to our storage account to be encrypted, so the choices to secure are transfer as a requirement, to require HTTPs at all times.
I will leave this disabled for now for the sake of some of our demos. We'll use our current subscription, in my case it is named Learn Azure Pay-As-You-Go, and we'll create a new resource group, Learn_Azure, for all of our test storage accounts. I will place my storage account in West Europe, this is closest to me, closest to all my applications. This is a critical decision, as this will dramatically impact the latency that your applications see when they communicate with storage. Usually you'd want to pick the location closest to your application.
I'll pin this new storage account to my dashboard and click Create. Creating a new storage account is relatively quick, but while this is happening, let's also look at a second way to do the same task. On the left edge, click on the little arrow where it says More Services, and you'll notice there's a list of services that we can add to the left-hand column as our Favorites. Your storage account may already be there. I'm going to search for storage and find the Storage Accounts Services Panel, and I'll click on the star to add this to my Favorites, and you'll see it appear on the left edge.
When I click on storage accounts, I'll get a list of all of the storage accounts currently in my subscription. So, Subscription at the top level, then Resource Groups, and then our storage account. In this case, the blade storage accounts lists all storage accounts in my subscription. Once your deployment completes, you can see the alert here, Deployment Succeeded, then it should show up in this blade. You may need to click Refresh for the latest one to show up. So, there we have the learnazuretoday storage account created using the Azure Portal.
Because we're in the storage accounts blade, we can click Add up here to also add a storage account without going through the Marketplace. Click on Add and we see the same Create blade. This time, we'll call it learnazureblobstoday, which has to be a unique name, this is, again, a DNS name. We'll use the Resource Manager Deployment Model. In this case, we'll not choose the General Purpose storage account. We already have one, so in this case, we'll choose Blob Storage to work with the specialized features of blob storage.
Performance is Standard, Replication has the same choices as before, some limitations, and I'll choose Locally-redundant Storage for the cost advantage. Do consider your high availability strategy and your disaster recovery strategy when making these choices. Because we picked the account kind Blob Storage earlier on, we now get the choice of how we want to optimize for cost. Are we going to access our blobs frequently? So, Hot Storage will provide the best performance.
Cool Storage will optimize for price in terms of lowering the cost of the consumed storage space, and raise the cost of accessing the blobs. Similar to before, we also have the choice to limit access to HTTPs, I will leave that disabled temporarily. We'll use the same subscription as before and I'll use the existing resource group we created a moment ago, Learn_Azure. Again, West Europe is closest to where I am right now, so the location is convenient.
Do choose one that meets your latency requirements. And again, I will pin this to my dashboard. Click Create. So, here we have the existing storage account learnazuretoday, and we will soon have learnazureblobstoday as a second storage account. I'll go back to the left-hand column and click on Storage Accounts again. Here we see the first storage account, learnazuretoday, and once the deployment completes, we'll see the second one as well.
There the deployment succeeded, we'll click Refresh, and we see both storage accounts. Regarding high availability, do take note of the Azure Storage replication models. There is Locally-redundant, which gets you three copies in the same datacenter, and then the ultimate is Read-access geo-redundant, which places a copy of your data in a geographically distant location and even gives you read-access to that data. However, there are implications and certain limitations in terms of data consistency and so fourth, so do study these carefully and design for disaster recovery appropriately.
- Azure Storage overview
- Azure Storage security
- Deploying Azure Storage
- Accessing Azure Storage files
- Passing messages with Azure Storage queues
- Storing unstructured data with Azure Storage blobs
- Storing structured data in Azure Storage tables (Cosmos DB)