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.
While creating and publishing from Visual Studio is straightforward and easy, it is still a manual task and doesn't fit well with current continuous integration and deployment methodologies. Azure app service has the ability to integrate build pipelines from several sources. I've added another boilerplate web application project to my solution, but the connection string is pointing to the URL of the web API we have just deployed to app service. This solution is stored in an Azure DevOps Git repo. I'll just quickly create another web app service for this new project. I won't bother with all the steps and just go straight to review and create. Now that that's done, let's go to Deployment Centre under the deployment menu.
As you can see, it supports the major CI/CD providers, and you can also manually push and synchronize code from other cloud storage sources. I'm already authorized with Azure Repos, which is where the project code resides, so that's what I'll choose. Next, I'll select Azure pipelines and hit the continue button. In configuration, we select our DevOps organization, the project, the repository, and the branch we want to pull our code from. Next, I'll click continue and then finish. The connection has been successfully set up, and at the top, we can see the URL of the repository. If I switch over to the project in Azure DevOps and go to project settings, and then service connections, we can see the newly created connection to app service. Here, I'll click edit to verify the connection and also rename it. Now you may be tempted to select the resource group from the drop-down list before you verify the connection. I found doing this resulted in a verification failure, and I'm assuming that is the case as the connection is scoped to the subscription level, but that is just an educated guess.
Having set up the connection, a pipeline is automatically created, but in this case, I don't want that as this repo contains the whole solution, but I only want to deploy one of the projects to Azure app service. What I'll do was delete this pipeline and create another one that will just publish this one project. This isn't a course about DevOps pipelines, but just as a point of interest, this default pipeline is building and testing the whole solution, whereas this pipeline that I prepared earlier is only dealing with the LorryLogAdmin project. The final step is the deployment, where we can see the service connection is the Azure subscription, and the web app name is that of our app service. Now I'll run the pipeline, giving it permission to use the service connection. After that has finished, I'll go back to the app service and click on the URL, and we can see that the web app has been deployed. When I click on vehicles, it returns the data that we set up in the last demonstration.
Just to recap app deployment so far. We created an App Service resource through the portal, which is essentially a placeholder website that is ready to accept a web application. Then we created an Azure SQL database and allowed access from other Azure resources. From the Visual Studio IDE we deployed a web API application using the app service publish profile. We saw how the same could be achieved without the profile, and in fact, how an App Service and Azure SQL database could be created from within Visual Studio. Finally, we integrated an App Service deployment with an Azure DevOps repository to implement a CI/CD build pipeline.
Next, I want to look at Docker container image deployment.
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.