What Modules Are Available In Azure Functions PowerShell

In this Azure tutorial, we will discuss What Modules Are Available In Azure Functions PowerShell. Along with this, we will also discuss a few other topics like Default PowerShell modules Azure Functions, Create Azure Function App Using PowerShell, Create Azure Function App Using PowerShell Visual Studio Code, Create Azure Function App Using PowerShell In Azure Portal. We will also discuss Azure Functions Timer Trigger PowerShell, Installing PowerShell Modules By Using Install-Module Is Not Allowed, How To Add Custom Modules In The Azure Functions App, Add Custom Modules In The Azure Functions App using Kudu, How To Load Custom Modules From The Azure Functions App.

What Modules Are Available In Azure Functions PowerShell? Now Azure Function supports different modules. There are many PowerShell modules that are supported in case of Azure Functions, Below are few among them

• AppLocker
• Appx
• AppBackgroundTask
• Az.Accounts
• Az.Advisor
• Az.Compute
• AzureAD

We will discuss all the lists of module below in detail with the version.

What Modules Are Available In Azure Functions PowerShell

Like you can create the Azure Functions using the C#, Javascript, java, etc. Same way, you can create the Azure Functions using the PowerShell. You can build your PowerShell script based on your business requirement and run as part of your Azure Functions app.

• How To Access Azure Functions wwwroot Folder

Azure Function with PowerShell executes the PowerShell script when it triggers. Same way like the Azure Function in other languages, it has also the function.json file that actually defines the behavior of the Azure function like the input and out parameters for the function and how the Azure function triggered.

There are different PowerShell modules are supported in the case of Azure Functions. Below are the lists of some key modules with the version details.

