1. Home
  2. Training Library
  3. Microsoft Azure
  4. Courses
  5. Configuring Serverless Computing on Azure

Managing Azure Function App Settings

The course is part of this learning path

play-arrow
Start course
Overview
DifficultyBeginner
Duration1h 20m
Students428
Ratings
4.7/5
star star star star star-half

Description

Course Overview

Learn Configuring Serverless Computing on Azure with this course. Allowing cloud engineers to leverage serverless technologies to deploy solutions is vital to any enterprise. In this course you will learn to do this without the hassle of maintaining actual servers or virtual machines. In addition, this course provides a true insight into the creation of a 'Function App'. This is an interesting feature because creating a basic Function App is actually deceptively easy. Develop your skills with this course by learning exactly how to create a basic Function App. 

We would recommend having an intermediate understanding of MS Azure along with knowledge of its principles and product offerings before starting, ensuring that you yield the maximum potential of the training content. This Azure training content is made up of 11 comprehensive lectures along with an overview and summary.

This course can also be found in the following Learning Paths:

Learning Objectives

  • Learn what serverless computing is and what it offers
  • You’ll learn how to create an Azure Function in the Azure Portal and how to manage Azure Function App settings
  • Learn how to create an automated workflow with Azure Logic Apps
  • Learn about Event Grid and how to use it to monitor for changes in an Azure subscription
  • Learn what Azure Service Bus is and how to use it

Intended Audience

  • IT professionals who are interested in earning Azure certification
  • IT professionals who need to deploy and configure serverless resources in Azure

Prerequisites

  • Access to an Azure tenant to follow along with demos
  • Moderate understanding of Azure

Related Training Content

Transcript

- [Narrator] In Azure functions, the function app is what provides the execution context for individual functions. The behaviors of a function app apply to all functions that are hosted by that app. In this brief demonstration, I'm going to show you how to manage your function apps in the Azure portal. We're going to review a few of the key tabs and what settings are available in each of those tabs when managing a function app in the portal. To begin managing a function app in the Azure portal, as you can see on your screen here, you need to log in to the Azure portal and browse to the resource group that contains your function app. So what I've done here is browsed to the function app resource group that was created when I created the function app in the previous demonstration. And from within this resource group, all I need to do is click on the app that I created. After clicking on the function app that I created, I'm taken to the overview page where I'm provided with some basic information about the function app itself. I'm provided with the URL to access that function app, along with the app service plan and the pricing tier that I'm using. 

I can also see here that my subscription is my Pay-As-You-Go, which is where the function app is deployed, along with the resource group and location. From the overview page, I can access the platform features, function app settings, the application settings, and even application insights. If I click on platform features here, I can see that I can access many of the features of the app service platform that I can use in my function apps. I have access to general settings, networking, the code deployment center, development tools, monitoring, even the API and the app service plan itself. For example, under networking, I can select Custom Domains here to configure and manage a custom hostname that I can assign to my function app. Because if you remember, if I go back to my overview page here, the default URL is testapp9878.azurewebsites.net. What I could do in the Custom Domains section under Networking is assign a hostname to my function app. You can even buy domains here from the bottom here. If we roll back to our function app here in our overview screen, we can click on function app settings. You notice when you click the tab it actually pins it to the top here. Now the function app settings tab is where I can update the functions runtime version that I used for my app. I can also manage the host keys that are used to restrict HTTP access to the functions that are hosted by the function app itself. 

