Powershell / Visual Studio Code: Update version of Powershell in Visual Studio Code. I'm using Visual Studio Code version 1.37.1 and the version VS-Code is using is powershell version is 5.1.18362.145. I went to GitHub and got the latest powershell version, 6.2.2 and installed it, but when I run $psversiontable in VS-Code, it tells me it's version 5.1.18362.145. I’ve used VSCode as my primary Powershell environment for over 3 years and have tried a lot of extensions and settings, and now is your turn to learn from my. The PowerShell extension for Visual Studio Code. The Azure Functions extension for Visual Studio Code. Create your local project In this section, you use Visual Studio Code to create a local Azure Functions project in PowerShell. Visual Studio Code is a cross-platform script editor by Microsoft. Together with the PowerShell extension, it provides a rich and interactive script editing experience, making it easier to write reliable PowerShell scripts. Visual Studio Code with the PowerShell extension is the recommended editor for writing PowerShell scripts.

In this article, you use Visual Studio Code to create a PowerShell function that responds to HTTP requests. After testing the code locally, you deploy it to the serverless environment of Azure Functions.

Completing this quickstart incurs a small cost of a few USD cents or less in your Azure account.

There's also a CLI-based version of this article.

Configure your environment

Before you get started, make sure you have the following requirements in place:

  • An Azure account with an active subscription. Create an account for free.

  • The Azure Functions Core Tools version 3.x.

  • Both .NET Core 3.1 runtime and .NET Core 2.1 runtime

  • Visual Studio Code on one of the supported platforms.

  • The PowerShell extension for Visual Studio Code.

    Evernote connects with the productivity tools you already use, so you can work your way. Learn more → Document scanning. Back up important documents to all your devices, and keep the information—not the clutter. Learn more → Web Clipper. Save web pages (without the ads) and mark them up with arrows, highlights, and text to. Locate 2FA setting Log in to your Evernote account, go to ‘Security Summary’ in the left-hand navigation. On the next page, you’ll see that Two-Step Verification (aka 2FA) is not enabled. Enable two-step verification on your Evernote account Sign in to your account settings. Select Security Summary from the menu, then click Enable next to 'Two-Step Verification'. Follow the steps to complete the setup process. Evernote 2 factor authentication. Two Factor Authentication (2FA) or Multifactor Authentication is the process of the authentication in which you have to provide two factors to gain the access. First Factor is the one that you know username and password and Second factor is what you might have as unique like a phone (For OTP) or Fingerprint. Create the Evernote Application in Duo Log on to the Duo Admin Panel and navigate to Applications. Click Protect an Application and locate the entry for Evernote with a protection type of '2FA with SSO self-hosted (Duo Access Gateway)' in the applications list.

  • The Azure Functions extension for Visual Studio Code.

Create your local project

In this section, you use Visual Studio Code to create a local Azure Functions project in PowerShell. Later in this article, you'll publish your function code to Azure.

  1. Choose the Azure icon in the Activity bar, then in the Azure: Functions area, select the Create new project.. icon.

  2. Choose a directory location for your project workspace and choose Select.


    These steps were designed to be completed outside of a workspace. In this case, do not select a project folder that is part of a workspace.

  3. Provide the following information at the prompts:

    • Select a language for your function project: Choose PowerShell.

    • Select a template for your project's first function: Choose HTTP trigger.

    • Provide a function name: Type HttpExample.

    • Authorization level: Choose Anonymous, which enables anyone to call your function endpoint. To learn about authorization level, see Authorization keys.

    • Select how you would like to open your project: Choose Add to workspace.

  4. Using this information, Visual Studio Code generates an Azure Functions project with an HTTP trigger. You can view the local project files in the Explorer. To learn more about files that are created, see Generated project files.

Run the function locally


Visual Studio Code integrates with Azure Functions Core tools to let you run this project on your local development computer before you publish to Azure.

  1. To call your function, press F5 to start the function app project. Output from Core Tools is displayed in the Terminal panel. Your app starts in the Terminal panel. You can see the URL endpoint of your HTTP-triggered function running locally.

    If you have trouble running on Windows, make sure that the default terminal for Visual Studio Code isn't set to WSL Bash.

  2. With Core Tools running, go to the Azure: Functions area. Under Functions, expand Local Project > Functions. Right-click (Windows) or Ctrl - click (macOS) the HttpExample function and choose Execute Function Now...

  3. In Enter request body you see the request message body value of { 'name': 'Azure' }. Press Enter to send this request message to your function.

    You could have instead sent an HTTP GET request to the http://localhost:7071/api/HttpExample address in a web browser.

  4. When the function executes locally and returns a response, a notification is raised in Visual Studio Code. Information about the function execution is shown in Terminal panel.

  5. Press Ctrl + C to stop Core Tools and disconnect the debugger.

After you've verified that the function runs correctly on your local computer, it's time to use Visual Studio Code to publish the project directly to Azure.

Sign in to Azure

Powershell Visual Studio Code Format

Before you can publish your app, you must sign in to Azure.

  1. If you aren't already signed in, choose the Azure icon in the Activity bar, then in the Azure: Functions area, choose Sign in to Azure... If you don't already have one, you can Create a free Azure account. Students can create a free Azure account for Students.

    If you're already signed in, go to the next section.

  2. When prompted in the browser, choose your Azure account and sign in using your Azure account credentials.

  3. After you've successfully signed in, you can close the new browser window. The subscriptions that belong to your Azure account are displayed in the Side bar.