Module Name	Version
AppLocker	2.0.0.0
Appx	2.0.1.0
AppBackgroundTask	1.0.0.0
AppvClient	1.0.0.0
AssignedAccess	1.0.0.0
Az.Accounts	1.9.2 and 1.7.5
Az.Advisor	1.1.1
Az.Aks	1.0.3 and 1.2.0
Az.AnalysisServices	1.1.2 and 1.1.4
Az.ApiManagement	2.1.0 and 1.4.1
Az.ApplicationInsights	1.0.3 and 1.1.0
Az.Automation	1.3.6 and 1.3.7
Az.Batch	2.0.2 and 3.1.0
Az.Billing	1.0.2 and 1.0.3
Az.Cdn	1.4.3
Az.CognitiveServices	1.3.0 and 1.5.1
Az.Compute	3.7.0 and 4.2.1
Az.ContainerInstance	1.0.3
Az.ContainerRegistry	1.1.1
Az.DataBoxEdge	1.1.0
Az.DataFactory	1.7.0 and 1.9.0
Az.DataLakeAnalytics	1.0.2
Az.DataShare	1.0.0
Az.DeploymentManager	1.1.0
Az.DesktopVirtualization	1.0.0
Az.DevTestLabs	1.0.2
Az.Dns	1.1.2
Az.EventGrid	1.2.3 and 1.3.0
Az.EventHub	1.5.0 and 1.4.3
Az.FrontDoor	1.4.0 and 1.6.1
Az.Functions	1.0.1
Az.HDInsight	3.1.0 and 3.4.0
Az.HealthcareApis	1.1.0 and 1.0.1
Az.IotHub	2.5.0 and 2.4.0
Az.KeyVault	2.0.0 and 1.6.0
Az.LogicApp	1.3.2
Az.MachineLearning	1.1.3
Az.Maintenance	1.0.0
Az.ManagedServices	1.0.2
Az.MarketplaceOrdering	1.0.2
Az.Media	1.1.1
Az.Monitor	1.7.0 and 2.0.2
Az.Network	2.5.0 and 3.3.0
Az.NotificationHubs	1.1.1
Az.OperationalInsights	1.3.4 and 2.3.0
Az.PolicyInsights	1.3.1 and 1.3.0
Az.PowerBIEmbedded	1.1.2 and 1.1.1
Az.PrivateDns	1.0.3 and 1.0.2
Az.RecoveryServices	2.11.1 and 2.8.0
Az.RedisCache	1.2.1
Az.Relay	1.0.3
Az.Resources	1.13.0 and 2.4.0
Az.ServiceBus	1.4.1
Az.ServiceFabric	2.1.0 and 2.0.2
Az.SignalR	1.1.1
Az.Sql	2.9.1 and 2.6.0
Az.SqlVirtualMachine	1.1.0
Az.Storage	2.4.0 and 1.14.0
Az.StorageSync	1.3.0 and 1.2.3
Az.StreamAnalytics	1.0.1
Az.Support	1.0.0
Az.TrafficManager	1.0.4 and 1.0.3
Az.Websites	1.11.0 and 1.8.0
AzTable	2.0.3
AzureAD	2.0.2.106
AzureADPreview	2.0.2.105 and 2.0.2.102
BitLocker	1.0.0.0
BitsTransfer	2.0.0.0
BranchCache	1.0.0.0
CimCmdlets	1.0.0.0
ConfigCI	1.0
ConfigDefender	1.0
Defender	1.0
DeliveryOptimization	1.0.2.0
DirectAccessClientComponents	1.0.0.0
Dism	3.0
DnsClient	1.0.0.0
EventTracingManagement	1.0.0.0
International	2.0.0.0
iSCSI	1.0.0.0
ISE	1.0.0.0
Microsoft.Online.SharePoint.PowerShell	16.0.20017.0
Microsoft.PowerShell.Archive	1.0.1.0
Microsoft.PowerShell.Diagnostics	3.0.0.0
Microsoft.PowerShell.Host	3.0.0.0
Microsoft.PowerShell.LocalAccounts	1.0.0.0
Microsoft.PowerShell.Management	3.1.0.0
Microsoft.PowerShell.ODataUtils	1.0
Microsoft.PowerShell.Operation.Validation	1.0.1
Microsoft.PowerShell.Security	3.0.0.0
Microsoft.PowerShell.Utility	3.1.0.0
Microsoft.WSMan.Management	3.0.0.0
MMAgent	1.0
MsDtc	1.0.0.0
MSOnline	1.1.183.57
MSOnlineBackup	2.0.0.0
NetAdapter	2.0.0.0
NetConnection	1.0.0.0
NetEventPacketCapture	1.0.0.0
NetLbfo	2.0.0.0
NetNat	1.0.0.0
NetQos	2.0.0.0
NetSecurity	2.0.0.0
NetSwitchTeam	1.0.0.0
NetTCPIP	1.0.0.0
NetworkConnectivityStatus	1.0.0.0
NetworkSwitchManager	1.0.0.0
NetworkTransition	1.0.0.0
PackageManagement	1.4.7, 1.0.0.1 and 1.0.0.0
PcsvDevice	1.0.0.0
PersistentMemory	1.0.0.0
Pester	1.0.0.0
PnpDevice	1.0.0.0
PowerShellGet	1.0.0.1
PrintManagement	1.1
ProcessMitigations	1.0.11
Provisioning	3.0
PSDesiredStateConfiguration	1.1
PSDiagnostics	1.0.0.0
PSReadline	2.0.0
PSScheduledJob	1.1.0.0
PSWorkflow	2.0.0.0
PSWorkflowUtility	1.0.0.0
ScheduledTasks	1.0.0.0
SecureBoot	2.0.0.0
SharePointPnPPowerShellOnline	3.21.2005.2
SmbShare	2.0.0.0
SmbWitness	2.0.0.0
SQLASCMDLETS	1.0
SQLPS	1.0
StartLayout	1.0.0.0
Storage	2.0.0.0
StorageBusCache	1.0.0.0
TLS	2.0.0.0
TroubleshootingPack	1.0.0.0
TrustedPlatformModule	2.0.0.0
VpnClient	2.0.0.0
WindowsSearch	1.0.0.0
WindowsUpdate	1.0.0.0
WindowsUpdateProvider	1.0.0.2

Default PowerShell modules Azure Functions

You can always check the latest versions of the PowerShell module supported in the case of Azure functions using the below PowerShell script. If you are already using the Visual Studio Code for your Azure PowerShell function development. In Visual studio code itself, you can able to check the different PowerShell modules along with the versions for the Azure Function.

