Build Azure Functions using PowerShell Core 6 & VS Code!

I’ve been creating Azure Function using PowerShell since it was added as an option in their “Experimental Language Support” in V1.0. In fact, It was almost a year to the day that I wrote my first blog post about how I used Azure Functions to make PowerBI work nicely with Graph.

So, it only seems fitting now that the public preview of PowerShell support for Azure Functions V2 has been released, that I demonstrate not only how to create a PowerShell function, but how to create, test AND deploy the function entirely in VS Code!

Before we get into this amazing new era of serverless computing, we need to set up our development environment with the following pre-requirements:

For the sake of brevity, this guide will assume you are setting your development environment up using a 64-bit Windows operating system.

Once you’ve set up your development environment, fire up VS Code and select the Azure icon in the sidebar.

Sign in to your Azure account by clicking the very obvious link and following the bouncing ball. (This isn’t necessary right now, but it’s handy to connect to you Azure tenant.)

Once you are signed in, you will see your subscription, along with any other existing functions previously created.

Now let’s get started onto the fun stuff. Open up the command palette (F1), search for Azure Functions and select Create New Project…

Save your project somewhere locally, then select PowerShell (Preview) as your development language.

For this scenario we are going to create a basic web API, so select HTTP trigger, but take some time to view all the options now made available to us in Azure Functions V2.0

Give your function a name, and set the authorization level to Function

Finally, select Add to Workspace.

You should now be greeted with the basic scaffold of an Azure Function App. Key files of mention here are:

  • Function.json – Where all IN / OUT bindings for your function are defined and configured.
  • Run.ps1 – The PowerShell code that is run when the function is triggered.
  • Host.json – The configuration file for the entire project.
  • Local.settings.json – Where all environment variables can be defined.

Now let’s run the sample function to make sure everything is working as it should be.

Open run.ps1 – the first thing we will need to do is switch the Terminal session from the default 5.1 to PowerShell Core 6.


On the notifications tray of VS Code click on the green 5.1 PowerShell icon to launch the session menu.


In the session menu, select Switch to: PowerShell Core 6 (x64) and select Yes when asked to start a new session.

You should now see a green 6.2 PowerShell icon in the notifications tray.
Finally, Hit F5 to launch the function app into VS Code!

Once the app has finished launching, you should see the endpoint URL in the terminal output. Select and copy this to the clipboard.

Now, let’s switch over to the PowerShell Console (or just open up another PowerShell terminal window!)

The template Function that is provided with the scaffold is a simple “Hello World” HTTP trigger which is simply looking for a Name property, so using the URL generated from the Function App, let’s send a request and see what happens.

Invoke-RestMethod -Method Get -Uri http://localhost:7071/api/Powers-Hell_HTTP-Trigger?Name=Ben

When we run that command we should receive back a very exciting response from the Function!

And there you have it – a locally run Function App using PowerShell Core 6 & VS Code!

Stay tuned for my next post, where I’ll take everything we’ve gone over here and turn it into a way to modernize logon scripts for Intune managed devices!

Leave A Comment

Please be polite. We appreciate that. Your email address will not be published and required fields are marked