Publish the project to Azure

Powershell Visual Studio Code Debug

In this section, you create a function app and related resources in your Azure subscription and then deploy your code.


Publishing to an existing function app overwrites the content of that app in Azure.

  1. Choose the Azure icon in the Activity bar, then in the Azure: Functions area, choose the Deploy to function app.. button.

  2. Provide the following information at the prompts:

    • Select folder: Choose a folder from your workspace or browse to one that contains your function app. You won't see this if you already have a valid function app opened.

    • Select subscription: Choose the subscription to use. You won't see this if you only have one subscription.

    • Select Function App in Azure: Choose - Create new Function App. (Don't choose the Advanced option, which isn't covered in this article.)

    • Enter a globally unique name for the function app: Type a name that is valid in a URL path. The name you type is validated to make sure that it's unique in Azure Functions.

    • Select a location for new resources: For better performance, choose a region near you.

    The extension shows the status of individual resources as they are being created in Azure in the notification area.

  3. When completed, the following Azure resources are created in your subscription, using names based on your function app name:

    • A resource group, which is a logical container for related resources.
    • A standard Azure Storage account, which maintains state and other information about your projects.
    • A consumption plan, which defines the underlying host for your serverless function app.
    • A function app, which provides the environment for executing your function code. A function app lets you group functions as a logical unit for easier management, deployment, and sharing of resources within the same hosting plan.
    • An Application Insights instance connected to the function app, which tracks usage of your serverless function.

    A notification is displayed after your function app is created and the deployment package is applied.


    By default, the Azure resources required by your function app are created based on the function app name you provide. By default, they are also created in the same new resource group with the function app. If you want to either customize the names of these resources or reuse existing resources, you need to instead publish the project with advanced create options.

  4. Select View Output in this notification to view the creation and deployment results, including the Azure resources that you created. If you miss the notification, select the bell icon in the lower right corner to see it again.

Run the function in Azure

  1. Back in the Azure: Functions area in the side bar, expand your subscription, your new function app, and Functions. Right-click (Windows) or Ctrl - click (macOS) the HttpExample function and choose Execute Function Now...

  2. In Enter request body you see the request message body value of { 'name': 'Azure' }. Press Enter to send this request message to your function.

  3. When the function executes in Azure and returns a response, a notification is raised in Visual Studio Code.

Clean up resources

When you continue to the next step and add an Azure Storage queue binding to your function, you'll need to keep all your resources in place to build on what you've already done.

Otherwise, you can use the following steps to delete the function app and its related resources to avoid incurring any further costs.

  1. In Visual Studio Code, press F1 to open the command palette. In the command palette, search for and select Azure Functions: Open in portal.

  2. Choose your function app, and press Enter. The function app page opens in the Azure portal.

  3. In the Overview tab, select the named link next to Resource group.

  4. In the Resource group page, review the list of included resources, and verify that they are the ones you want to delete.

  5. Select Delete resource group, and follow the instructions.

    Deletion may take a couple of minutes. When it's done, a notification appears for a few seconds. You can also select the bell icon at the top of the page to view the notification.

To learn more about Functions costs, see Estimating Consumption plan costs.

Next steps

You have used Visual Studio Code to create a function app with a simple HTTP-triggered function. In the next article, you expand that function by connecting to Azure Storage. To learn more about connecting to other Azure services, see Add bindings to an existing function in Azure Functions.

PowerShell Core is the latest version of PowerShell, and is designed to run cross-platform on Windows, Mac, and Linux.

Download the latest version of PowerShell Core that matches your installed operating system from https://github.com/PowerShell/PowerShell/releases taking note of any caveats.

Start Visual Studio Code.

Once loaded open the user settings.json file, via either:

  • use the key combination “CTRL and ,” or
  • press F1 and type settings or
  • via File menu, Preferences, Settings.

On the right hand side, between the { } section, enter the following information, to advise Visual Studio Code that you want to use PowerShell Core, and optionally also change the terminal.

If you already have lines in this file, it’s recommended to make a copy first for backup purposes, and you may also need to change the commas at the end of the lines to ensure that each setting line ends with a comma, apart from the last line.

// Specifies the full path to a PowerShell executable. Changes the installation of PowerShell used for language and debugging services. Select the relevant line that matches the installed OS, replacing version with the version installed.**

// On Windows:

// On Linux:

// On macOS:

// The path of the shell that the terminal uses. Select the relevant line that matches the installed OS.

// On Windows:

// On Linux:

// On macOS:

Example settings file that includes the lines above.

Save the settings.json file, then restart code.

To undo these changes, repeat the above but instead of adding the above lines, remove them, taking note to ensure the end of lines commas are matched up as above.

Tip: PS core by default does not know about modules used by the default installation of PowerShell, so many cmdlets will not be available.

To add these, modify the $env:psmodulepath to include:

You can either add these modules in the code, or by utilising PowerShell profiles. However, relying on profiles reduces code portability, and some developers prefer not to use profiles in order to reduce the risk of creating external dependencies that complicate running code on different machines.

Visual studio powershell add in

To use the profile option, add the following line to current PowerShell profile.

You can view the path to this file by typing $Profile into the powershell terminal at the bottom of the Visual Studio Code window.