Write-Output ‘Azure Function PowerShell Module’

$modules = Get-Module -ListAvailable | Select-Object Name, Version | Sort-Object -Property Name | Out-String

Write-output `n$modules

You can open a new terminal in the Visual Studio Code IDE, and run paste the above PowerShell script to get the list of PowerShell modules available for your Azure PowerShell function. As of now, these are the modules that are supported or available for the Azure Functions.

Installing PowerShell Modules By Using Install-Module Is Not Allowed

One important thing to note down here is you cannot install PowerShell modules by using install-module directly in case of Azure PowerShell functions. Meaning if you will try installing any other modules that are not part of the default modules, than it will not allow you to install the modules, it will show you the error message ” Administrator rights are required to install modules “.

Below is the exact error message what i got

install-module : Administrator rights are required to install modules in ‘C:\Program Files\WindowsPowerShell\Modules’. Log on to the
computer with an account that has Administrator rights, and then try again, or install
‘C:\Users\Bijay\Documents\WindowsPowerShell\Modules’ by adding “-Scope CurrentUser” to your command. You can also try running the Windows
PowerShell session with elevated rights (Run as Administrator).
At line:1 char:1

• install-module azurerm
• ~~~~~~
  • CategoryInfo : InvalidArgument: (:) [Install-Module], ArgumentException
  • FullyQualifiedErrorId : InstallModuleNeedsCurrentUserScopeParameterForNonAdminUser,Install-Module

You can see it here

Since the install-module points to the PowerShell environment directory directly and we don’t have access to that so we are getting this error message ” Administrator rights are required to install modules ” .

How To Add Custom Modules In The Azure Functions App

You can add the custom modules to your Azure Functions App using the FTP. So basically what we need to do is, We will have to configure one service account using the Azure Portal that will have access to the Azure Function App FTP. Now from the FTP we can able to add the the Custom modules to the Azure Functions App in the path \Site\wwwroot\[Functionname].

Add Custom Modules In The Azure Functions App using Kudu

Another option to use external PowerShell Modules inside of you Azure Function App is to use

Advanced tools (Kudu) for this purpose. This is one of the best option to use in this case. Let’s follow the below steps

Navigate to your Azure Function app that you have created to use with PowerShell. Click on the Advanced Tools link under the Development Tools section.

Now click on the Go button on the Advanced Tools window.

Select the CMD option from the Debug console DropDown from the top navigation window.

Navigate to the subfolder site/wwwroot/{yourFunctionName}. You can able to see there that two default files run.ps1 and function.json

Click on the Home Button –> Site –> wwroot –> Click on your Function Name

Now click on the + button –> NewFolder and create a folder with the module name like below

Now you can simply drag and drop the files from your local path to this folder

Now copy the complete path from the CMD window and keep it as we need to add that in our Import statement

For me, the path is D:\home\site\wwwroot\MyHttpPowerShellFunction\azurerm

Now you need to import the powershell module in the Run.ps1 file like below

Import-Module “D:\home\site\wwwroot\MyHttpPowerShellFunction\azurerm\AzureRM.AnalysisServices.psd1”

This is one of the best option to Add Custom Modules In The Azure Functions App.

How To Load Custom Modules From The Azure Functions App

Once you upload the Custom Module in the Azure Functions App, then import the custom module in the Run. ps1 file on the Function windows as shown above. The import statement will be like below

Import-Module home\Site\wwwroot\MyHTTPPowerShellFunction\[YourModuleFolderName]\filename.psd1

Create Azure Function App Using PowerShell

We can create the Azure Function App using Powershell in the Azure PowerShell as well as we can develop our Azure Function using PowerShell in the Visual Studio Code IDE. Well, Let’s discuss here How to Create Azure Function App using PowerShell in Visual Studio Code IDE. Follow the below steps

The most important thing, Before we start the actual development, You can set up your Environment and install the Prerequisites needed, If you are creating the Azure Function for the First time using the Visual Studio Code IDE.

Create Azure Function App Using PowerShell Visual Studio Code

Assuming you have everything ready to start the Azure Function development activities, Open the Visual Studio Code IDE.

Now from the left side, click on the Azure button and then click on the Create New Project icon from the top as highlighted below.

The next step is, Browse a location for your Azure Function project where you want to store the project in your local machine. You can click on the Browse button to select your preferred location for the Project.

Now the next step is very important, Make sure to choose the language as PowerShell here.

Now the time to choose the trigger for your Azure function. Choose the HTTP trigger as your Azure function trigger. Here you can also choose the trigger as per your business requirement.

Provide the name for your PowerShell Function App

Now, you can choose the Authorization level as Anonymous, You can choose any of this based on your business requirement.

You can able to see the Azure PowerShell Function project created successfully with out any issue.

The Default Azure Functions PowerShell script

Once the Project got created successfully, It creates the default PowerShell Script file run.ps1 and this is the file which contains your actual Azure function code. Along with this file, it also creates one more JSON file named as the Function.JSON file that contains the main configuration or settings for your Azure function. Along with this it also contains the trigger and bindings for your Azure functions.

Now, If I will open my run.ps1 file, below is the code that it contains

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
}

if ($name) {
    $status = [HttpStatusCode]::OK
    $body = "Hello $name"
}
else {
    $status = [HttpStatusCode]::BadRequest
    $body = "Please pass a name on the query string or in the request body."
}

# Associate values to output bindings by calling 'Push-OutputBinding'.
Push-OutputBinding -Name Response -Value ([HttpResponseContext]@{
    StatusCode = $status
    Body = $body
})

You can see below

Now if I will open the Function.JSON file, you can find the below code present there. You can able to see this file contains all the configurations for the Azure Function

{
  "bindings": [
    {
      "authLevel": "anonymous",
      "type": "httpTrigger",
      "direction": "in",
      "name": "Request",
      "methods": [
        "get",
        "post"
      ]
    },
    {
      "type": "http",
      "direction": "out",
      "name": "Response"
    }
  ]
}

you can find the same code here

Now let’s run the Azure PowerShell function to check if it is working fine with out any issue. You can see below it executed successfully and we got the Azure function URL.

http://localhost:7071/api/MyDemoPowerShell

Now we got the function URL, So let’s see if it is working fine or not. So to test that you can paste the Azure Function URL in any of your favorite Browser. You can see it is prompting me to pass a name on the query string or in the request body and this is the expected behavior.

Now i provided a name value in the query string and now you can able to see we got the expected output. So the Azure PowerShell function is working as expected.

Create Azure Function App Using PowerShell In Azure Portal

Above, we discussed how to create Azure Functions using PowerShell Visual Studio Code. We can also able to create Azure Function App using PowerShell in Azure Portal. Follow the below steps to create the Azure PowerShell Function.

Login to the Azure Portal

Once logged in to the Azure Portal, search for the Azure Functions App and click on the search result Function App as highlighted below.

Click on the + Add button to create the Azure Function App on the Function App page.

Provide the below details for the Basics tag on the Create Function App window

1. You have to choose your valid Subscription.
2. The next option is, you need to choose your Existing Resource Group if you have a resource group already and in case, if you don’t have any existing resource group, click on the Create new link to create a new resource group.
3.  You need to enter an unique name for your Azure Function App for the Function App name option.
4. Here, For the Publish option, you can choose the Code option.
5. Since we will have to create the Azure Function App in PowerShell so you can choose the PowerShell Core for Runtime stack option.
6. It will take the latest version for the Version option . Here it is 7.0.
7. Finally, You need to select the Region for your Function App.

Now click on the Next : Hosting > button to navigate to the Hosting tab.

Provide the below option details for the Hosting tab

• Storage account: Choose your existing storage account if you have or you can click on the Create new link to create a new storage account.
• Operating system: You choose the operating system as Windows.
• Plan type: Choose your Function App plan type.

Keep the other tab value as it is and now click on the Review + Create button

Well, the next step is click on the Create button on the next window to create the Azure PowerShell Function App.

Now, you can see the deployment is completed successfully and now click on the Go to resource button to see the Function App that we created just now.

So now our Azure PowerShell Function App is ready. So the next what we need is, we need to create an Azure Functions. So to create the Azure PowerShell Function follow the below steps

Click on the Functions link from the left navigation on the Function App page and then click on the + Add button to create the new Azure PowerShell Function.

Now as we already know this, A trigger is must for the Azure function. So select the HTTP trigger from the below window

On the next window, Provide an unique name for the Azure Function and then choose the Authorization level as Anonymous and finally, click on the Create Function button to create the Azure Function.

Now you can able to see the Azure Function created successfully

You can see the function code as below. Now to make sure that the function is working fine, we can check that by clicking on the Code + Test link on the Function page and then click on the Test/Run from the top.

Provide the input values from the below window, Choose the HTTP method and provide the name value in the Body and then click on the Run Button.

We got the expected output with the proper Response code i.e 200 OK as below

Azure Functions Timer Trigger PowerShell

Above, we discussed How to create HTTP triggered Azure Function using the Azure Portal. Now we will discuss How to create An Azure Timer Trigger Function using PowerShell in Azure Portal. Follow the below steps to create the Azure Timer Trigger Function.

You can follow the same steps as mentioned above till you create the Azure Function App. Once your Function app is Deployed successfully, you can able to see the below screen. Click on the Go to resource button to open the Azure Function ap created.

Now our function app is ready, You can see the below screen shot

So the now the time to create the Azure timer triggered function since our Function app is ready now. To create the function follow the below steps

You need to click on the Functions link from the left navigation on the Function App page and then the next step is to click on the + Add button to create the new Azure timer triggered function.

Now this is a very important step, make sure to select the Timer trigger as the template on the New Function window.

Provide an unique name for your timer triggered function and then mention a Schedule based on your business need. You can click on the info icon on the format to mention for the Schedule option. Finally, click on the Create Function button to create the timer triggered PowerShell Azure function.

Now you can able to see the Azure PowerShell Timer Triggered Functions created successfully with out any issue. Refer to the below screenshot.

Below is the code for the Run.ps1 file

# Input bindings are passed in via param block.
param($Timer)

# Get the current universal time in the default string format.
$currentUTCtime = (Get-Date).ToUniversalTime()

# The 'IsPastDue' property is 'true' when the current function invocation is later than scheduled.
if ($Timer.IsPastDue) {
    Write-Host "PowerShell timer is running late!"
}

# Write an information log with the current time.
Write-Host "PowerShell timer trigger function ran! TIME: $currentUTCtime"

This is the code for the function.json file as mentioned below

“0 */5 * * * *” is known as the CRON expression. For example below are few CRON expression and their time details.You can decide based on your business

The format of the CRON expressions in Azure is, 

{second} {minute} {hour} {day} {month} {day of the week}

CRON Expression	Time Details
*/1 * * * * *	Function will execute Every second
0 * * * * *	Function will execute Every minute
0 */3 * * * *	Function will execute Every 3 minutes
0 0 * * * *	Function will execute Every hour
0 0 0 * * *	Function will execute Every day
0 0 0 * * 1-5	Function will execute Every workday (Monday to Friday)

{
  "bindings": [
    {
      "name": "Timer",
      "type": "timerTrigger",
      "direction": "in",
      "schedule": "0 */5 * * * *"
    }
  ]
}

Now click on the Test/Run and then on the Run button to check if the Function is executed successfully. As per our CRON expression “0 */5 * * * *” what we have mentioned above, so it means the function will execute each 5 minutes duration. You can able to see it is working as expected. You can refer to the below screen shot.

You may also like following the below Articles

• The term ‘Get-AzTableRow’ is not recognized as the name of a cmdlet
• How To Store Logs in Azure Functions Which Can Be Accessed Later

Wrapping Up

Well, in this article, we discussed, What Modules Are Available In Azure Functions PowerShell, Default PowerShell modules Azure Functions, Create Azure Function App Using PowerShell, Create Azure Function App Using PowerShell Visual Studio Code, Create Azure Function App Using PowerShell In Azure Portal, Azure Functions Timer Trigger PowerShell, Installing PowerShell Modules By Using Install-Module Is Not Allowed, How To Add Custom Modules In The Azure Functions App, Add Custom Modules In The Azure Functions App using Kudu, How To Load Custom Modules From The Azure Functions App. Hope you enjoyed this Article !!!.