Learn the overview differences between Azure App Service plans, including their scopes, and a quick demonstration about creating a plan.
- [Instructor] Before we can start deploying apps we need to understand and create app service plans. Every app needs to be associated to an app service plan, but you are not limited to a single app per service plan. You can host multiple apps in a single service plan. The apps within that service plan share resources across the service plan, as long as the app is in the same subscription, region, and resource group. You could have multiple app service plans in a resource group.
For example, you may have an app service plan for production, another app service plan for test and a third for dev. And keep in mind the costs are based on the app service plan tier, not the number of apps within that plan. And let's talk about the app service plan tiers. First, we have our free and shared tiers. These are great for test and dev and getting your feet wet. Next, we have the basic tier. This can be used for low traffic apps, you must scale manually, and you could have three instances running within the basic tier.
Next, we have our standard tier. Typically we'll use our standard tier for production apps, it includes auto-scaling and backup, and you can have 10 instances running within the standard tier. And finally, the premium tier. You can use the app service environments, ASE, and have 20 instances running within this tier. There will be times when you will need to isolate your app. For example, if your app is highly resource intensive you'll want to isolate it within its own service plan.
If the app requires different scaling than the other apps within that plan. The scaling affects all the apps within the plan, you cannot isolate just one app to have a different scaling metric than the rest of the apps in the service plan. And finally, if the resources are located in different geographical regions, you will want to use an isolated service plan for that app. Now that we've discussed app service plans, let's take a look at them and create one.
As you can see, I have already logged into Azure. I have two resource groups already created, one is DeployApps and one is securitydata. We will be focusing on the DeployWebApps resource group. As you can see, I have nothing in this resource group. Let's go ahead and create an app service plan. To do so, click Add. I'm going to enter in our search terms to bring up the service itself.
I've entered in app service, I'm looking for app service plan. And we can see that we have a service called App Service Plan, I'm going to go ahead and select that. Our next blade provides a little bit of information about the service, I'm going to go ahead and click Create. Now we can provide the information about the service plan. The first thing we need to do is provide a name for it.
I'm going to go with the example of Production. You will select your subscription. You can go ahead and create a new resource group on the fly, or, if you're already creating the app service plan within the resource group, the resource group will be populated automatically for you, as we have here. Our Operating System, remember you can also select a Linux based service plan, I'm going to stick with Windows. I'm going to leave the location as South Central US, but I have several to choose from.
And next we have our pricing tier. By default, an S1 Standard will be selected for you. Again, this is what we'd typically use for production. As this is a production environment, I'm going to leave it as S1, but I'd like to show you the other options available to us. At the top we have our Premium tiers. And you'll notice that we have up to 250 GB of storage, we have up to 20 instances, and we also have 20 deployment slots. We'll be talking about deployment or staging slots a little bit later in the course.
Our app will be backed up 50 times daily, and we have our Traffic Manager available to us. Next, as I scroll down, you'll notice that we have the Standard tiers. You can see that we will only have 50 GB available per tier, up to 10 instances, our backup is now daily, and we only have five slots. As we scroll down further and as we move into the Basic tier, our options become less and less.
Because I already have the S1 tier selected I'm going to go ahead and close this blade and then click Create. It'll take about a minute, minute and a half or so, for the app service tier to be deployed. We now have notification that our deployment has been successful. I'm going to go ahead and close the app service plan blade. And I'm going to close the Everything blade. Next, I'll refresh our resource group.
You'll see we have our app service plan. I'm going to click in that. And we have the basic information about our plan. We don't have any apps in it yet, so it looks pretty boring. We will add in an app in the next video.
- Deploying Web Apps
- Creating App Service plans
- Deploying and moving apps
- Configuring app settings
- Managing Web Apps using PowerShell and CLI
- Configuring alerts
- Enabling diagnostic logs
- Retrieving and streaming logs
- Configuring Web Apps for scale and resilience