Introduction & Overview
Creating an App Service Web App
Creating Web Service Containers
Configuring a Web App
The course is part of these learning pathsSee 2 more
You’ve got an idea for a great web app, or maybe you’ve already started building it. The next question is how are you going to get it out there on the Internet?
In this course, you will learn how you can quickly and easily set up a website and publish your app to the world with Azure App Service. Of course, web apps are a lot more complex and varied than just HTML pages and we will see how App Service supports a range of programming languages, frameworks, and even operating systems. We will explore features that greatly simplify application deployment and management, as well as those that will increase your app’s functionality like authentication and accessing on-premise data. App Service as with other Azure products has a raft of tools for monitoring and logging so you can make sure your app is performing optimally.
For any feedback, queries, or suggestions relating to this course, please contact us at email@example.com.
- Deploy apps using the Azure App Service
- Create a web app using the Azure Portal
- Create a web app using Visual Studio
- Understand the configuration and diagnostic capabilities available from Azure App Service
- Understand the advanced features of the service such as container deployment and deployment slots
This is a beginner level course suited developers or anyone wanting to know how to deploy web apps to the Azure cloud.
To get the most from this course, you should have a basic understanding of the software development lifecycle, while knowing how to code would be a plus.
Course source code
Visual 2019 with .NET Core 3.1 was used for the demonstrations in this course.
Since I first made be getting started with Azure App Service. There has been a change in the portal in the way that you can link a repository. In that original demo, the classical deployment Centre is being deprecated and is being replaced with a new deployment Centre experience, or UI so I'm just doing a little addendum here to show you how to use the new repo integration. I'm going to start off with a new Azure DevOps account which has only got one project and at the moment and I'm going to grab or clone the code from the Cloudacademy GitHub repo into my Azure DevOps repo. I'll start off by creating a new project called Lorrylog and then go into the repos and do an import. Click the import button to grab the code from GitHub. Pretty simple, just click the import button and then enter the URL for the repository that we're interested in. Now that's been set up I'll go over to the Azure portal and create a basic web app LorryAPI which I think is the same as what I call that originally in that demo. Still using .net core 3.1 on a Windows server. This time instead of going deployment Centre classic I'll go into Deployment Centre and set up a new CI/CD pipeline. In the source drop-down I've got pretty much the same options that we had in the classic style that were little graphical boxes on the screen, but this is just options from a drop-down list. When it comes to selecting the organisation, I am logged in to the portal with the same username that I log into Azure DevOps and I've got a couple of different accounts there, so I'm going to select the Hallam0349 which is this temporary one I've just set up. I'll select the project that I just created, and the repository is obviously Lorrylog and there's only a main branch. As soon as I've done that and click save, it's going to start doing a build and trying to deploy. You may have realised that there are several projects in that solution, so I need to tell the app service which one I want published. We will see that this is going to cause a problem. What you need to do is go down to configuration and under settings create a new appsetting called project. For the value, I'm going to put in the path to the LorrylogAPI project that I want to publish. Because I'm lazy and not very fast at typing I'm going to just whip back to the DevOps repo and grab the path from there and paste it in and click Save. Back to deployment Centre, looking at the logs, and sure enough, it's failed, because it didn't know which project to publish. What I'll do now is go back to the repo and make a change in the VehicleController file. I'll remove a comment and commit the change to kick-off another build and deploy. I'll head back to Azure and wait for the project to be deployed. We can see now after that check-in and commit the status is success and it's active, which means it's been deployed and is live. If I open up another browser window and put in the URL with the vehicles path, we can see that it has indeed successfully deployed and is returning the same results as it did in the previous old demo.
Hallam is a software architect with over 20 years experience across a wide range of industries. He began his software career as a Delphi/Interbase disciple but changed his allegiance to Microsoft with its deep and broad ecosystem. While Hallam has designed and crafted custom software utilizing web, mobile and desktop technologies, good quality reliable data is the key to a successful solution. The challenge of quickly turning data into useful information for digestion by humans and machines has led Hallam to specialize in database design and process automation. Showing customers how leverage new technology to change and improve their business processes is one of the key drivers keeping Hallam coming back to the keyboard.