Introduction & Overview
Creating an App Service Web App
Creating Web Service Containers
Configuring a Web App
The course is part of these learning pathsSee 1 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.
Metrics give you a graphical representation of predefined parameters where you can select the aggregation type from a dropdown along with the timeframe. You can add multiple metrics to a chart. If you find one metric swamps the others it’s easy enough to remove. Once you are happy with your chart, give it a meaningful title and pin it to your dashboard.
Within alerts, you can set up notifications to tell you when a particular set of events has occurred. An obvious candidate is to be emailed when your app experiences a 500 server error. First, we need to select our resource of interest from our subscription and resource group. Next, we need to define the condition we want to be notified about by adding a condition. We select the signal metric from quite an extensive list. We can specify which instance of our running app we want to monitor if we have more than one. Under alert logic, you can choose whether your threshold is static or dynamic. A dynamic threshold gives you 3 options: high, medium or low sensitivity. The sensitivity is based on historical data and uses sophisticated machine learning algorithms. As far as server errors are concerned one is one too many so I’m going to stick with static. Next, we need an action group to send the notification so I’m going to get it to send me an email. As you can see there are other options like SMS and a voice call. To finish off I’ll give the alert rule a name and description, leaving the severity level on 3. I’ll just make sure the rule is selected and enabled. After inducing a few errors I should get a notification email, and here it is.
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.