You can scroll down here, you can see the host keys that are available. I can renew them, revoke them, and I can even show them here. I can change the edit mode of my function app and because I'm on a consumption plan, I can set a daily usage quota which is measured in gigabyte seconds. Clicking on the little icon here, you can see that you can limit platform usage by setting your daily usage quota. Now what'll happen is that once that daily usage quota is reached, the function app stops until the next day. Now what you're seeing on the screen here is a notice that I can't upgrade my runtime version with existing functions. Now, this is because the major version upgrades can break things. I'm at the only runtime version of 2.0, so I can't change back to one, and I don't have any other runtime versions within that major release to change to. So I'm kind of stuck where I'm at. If I go back to my overview screen here, clicking on application settings takes me to the settings for my application where I can change a few different things about my app. I can view the PHP version that's used to run the web app if it's using PHP, I can set the platform bitness to 32-bit or 64, I can also set the HTTP version. If I were using multiple slots for development of my app, I could configure auto swap, but since I'm not, I only have one production slot available, auto swap is turned off. From the application settings screen, I can also configure FTP access for my function app as well as configure remote debugging. Further down here, we can see the application settings, which are encrypted at rest, and then transmitted over an encrypted channel. If we click on show values here, we can see all the values for my app settings. 

We'll hide these back over again. And then further down we see the connection strings that are used with a function app when you're using entity framework. We're not currently using any connection strings so there's none shown here, but if there were, they'd be listed here, and then we could show and hide the values just as we did with our application settings up here. And then, of course, we have default documents. This might look familiar to you because you'll see this in IIS, if you've ever worked with IIS. This is the order in which default documents are referenced. And then further down the page here, you have handler mappings that you can configure, as well as virtual applications and directories. The default one here is the forward slash virtual path that points to the physical path of wwwroot. Again, this is stuff that you probably have seen in IIS. And if you have to mount storage, which is a preview feature, you can choose to display those hidden storage keys in your browser using the controls below. We're not mounting any storage, and since it's a preview, there's not even a guarantee this is going to be live by the time you see this course, so I'm not going to really do a whole lot with this at this time. If we scroll back to the top here and go back to our overview, we can then hit our application insights page. Application insights provide us with some feedback on the application itself and how it's functioning. Server requests, availability, response times, failed requests, even the number of unique users that have used the application. If we click on the application dashboard, we're presented with a new dashboard which shows quite a bit of information about our function app. 

After a few minutes, all these boxes will render, and you can see quite a bit of information is available from one single pane of glass here. Each one of these panes is clickable. And when you click it, you're presented with a larger screen with more detail about each metric. For example, here I'm looking at the average process I/O rate for my app. You're not seeing a whole lot here 'cause we're not doing much with it. We can go back to the dashboard, and even click on an app map. What the application map does is provide us with a graphical view of our application. Bouncing back to the dashboard, we can go in and look at our alerts, and basically, this is telling me here that the status of my app is active, and that the failure anomalies alert has never fired. And then you can go in here and add metric alerts and activity log alerts as well. If we click on failures here, we can see what failures are associated with our function app, and in the operations tab, we can see that there have been four overall operations associated with my function app, but that none have failed. If we click on the performance box, we can see the overall performance of my function app as well. 

We can zoom in to ranges, and look at operation times. We can look at the overall performance. We can see the duration, on average, for my app to fire is seventy-seven milliseconds, and it's done this four times. It will even tell me down at the bottom here the number of samples that it has to produce this information. So as you can see, there's quite a bit that you can gather for your function apps, especially from the function app application insight dashboard. What I suggest you do, and we'll bounce back over to our server list here, and go back into our app service. What I suggest you do, is that you play around with these dashboards. There's quite a bit of information that you can gather when you manage your function app from the Azure portal.

About the Author

Students4553
Courses20
Learning paths2

Tom is a 25+ year veteran of the IT industry, having worked in environments as large as 40k seats and as small as 50 seats. Throughout the course of a long an interesting career, he has built an in-depth skillset that spans numerous IT disciplines. Tom has designed and architected small, large, and global IT solutions.

In addition to the Cloud Platform and Infrastructure MCSE certification, Tom also carries several other Microsoft certifications. His ability to see things from a strategic perspective allows Tom to architect solutions that closely align with business needs.

In his spare time, Tom enjoys camping, fishing, and playing poker.