Creating Storage Accounts

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with

Already have an account? Sign In »

23 hours 16 minutes
Video Transcription
Hello and welcome back to Siberia is Microsoft Azure Administrator A Z 103 course. I'm your instructor. Will Carlson and Mrs Episode 17 creating storage accounts. So today is gonna be the first episode where we start delving into the second main section of the easy one of three exam storage.
And to do that, we're gonna go ahead and we're going to discuss the different options that we have here
for storage accounts here in Azure. And we're also gonna go ahead and create a storage account using portal to get started. We're going to start a little bit differently than we have in previous videos,
but we're gonna dive right into some Microsoft documentation about storage. Now,
there are four primary storage functions here within Azure. There's gonna be blobs, files, cues and tables. Now, for a Z 103 cues and tables will not be featured prominently.
The A Z one of three exam is gonna focus exclusively on blobs and files. So
in this course, we're going to do the same. Now we'll talk about both of those file types in greater detail, actually, with episodes for both of those individually, we'll have an episode on blobs will have an episode on files, so
we're going to skip ahead a little bit. And what I really want to call your attention to here in this documentation
is this table right here.
Now, as I'm going through in creating a storage account, all of these options are going to show up. We're going to see all of these things in Portal,
but I find that it's a little difficult to keep up with all of the options as we're going through in Portal. So I want to call your attention to this documentation. I'm not going to reinvent the wheel here. You should definitely refer to this table as you're learning about what the storage options are.
There's going to be more documentation, even about thes storage types,
about redundancy related to storage and about S. L. A's related to different storage options.
I highly recommend you go through and you read that documentation, make some flash cards on that information and ultimately know that information for the exam that is great test fodder for Microsoft.
I'm not gonna bore you to tears, though, and give you 15 slides of the different definitions of storage types.
Microsoft stand that for us for storage in particular, please refer to the online documentation again. I can't stress it enough. There's so much going on here in these cloud environments, the online documentation is going to really be your friend, both for the exam
and as an administrator. As things continually change over the years.
In the months
to get right into the interesting part and done with this documentation part, let's go ahead and go right here in tow. Azure
to create a storage account in Azure. We're gonna go to storage accounts and you'll see the list of existing storage accounts. And this one here is the one that we created a number of episodes ago when we initially set up our cloud shell account.
But to add an account from the ground up, we're going to click on add.
You'll see here that we need to select the subscription that we want to put this in. I'm gonna go ahead and leave this in my free trial subscription,
and then we need to select or create a new resource group because of the R, maybe I to create this storage account in I'm gonna go ahead and put this in the I T resource group
and then I'm gonna name the storage account. Now, one interesting thing here about the storage account name is that because storage accounts in azure, our public and globally available, these names have to be unique. So if I just put test in here, you'll see that that's going to fail.
That's gonna fail as well. But as soon as I make it unique,
it's going to allow me to take that storage account name. So we're gonna go ahead and see if we can
pick one that's not been used before. I'm gonna lead this in move this actually into the central US region.
And now we get into the options here before us for storage accounts in Azure. Now, remember the documentation. It laid out all of these details and really what they are and what they mean. But we'll talk about them here briefly.
So the performance to your is going to be the type of media that the account was created on. So currently, a standard here is going to be on magnetic spinning disks.
The premium tier is going to be on SS D's now, as soon as I go ahead and select premium, clearly the more expensive option, you'll notice that my options here changed, and that's going to be because premium is on. Lee only has available certain functionality and some functionally that
you cannot get on premium that is available on standard.
So we're gonna go back to standard here so we can talk through all of the options.
And again, I want to call your attention to these tool tips. They really are very helpful, particularly here in storage. They tell you a number of bits of information, and ultimately they link you to extend documentation. So as you're preparing for a Z 103
make heavy use of the tool tips and the associated documentation.
But the next option here in a storage account is going to be the kind of account.
Now, general purpose be one is a less expensive option currently for certain workloads.
But I wouldn't personally spend too much time researching general purpose V one storage because we're told that Microsoft is ultimately phasing that out, and that should, from what I've read, be happening relatively soon. General purpose be to storage, rolled out now, some time ago.
So for the most part, general purpose V two is going to meet your needs.
Blob storage is going to be just that you can only store blobs and blob storage. So for the sake of a Z one of three, you will not be able to do file shares in a blob storage storage account. So we're gonna go ahead and leave this as general purpose, be too,
and talk briefly about replication.
Now, locally redundant storage is going to make three copies of my data. They're going to all be within one data center or one zoom
zone. Redundant storage is still going to make three copies of my data, but that data is going to be spread. A cost across multiple availability zones. And essentially, an availability zone is an additional data center within the azure ecosystem. So
locally redundant is three copies within one data center or zone
zone. Redundant is still three copies. That's important to know, but it's gonna be spread across multiple data centers or availability zones, clearly a more redundant option. Also, a more expensive option.
Geo redundant storage goes up a level higher, and that's actually going to create six copies of my data
and one set of those three copies are going to be in a completely different region now from the portal, you definitely do not have the choice of what that secondary region is, but you can see what region it's deployed in. Within the portal
read access Geo redundant storage is going to be the same thing is Geo redundant storage. But that second region that your data is in is also going toe have read access. So all of the connection strings that you get for your storage you're going to get two sets of those one for the primary or marine, right
copy of the data
and another four just read access copies of the data. Clearly, the most expensive up, most expensive option is going to be read access Geo Redundant storage.
We're gonna go ahead and click that here is so I can illustrate what that looks like for you in Portal
in the last option here has to do with the access here
again, tool tips are great. This has to do specifically with blobs, but hot storage is going to be more expensive to store the data but less expensive to access the data.
Cool storage is the opposite. Cool storage is going to be less expensive to store the data
Maur expensive to access the data
now cool and hot storage. Both have millisecond availability,
but cool storage does have a retention timeline. So
cool storage. When you put a blob, they're Microsoft assumes that you're going to keep it there for 30 days or longer. If you delete the blob before 30 days, there is a penalty for doing so. So clearly, they're making the storage cheaper to use, assuming you're going to leave it there for a certain period of time.
Now there is 1/3 option for blob storage that will talk about or a blob access to your But we'll talk about more when we talk about blobs. But it is an archived here, and that archive tear is goingto have
you know up to 15 hour S L. A. For retrieval of the file. But it's going to be very affordable to archive files into the archive tier of blob storage.
The other caveat here for the are capped era blob storage is that Microsoft assumes that you will leave it in the archive storage for 180 days, with some costs for early deletion as well.
We're gonna go ahead and look at the advanced tab and you'll see here secure transfer required and that very generally, regardless of how you access the storage B A, S and B or http a GPS. If you select secure transfer required,
an encryption will need to be available on whichever channel you use
to access that storage. So you're accessing it over the way of you would have to use https if you're accessing it over S and B, you're going tohave tohave encryption enabled at an S and B level high enough that allows it.
We're gonna talk a little bit more about Onley allowing access to your storage from certain virtual networks when we talk about storage firewalls. So for now, we're gonna leave that on all networks.
Data protection Robe briefly has to do specifically with blobs, and it's a way to
store your blobs even after you delete them or update them so it does version ing. So when you make a change to a blob file, it will keep the previous version transparently in the background. You'll only see the one version available. But when you browse through, you will ultimately be able to get back to that previous version of the Blob.
And if you delete a blob, it doesn't actually delete it out of storage. It just marks it as deleted so you can go back in and restore it. So soft elite for blobs can be very hopeful if you're trying to make sure you don't lose important items in that storage.
But be warned, it will bloat your storage account because you're still storing all of those blobs, even though you've marked them as deleted
and or made six simple edits. Now you have six copies of that blob.
We're not gonna talk about Data Lake storage for a Z 103 We're gonna leave that disabled.
We've already talked about tags. There shouldn't be anything new there, So we're gonna go to review and create
everything's validated, and we're gonna go ahead and create this storage account.
So in today's video, we talked about how you go about creating a storage account in Azure, and we also talked about the number of options that are available to us both for the storage type and the access to your and a whole host of other things
and how they're interrelated. And the options presented to us change based on some of the initial options that we select. That was so much fun. In fact, I think coming up, we're gonna dive into some more of the details of the storage blade now that we have our storage account set up.
Thanks so much for joining me today. And I'm looking forward to seeing you in the second storage of video.
Up Next
AZ-103 Microsoft Azure Administrator

This Microsoft Azure AZ-103 Certification training course teaches students to perform tasks like managing Azure subscriptions and resources, implementing and managing storage, deploying and managing virtual machines (VM) and networks, and managing identities!

Instructed By