Learn how to create your first app service. This video provides an explanation of what an app service is.
- [Instructor] One of the principal things we'll be working with in platform Azure service are app services, and you can find them in the menu. By clicking on app services, we indicate that we wish to create a new one. However, at the moment, we don't have any app services, so we're going to click "Create App Services." This will bring us to a large menu of the different types of app services that are available to us. We're going to scroll down and find the one that we want, which is the asp.net starter web app.
Let's go ahead and click that, and it's going to review what the starter web app offers. We'll click "Create," and that will start up our process for creating an asp.net starter web app by opening up the configuration blade. We need to give our app a name, and that name must be universally unique. In order to make it unique, I typically prepend the name with the initials of my client or the company I'm working for.
In this case I'll use JL, and we're going to say that our first asp.net application is jl-aspnet1. And that is unique, and if you look carefully just below the name, it says dot Azure websites dot net. So the complete URL for this will be jl-aspnet1.azurenetwebsites.net. Now I need to pick which subscription I'm going to use to cover the cost of this application, and I'll go ahead and use my enterprise MSDN subscription.
Next is whether to create a new resource group, or use an existing one. Resource groups are a way to bundle together various resources that you will create as you go along, where resources are things like applications, databases, and so forth. By aggregating your various resources into one resource group, you can manipulate them and you can delete them all at one go. And that will be very helpful when we're creating test applications.
So let's create a new resource group. It has helpfully named jlaspnet1, the same name as our app name, which is in this case is fine. We're now going to go and pick our app service plan, and this is going to determine quite a bit about how performant it is and what it costs. Let's go ahead and say, "Create New," and up comes the app service plan blade. Give that a name, so we'll call this jl-aspnet1 app service plan, and that's a unique name, and now we need to tell it where we want our app service to be.
It's best if it's proximate to our location where we'll be working from, because that cuts down on latency, so I'm going to say "West US." Now, comes the fun part, the pricing tier. When we click on the pricing tier, the pricing tier choices blade comes up, and you can see there are quite a large number of choices, and each one has a price associated with it. It also tells you what you're getting for that price - how many core, how much RAM, how fast is the disk, and so forth.
We're going to scroll down to the basic, or least expensive, B1, highlight that, and say "Select." That puts that pricing tier back into our service plan blade, and we are now comfortable with that service plan, and we can click OK. That takes us back to the configuration blade, and we have already filled out everything we care about in this configuration, except application insights.
Application insights are beyond the scope of this introductory video, and so we're going to set that to off. The next question is whether we want our new service to show up on our dashboard. And we do, it'll make it easier to access. It's not required, you can certainly search for it as you go, but having it on the dashboard is convenient. And we'll go ahead and click "Create." Azure is now going to create our web app for us, and you can see that it is deploying the aspnet starter web app.
That can take a few minutes.
- Examining and personalizing the Azure portal
- Creating an app service
- Creating an ASP.NET application with Visual Studio
- Viewing your published app
- Creating a virtual machine
- Triggering Azure functions