From the course: Azure Administration Essential Training

Implementing Azure web apps - Azure Tutorial

From the course: Azure Administration Essential Training

Start my 1-month free trial Buy for my team

Implementing Azure web apps

“

- [Instructor] Early on in Azure, one of the first services and functionalities that became available and that drove utilization of the Azure Cloud was app hosting. When you have a web app, you can publish your APIs to the cloud and then configure an interface for your app, and provide access to users through secure mechanisms that are available in Azure. So basically, you're getting all of the functionalities to host your code, host your APIs, provide access, secure your access, as well as the infrastructure that will provide the backup for your code, and even testing and redeployment of applications whenever you've got updates that are being added or functionalities that are being added to your applications. So let's take a look at how we create a web app in Azure. If I click on create a resource, I have here web app as one of the most popular resources in Azure and I'm going to click on that. And, of course, as usual, I'm going to pick my subscription as well as pick my resource group. Once I have those selected, I need to specify a name for my web app. Now, your web app will immediately have a name that will be available in a URL and therefore that URL, which is a publicly accessible URL, means that your app name must be unique. So, if I just pick app1, I'm going to get a validation error letting me know that that name has already been used. So, I'm going to do app1webtestapp, all right? And once I've got this name that is been validated, I get that little green check letting me know, I can choose what type of app I'm going to push out. So, if I have my own code, I'll select the runtime stack that will be used to host it. So the coding runtime stack that will be used for my app. As well, it will specify whether it's a Linux or Windows app if I specify a docker container. So the docker container will host an operating system, that operating system will host the code. The third choice is a static web app, and if I click on static web app, I actually have to create some other components inside of Azure to host that static web app. So if I've got my code that already going to inject in there. So I'm going to select a traditional code app, specify the region where that will be deployed, and then I'm going to specify the app service plan. Now the app service plan defines all the resources that will reside around the app. So the app service plan will specify the amount of memory and the CPUs, and essentially the resources that you're throwing at this app, which will have a direct impact on your overall cost. So I'm going to leave the default one there, and I want to highlight that an app service plan resource will be created as well. I can specify as well the zone redundancy for my app. Now, if I go a little bit above, you'll see that there are other tabs and other configurations that I can make during the deployment. I'm not going to select those. I will manage them after I've deployed my app. So I'm going to click on review and create and I'm going to allow that deployment to run through my subscription.

Contents