Develop Azure Platform as a Service compute solutions

7. AZ-203/204 - Lab -Azure Web Apps - App Service Logs

Hi and welcome back. Now in this chapter, let's look at the diagnostic feature that is available for Azure Web apps. So you can go ahead and use the Diagnostic feature that's available in the Azure WebApp service to get the following information: you can get all the application logging. So these are log messages that are generated by the application code. You can also get Web server logging. This is raw SB requests data. You can get detailed error messages. So these are copies of the dot HTML error pages that would have been sent to the client browser. Your failed request is tracing. This provides detailed tracing information on failed requests.

You also have deployment logging. These are logs that are generated when content is published to an application. Now over here, I'm giving a reference to the documentation. So for each type of log that you have over here, you can actually go ahead and FTP on to the underlying directory structure. And here are the directories in which all of the log information is stored. And here is a description of each log that is stored with the Web App Diagnostic feature. So let's go ahead to Azure. Let's see how we can work with Azure Web App diagnostics. So here I am in Visual Studio for one of our applications, our ESP net versionfour seven application, which is published on Twzo. So this is an MVC-based application. What I've done is that in the home controller. So here I am placing some information. So I'm just ensuring that I understand when my controllers are being invoked. So they have come as part of our application logging mechanism. So if I actually go ahead and just run this application locally, so if I go on to my output window over here, you can see that we have the trace information in place invoking the controller. So now I'll go ahead and publish this modified solution or project to Azure Web App. So again, I'll right click on Publish. So I'll ensure that I choose my profile accordingly. So staging that 4000, that's fine. Let me go ahead and publish.

I want to make sure these changes are published on the Azure Web application. Now, once the project is published successfully, there will be no changes when it actually comes to the application itself. So remember, this traces information happening in the background. But let's say you want to capture all of this information as part of the Azure Web App service. We can go ahead and work with Diagnostics, the feature that is available for Azure Web apps. So in the app service, if you go on to the monitoring section, you can actually go on to the App Service logs. Please note that this was part of the Diagnostic feature earlier on, but now it has been renamed to App Server Logs. So we have the ability to go ahead and log the application onto the file system itself. So remember that your Azure web apps are internally hosted on virtual machines. And these virtual machines have a file system. So if you want the logs to be stored on the file system of the virtual machine, you can go ahead and enable application logging. You can also go ahead and enable the application by logging onto a storage account. Here you can decide on the level of the message you want to store. So, for example, in our application code, remember we are tracing information. You can also specify a retention period. You can also define web server logging. This can be done either on the storage or on the file system.

You can also turn on detailedRMS and fail request tracing. So for the purpose of this demo, let's go ahead and turn on application logging over here. Again, I'll choose information. This is on the file system. Let me go ahead and also turn on Web server logging. You can give a maximum quota. And what is the retention period for the logs? In a few days, we can go and save these settings. Once we have this in place, you can go on to your application. We go again to the home page for my controller. Let me go on to the details. So I'm just trying to exercise my application. So internally in the background now, all these logs should be stored on the file system of the virtual machine which is hosting this web application. You can now go ahead and FTP onto the server to see that file system. So I'm going to go ahead and use theVin SAP two to go ahead and log into that machine to see the underlying file structure. So how do I FTP in order to see the file structure? Where do I get the host name, the username, and the password from? So, if you return to our app service and navigate to the Deployment Center section, you will see several options for deploying your source code to the Azure web app. So I'm going to scroll down and find FTP.

