- [Instructor] A fundamental configuration of Microsoft Azure is where your data will be stored. One of the main reasons why we move to the cloud and Microsoft's cloud offering Azure, is to actually put our resources and our data in a redundant cloud solution. Well the configuration of where your data will be stored, whether or not that data will be redundant and on which disks it will be stored. All of that is defined through what's called a storage account. Now by default when you subscribe to Azure, you do not have a storage account.
We need to go ahead and create one. So let's do that. First in order to create my storage account and in order to create any resources in Azure, I'm going to click on the new icon. Now when I click on the new icon, I see again all the list of various types of objects that I can create and those are organized again by category. So I need to create something that's in the storage category. And I need to create a storage account. Now that is one of the first things that we will do after we deploy our Azure subscription.
Now the first thing I need to do here is give it a name. Now you'll notice that that name actually becomes a full URL. Which means that your storage account could be directly accessible by customized API to actually store data directly from an application into that storage account. So I'm going to go ahead and give it a name. Now that name needs to be globally unique because the core.windows.net is going to publish that domain. So the name that I'm going to set here needs to be globally unique. So I'm going to call it LinkedinTest1.
And you notice here that I have a little red band that tells me the field can only contain lower case and numbers and name must be between three and 24 characters. So what do I have here? I have lower cases, I have numbers and I am less than 24 characters. The problem is I have upper cases. So I'm going to get rid of that upper case l and that upper case t, and that red band is gone and I transferred it to a green check. So I know that this name is unique. If I had given it a name that already exists, let's try for example Microsoft.
And I click next, it's going to tell me that the name is been used and in this case, not only is it been used but it's reserved and it's trademarked. So we for sure cannot use it. So linkedintest1. And my next option here is the deployment model. Now the deployment model will see that this is an option that will be available for every single resource we create in Azure. We have two types of deployment models, resource manager and classic. The classic resource model essentially means that each on of our resources will be managed individually and independently.
Resource manager model becomes a newer Azure resource manager model functionality, which essentially allows you to group resources together. Start them and stop them together. Manage them as a single entity. Control them and view their resources as a single entity. We will see throughout this course that we will create various types of resources, such as virtual machines, storage, databases. Now all of these could be related for a single task. And we may want to see them and manage them as a single entity.
To do that, we deploy them in the resource manager model. Once they are deployed in the resource manager model, we will be able to group them together and by grouping them together allows us to manage them as a single entity. So next thing here is general purpose, so this is the type of account. So what is this storage account for? Is it for general which means I don't really know what I'm going to store in there, could be anything. Or is is a blob storage account. Blob is used for specific subsets of data that are specific to various applications or clients that will be using that blob.
Now blob is a standard naming terminology that is used in many different types of products, not only Azure and not only Microsoft products. So it's very well known, and it's very specific to the client that you will be using. So if you use a specific client that requires blob storage, this is the type of account that you'll create. By the way, we can have multiple accounts in our Azure subscription. Blob could be one of them. So I'm going to pick here general purpose. Next thing here is I can specify the performance of the storage account. So will it be a standard or premium? Essentially the main difference between both of these is standard will use standard discs, and premium will use solid state discs.
However, once I select premium, I have fewer of the replication options provided to me. Now replication is the next functionality here. If I pick on standard, you'll notice that I have a list of four replication options. The first one locally redundant storage, which basically means that as soon as you create your storage account, it is replicated to another server within the same storage solution. Typically within the same data center.
So if I pick locally redundant storage, that means my storage will be replicated to another server within the same data center, the same region, or the same specific location of where my initial storage account has been created. Notice that if I click on premium, that is my only option. I cannot select any other type of replication. Now if I select standard I have three other options. First, zone redundant. Zone redundant will mean that my storage account will be replicated to other servers in the same zone.
Could be in the same data center, could be in another data center. But it will be in the same zone and we will select the zone in a minute and you'll see what zones are. Next I have geo redundant storage, which means that it will be replicated to another data center in another zone. So if I have all of my data in the United States for example it could be replicated to Asia. Now more likely if I put my data in the United States east it will be replicated to United States west.
But that is considered a different zone. So geo redundant zone, data replicated to separate zones. Now the third option is read access geo redundant zone. So the same thing as geo redundant zone, which means that the data is replicated to another zone, but now if a user in the other zone wants to read that data, he can also read that data. So for example you create a storage account in United States east, it is replicated to United States west, a user that is locally available in United States west, will go in will try to access the data, he won't have to go all the way to United States east.
He can read the data locally. Notice that this is only read access, not to write to the data. Now you can easily guess that depending on which option I use the cost will get greater. Next I have encryption, whether or not my data will be encrypted, and again there's cost and resources that are associated to that. Next is my subscription, how will I pay? Now I have a pay as you go subscription, which means that I have a credit card that is assigned to my account which is used to pay for my resource usage.
Now because I have selected my resource manager model, and I told you that we can group our resources together, I'm going to create a new resource group. And I'm going to call this one LinkedinGroup1. And this is going to be my resource group that all of my resources that I will create in this course will be located in. The next thing is my location. Well that's my zone, that's my region. So will it be Canada east, Central US? Notice that it defaulted to Canada east because that is where my account is, that is where I created my subscription, I'm local to Canada and that's where it went by default.
I can pick another location for this storage account. Such as east US, it's completely up to me. Now I'm going to go to my default of Canada east. And I have another option below here which is pin to dashboard. Which will actually create a tile for this storage account for me as soon as it's done. And now my storage account has been submitted to deployment. It is deploying the storage account, and within a couple of seconds, a couple of minutes maybe depending on how Azure is busy, I will see that my storage account will have completed its creation.
- Understanding Azure subscriptions
- Managing Azure with portals and PowerShell
- Configuring Azure web apps
- Deploying virtual machines
- Configuring virtual machines for high availability
- Managing Azure Active Directory
- Creating Azure virtual networks
- Implementing a VPN
- Performing Azure backups