You may have already heard the term serverless-computing. Many cloud service providers offer this service, including Microsoft. With Microsoft's Azure Functions, you can create function apps that support many languages, including Azure PowerShell.
Suppose you want to automate issuing software licenses to customers. When the customer paid, your website sends an HTTP request to your Azure Function App. The app then validates payment and automatically sends the license to the customer's email address.
That's just one scenario where an Azure Function App can be used. There are more usage scenarios from e-commerce to monitoring and reporting where Azure Function Apps can fit in.
In this article, you will learn how to create an Azure PowerShell Function App, develop, test, and execute the code. You'll also get the chance to build a mini-project where you'll create a function for getting the status of Azure VMs and display the result on the web.
There are several ways to create an Azure PowerShell Function App, and in this article, you will learn the most basic way with the least requirements.
To follow along with the instructions, you need to meet these requirements below.
As you will learn in this article, creating a new Azure Function app is quick and easy as long as you are familiar with the process. The high-level steps to create a simple function app consists of:
There are several ways to create an Azure PowerShell Function App. In this section, you will learn how to create a new Azure Function App using the Azure Portal and Azure PowerShell.
The first step is to log in to the Azure Portal using your credentials. Once logged in, click on the Create a resource button.
In the New page, click on Compute and select Function App from the list of resources.
In the Create Function App page, under the Basics tab, follow these steps.
The steps above are shown in the screenshot below.
Under the Hosting tab, you will create a new Storage Account to host the function app files using the steps below.
You will now see the summary of the new Azure Function App. Click on the Create button to start the resource creation.
At this point, wait for the deployment to complete, and you should see a similar confirmation page, as shown below. Click on the Go to resource button.
In the previous section, you have created a new Azure PowerShell Function App called AzFuncDemoApp1. But, that new function app does not do anything yet. For the Function App to be useful, you must add a new function to it.
Creating a new function requires choosing a template. There are several templates to choose from with different "triggers". These triggers define when the function is triggered, such as timer-based or by an HTTP request. In this section, you will create a new function that responds to HTTP requests.
To create an HTTP Request-based function, under the Functions section of the AzFuncDemoApp1 page, click on Functions. Then, click on the Add button.
Then, in the New Function fly-out, click on the HTTP trigger template option.
Then, in the Details tab, type in the name of the new function. In this example, the function name is HttpDemo1. Then, in the Authorization level, select Anonymous. There are other authorization levels, but since this function is not confidential or sensitive, anonymous should be sufficient.
After the function is created, you should be redirected to the HttpDemo1 function page, as shown below.
After creating a new function, a PowerShell script file is automatically created with the name run.ps1. This script file contains the default code that is executed when the function is triggered. To view this run.ps1 file, go to the Code + Test under the Developer section.
Below is the code that is automatically populated in the run.ps1 file using the HTTP request template.
using namespace System.Net
# Input bindings are passed in via param block.
param($Request, $TriggerMetadata)
# Write to the Azure Functions log stream.
Write-Host "PowerShell HTTP trigger function processed a request."
# Interact with query parameters or the body of the request.
$name = $Request.Query.Name
if (-not $name) {
$name = $Request.Body.Name
}
$body = "This HTTP triggered function executed successfully. Pass a name in the query string or in the request body for a personalized response."
if ($name) {
$body = "Hello, $name. This HTTP triggered function executed successfully."
}
# Associate values to output bindings by calling 'Push-OutputBinding'.
Push-OutputBinding -Name Response -Value ([HttpResponseContext]@{
StatusCode = [HttpStatusCode]::OK
Body = $body
})The expected action of the code above is to display a message based on the logic below.
If the function is triggered without the Name parameter, the message to be returned is:
This HTTP triggered function executed successfully. Pass a name in the query string or in the request body for a personalized response.If the function is triggered with the Name parameter, the message to be returned is:
Hello, <NAME>. This HTTP triggered function executed successfully.Now, to test the code, click on the Test/Run button.
Once the test fly-out shows up, leave the the Input tab's default values, then click on Run.
Wait for the test to complete, and you should see the HTTP response, as shown below.
Now that you've tested the function and confirmed that it is working, the next step is to execute the code the way it was designed for - by issuing an HTTP request.
To execute the function, you first need to get the function's URL. To do so, click on the Get function URL button.
Next, copy the URL to the clipboard.
Now that you have the function URL, you can use your browser to navigate to that URL, as shown below. In this example, the URL is https://azfuncdemoapp1.azurewebsites.net/api/HttpDemo1
The output above is what's expected if the function was triggered without the name parameter value. To execute the function with the name parameter, append the parameter and its value to the URL. Below is the example of the URL with the name parameter.
<https://azfuncdemoapp1.azurewebsites.net/api/HttpDemo1?name=June>The result below shows the output when the name parameter is used with the HTTP request.
It is now time to put your knowledge into practice. In this project, you will create a new function that is triggered by HTTP requests. Once the function is triggered, the code will get the status of the Azure VMs and return the information in the browser.
Note that you do not need to create a new Azure PowerShell Function App as you will reuse the AzFuncDemoApp1 you've created previously.
Since this project involves accessing Azure resources, you'll need to modify the AzFuncDemoApp1 to use a Managed Identity. A Managed Identity is essentially an Azure Service Principal that enables your function to authenticate to Azure and access resources. In this case, you'll be using a managed identity to read the Azure VM status.
There are two types of managed identity that you can assign to the Azure Function App; System assigned and User assigned. For simplicity, you will enable the System assigned identity in this project.
To enable the System assigned identity, follow these steps.
Once the identity is enabled, you would see that the Object ID has been created for the identity. At this point, the identity does not have any role assignment or permission yet. In this section, you will assign the Reader role to the identity.
To assign the role, first, click on the Azure role assignments button. It will take you to the Azure role assignments page.
In the Azure role assignments page, choose the Azure Subscription (if you have more than one). Then, click on Add role assignment.
Next, in the Scope, choose Subscription then choose the right subscription name. In the Role, select Reader. Lastly, click on Save.
After saving the role assignment, you should see that the new role has been assigned.
The identity has been enabled, and permission has been assigned. What's left now is to update the function code. By now, you should already know where to go to edit the function code. Once you are in the Code + Test page of the function, update the existing code using the code below.
using namespace System.Net
# Input bindings are passed in via param block.
param($Request, $TriggerMetadata)
# Write to the Azure Functions log stream.
Write-Host "Getting the Azure Virtual Machine Status."
# Get the Azure VM status
$vmList = (Get-AzVM -Status | Select-Object Name, PowerState)
# Associate values to output bindings by calling 'Push-OutputBinding'.
Push-OutputBinding -Name Response -Value ([HttpResponseContext]@{
StatusCode = [HttpStatusCode]::OK
Body = $vmList
headers = @{ "content-type" = "application/json" }
})Once you've updated the code, save it, and execute the function URL in your browser. The example below shows that the function could get the Azure VM status and returned the information as expected.
You now have a working function that gets and returns the Azure VM status. However, the output is in JSON format and looks ugly. Remember, you control how you want the information is displayed; you just need to modify your code.
Suppose you want the function to return a more presentable output. In that case, you can modify the code to return the result as HTML with custom formatting. Using the code below, you can make the function return the same information but in a table with style.
using namespace System.Net
# Input bindings are passed in via param block.
param($Request, $TriggerMetadata)
# Write to the Azure Functions log stream.
Write-Host "Getting the Azure Virtual Machine Status."
$head = @'
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "<http://www.w3.org/TR/html4/frameset.dtd>">
<html><head><title>Virtual Machine Status</title>
<style type="text/css">
table {
font-family: Verdana, Geneva, sans-serif;
border: 1px solid #1C6EA4;
background-color: #EEEEEE;
text-align: left;
border-collapse: collapse;
}
table td, table th {
border: 1px solid #AAAAAA;
padding: 3px 2px;
}
table tbody td {
font-size: 13px;
}
table tr:nth-child(even) {
background: #D0E4F5;
}
table thead {
background: #1C6EA4;
border-bottom: 2px solid #444444;
}
table thead th {
font-size: 15px;
font-weight: bold;
color: #FFFFFF;
text-align: left;
border-left: 2px solid #D0E4F5;
}
table thead th:first-child {
border-left: none;
}
</style>
'@
# Get the Azure VM status
$vmList = (Get-AzVM -Status | Select-Object Name, PowerState | ConvertTo-Html -Head $head)
# Associate values to output bindings by calling 'Push-OutputBinding'.
Push-OutputBinding -Name Response -Value ([HttpResponseContext]@{
StatusCode = [HttpStatusCode]::OK
Body = [string]$vmList
headers = @{ "content-type" = "text/html" }
})Once you update the function code using the code above, save it, and then execute the function URL again. This time, you should see a similar output, as shown in the image below.
Azure Functions is a quick way to create apps that can be a new system or a part of an already existing workflow to complement and automate some processes. It is reasonably priced (cheap), and there's even a monthly grant. You may potentially run functions at no additional cost!
Additionally, with Azure Functions, you do not need to worry about server maintenance. That way, you can keep your focus on maintaining your application.
In this article, you've learned how to create a new Azure PowerShell Function App. You've learned how to create a function triggered by HTTP requests and accept parameters in queries. You've also learned how to enable managed identities to allow your Function Apps to access Azure resources without embedding the authentication in your code.
What you've learned here are just the basics. There are other ways to create Azure Function apps that include using the command-line or Visual Studio Code. The code provided in the examples here can be improved and integrated with other Azure resources.
Hopefully, the knowledge you gained in this article helps you get started with using Azure Functions in your job, including development, monitoring, or even reporting, to name a few.