Let me go ahead and choose App and click on the dashboard. I'm going to go on to User Credentials. So if I want to FTP onto the file system as a user, I can go ahead and choose User credentials. Now I'm going to go ahead and enter the password, which I can now define for my username to FTP onto that file system. So let me go and specify a password. Please make sure to click on Save Credentials. Once this is done, I'll go and copy the link over here. So I've got the host name over here. Now for the username, we have to take this as the username, the complete username. So let's copy this and then I'll enter my password. Click on "login". Now, once you've logged in, we see our site folder dubbed up root. And here we can see all the contents of our web application. So I can go ahead and see the underlying file system, which is not only storing your application but also storing our log data. So if I just go up in terms of the directory, if I go on to log files, So if I go on to the application folder over here, I can see a text-based file if I go ahead and open it. So here you can see your trace information data if I go back up, if I go on to the HTTP folder, if I go on to raw logs, if I go on to this log data. So remember, this is our web server log data. Over here you can see the pages that are being invoked. If you scroll onto logging, right, you can see the client IP address. So you can see all the information about the requests that are being made on your web application, right? So in this chapter, I want to go through the features of the App service lock which are available for Azure App Service.

8. AZ-203/204 - Lab - Azure Web App - Publishing from GitHub

Hi and welcome back. Now in this chapter, we will see how we can publish a very simple project from Visual Studio onto our Azure Web App service using GitHub. So we'll check in our code to GitHubHub, and it will configure our Azure App service to pick up our code from GitHub itself. Now, if you want to go ahead and publish your code from Visual Studio onto GitHub, then make sure you go out and install the GitHub extension from Visual Studio. So let me go ahead and download this. I'll execute the extension. We just have to make sure Visual Studio is closed. I'll install the extension now. Once the extension is complete, let me go ahead and open Visual Studio.

Now I'm going to go ahead and create a new project. So I'll just create a simple ASP.NET web application. I'll give a name for the application. Click the Create button. So this time, I'll just create an empty ASP.NET application. I'll just create a simple web form. So for the project, let me just go ahead and add a simple web form. Give a name. Click on "Add." Just enter something in the diff tag. Click on save. Now I'll go on to GitHub. If you already know how to accept GitHub, it's a very easy process. You can go ahead and sign up for GitHub. Now, I already have a GitHub account, so let me go ahead and sign in. Give me my username and password. So I have a couple of repositories in place over here. So let me go ahead and now publish my code from Visual Studio onto GitHub. So in Visual Studio, after you go ahead and actually install that GitHub extension, now I'm going to go on to Team Explorer. Now, in case you can't see Team Explorer here, you can go ahead and add or remove buttons. You can go ahead and search for TeamExplorer and then enable it over here. So let me go on to Team Explorer. So the first thing I can do over here is GitHub. So I can go ahead and now connect to my GitHub account.

So I'll sign in using a browser. So I'll just log in to my GitHub account. So I'm now logged in over here. You can see that my GitHub account is now connected. Let me go back to my solution, Explorer. Now let me go ahead and add this entire solution to Source Control. Let me go ahead and commit all of my changes. I'll click on save. Let me enter a commit message. I'll go ahead and commit to stage. So now I can go ahead and sync my changes with a server. So if I click on Sync over here, I have the ability now to publish to GitHub. So let me go ahead and publish it on GitHub. Now this will go ahead and create a new repository on GitHub. So let me give a name for the repository. Let me go ahead and now hit Publish. So now, remember, my code is being published on to the remote GitHub repository. Once you have the repository in place, we can actually confirm this. So very good. And refresh my page for GitHub. So you can see we have our repository in place. Now I'll go on to our existing Azure Web application. So remember, for this app service, Staging Web4000, we had an existing application in place. So this was an MVC-based application. Now I want to ensure that my application gets picked up by the code from GitHub.

So for this, we are going to go on to the deployment center. In the deployment center, I'm going to choose GitHub. It's already gone ahead and connected to my GitHub account. Now, if it's not connected to theGitHub account, you can actually go ahead and configure it. So if I just go ahead and change the account, you will actually be redirected onto a page where you can actually authenticate into the GitHub account. Since I've already authenticated, I can go ahead and now click on Continue. You can now select an app development service from the Actions menu. You can also choose GitHub Action, which is in preview and even as your pipelines, which are also in preview state. So I'm going to choose the app service builder service itself. So what's going to happen is that our code is going to be picked up from GitHub. It's going to be built as an application on the app service. So we go ahead and hit Continue now over.I can go ahead and choose my repository. So it's a demo app thousand. I can leave it as my master branch. Click to continue. Click on Finish. And now it's going to go ahead and do an initialsync from the GitHub repository onto my Azure Web app. Let's come back once this is done. Now over here, you can see that we have a status of success. So that means our code should have been synced up on our app service. So now in the other tab, if I go onto mywebsite and if I go on to default, aspx, you can see that we have this is our sample application. So now our code has been picked up from GitHub.

Now let me go back to Visual Studio. Let me go ahead and make a change to my application. Let me go ahead and save it. Let me now proceed to Solution Explorer. Let me go on to my default aspx page. Let me do another commitment. Let me give a name. Let me commit all. So it's been committed locally. Let me go ahead and now sync my changes to GitHub. Let me go and make my changes. So it has successfully pushed my changes on to GitHub. Now, if I go back to the deployment centre, you can see how automatically there is one more deployment which has been triggered. So our deployment centre or appservice is now automatically connected to GitHub. And any changes you make to our code that we commit to the GitHub repository will now be reflected here. It will trigger a deployment to our app service. So now if I go ahead and refresh this page, you can see we are getting the change text over here. So this chapter is going to show you how you can publish your code. This is a very simple code from GitHub on to your app service. So this marks the end of this chapter.

9. AZ-203/204 - Lab - Azure Web App - Azure CLI

Hi and welcome back. Now in this chapter we are going to see how to use the Azure CLI to go ahead and create a resource group, create an app service plan, create a web app and also deploy it from a GitHub repository onto our app service. So over here I am specifying the location for my GitHub repository. I'm using the Ad Group Create command to go ahead and create a new resource group in the central US region. I'm giving a name to the resource group. I'm then going ahead and creating a new app service plan. I'm giving a name for the plan, mentioning the resource group and what is a skew. So over here I'm using the basic plan for the app service plan. And then I'm going ahead and creating the web app itself. I'm giving it a name, specifying the resource group and what plan it belongs to. And then I'm going ahead and executing an easy web app deployment source configuration to go ahead and take the code from our GitHub repository. From the master branch, I'm giving the name of our web application, the Resource Group.

And over here is the repo URL. So let's go ahead and execute these commands in Azure Cloud Shell. So here I am, logged into the Azure Cloud shell. Let me go ahead and first right-click and enter the Get repo URL. Next, let me go ahead and create the resource group. Once I have the resource group in place, let me go ahead and hit on Clear. Now let me go ahead and create a new app service plan. Once I have the app service plan in place, let me go ahead and hit Clear again. Now I'll go ahead and create the app service. Once this is done, I'll go ahead and copy the command to now publish our code on our GitHub repository. So, once this is finished, please allow me to move on to my app services. So you have that new app service, that new App 2000. So let me go on it. Let me go ahead and take the URL, go to a new tab, go on to the default espx. So here you can see the code has been automatically published from GitHub onto a new app service, right? So this marks the end of this chapter wherein we looked at how to create a resource group, how to create an app service plan, how to create an Azure web applaud how to publish code from a GitHub repository.

10. AZ-203/204 - Lab - Azure Web App - Custom domains

Hi and welcome back. Now in this chapter, we are going to look at custom domains. So, in a previous chapter, we saw how to create an Azure Web App. We then get a URL for our app, and then users can go ahead and access the web application via that URL URL. But let's say you want to assign a custom-friendly domain URL for your web application, so users could go ahead and hit that URL and then be redirected to your app service. Well, you can do this as well. Please note, to do this, you first need to go ahead and buy a domain. So I've already gone ahead and bought a domain on a yearly basis from a domain provider known as GoDaddy. You have to create something known as records with that domain provider. So this ensures that whenever a request is made on this domain, that request will be forwarded onto the Azure App service.

After you create the records, you have to do something known as "validating the domain" from the App service itself. So let's see how we can implement this list of steps. So over here, I was logged in to the GoDaddy portal over here. So I said I have a number of domains that I actually went ahead and bought as part of this domain provider. So I'll go on to cloudwalkalong.com. Let me go on to the DNS settings.

So here is where I can actually modify all the records which are present as part of this domain. So if I go on to my app service, I have an app service in place. So if I go ahead and just look at the URL, what is basically hosted in this application? So I have a simple ASP.Net application in place, an MVC app. However, I stated that I would like to map this to a more domain-friendly URL. So if I go on to my appservice, there's something known as custom domains. Now, in order to add my own custom domain, I have to add two records to my domain provider. So the first step is to get the IP address. We have to copy it. We have to go on to a domain provider. We have to ensure that we have a record type of a. This is the name added, and the value should be the public IP address of the app service. So we go ahead and click on Save. If you don't have this record in place, you can just go ahead and add a new record. Now, remember, this depends upon your domain provider. Since I've gone ahead and bought this domain from GoDaddy, these are the next steps. We don't have to go ahead and also have a CNNrecord with the name of "Dub Dub" and the value.

So in the value I need to go ahead on, what is the URL? The current URL for R as your web app. So let me go ahead and edit this. Let me go ahead and then click on Save. Now, after you've modified these settings, you have to wait for a couple of minutes for the settings to propagate. After a couple of minutes now, in yourapp service in custom domains, you can go ahead and add a custom domain. So over here, you have to give the name of the custom domain, so that's Cloudworkalong.com. Let me go ahead and hit on Validate. So I will choose the hostname record type that has a C name. Let me go ahead and add the custom domain. So if the verification is complete, it should work as it's shown over here. And you can go ahead and then add the custom domain. Now, once this is done, over here, you can see that currently it's not secure in nature. So remember that when adding a custom domain, it will by default be routed on to just SDP. It will not use SSL. So in a new tab, if I go on to Cloudworkalong.com, I will now see my Net Core application. So now my requests are being routed from my domain provider onto my app service, right? So this is the end of this chapter.

11. AZ-203/204 - Lab - Azure Web App – SSL

Hi and welcome back. Now, in the prior chapter, we had seen how we could map a custom domain onto our app service. But remember, this is not secure in nature. Now, if you want to apply SSL to your app service, you can do that as well. So if I go on to the TLS SSL settings over here, you can go ahead and create something known as a binding. Now, you could use either your private key certificates or you could use your public key certificates. So remember, the private key certificates are within the Azure environment itself, but you could also have public certificates that have been issued by other CA authorities. The best thing about Azure is that it is currently in an in previous state if you go on to private key certificates. Normally, you would need to purchase a certificate and then apply it here. But there is the ability to go ahead and create something known as an App Service Manager Certificate for free.

So instead of actually going in and buying a certificate, you can just go ahead and create an App Service Managed Certificate. Now, the only limitation is that you can't download the certificate, but just for the means of seeing how this works, this should be more than enough. So we can go ahead and click to create an app service manage certificate. Let's go ahead and recognise our current domain. We can go ahead and then hit on Create. Now, once you have the certificate in place, you can actually go back on to custom domains. Now over here, you can go ahead and add a binding. So here you can choose that certificate. You can choose the SSL type. Click on Add Binding. Once you have the binding done, you can see the state is secure. Now if I go on to the URL over here, let me go on to HTTPS. And now you can see that your site is secure and you're able to browse to your application right away. This marks the end of this chapter, wherein we have seen how we can apply SSL to your app service.

Prepared by Top Experts, the top IT Trainers ensure that when it comes to your IT exam prep and you can count on ExamSnap Developing Solutions for Microsoft Azure certification video training course that goes in line with the corresponding Microsoft AZ-204 exam dumps, study guide, and practice test questions & answers.