Use the Azure Functions extension to quickly create, debug, manage, and deploy serverless apps directly from VS Code.
Visit the wiki for more information about Azure Functions and how to use the advanced features of this extension.
Sign up today for your free Azure account and receive 12 months of free popular services, $200 free credit and 25+ always free services 👉 Start Free.
-
Select Create New Function Project... in the Azure Workspace explorer or command palette.
-
In the template gallery, select an HTTP trigger template and your desired programming language.
-
Select a new, empty folder to contain your project and create the project.
-
If the selected folder is not already open, select "Open in current window" to open it.
Create New Function Project... opens the template gallery, even when a Functions project is already open. Gallery-created projects are initialized for VS Code before opening, including their language, tasks, and debugging configuration. Their programming model is detected from the copied project rather than overridden by a global default.
Create Function... adds a function to an existing Functions project using the classic template feed, including projects created from the gallery. If no Functions project exists in the selected folder, it opens project creation.
To use the previous project creation wizard, select Switch to classic in the gallery banner. This saves the user setting "azureFunctions.classicTemplateFeed": true for future project creation. The classic wizard asks for a destination again rather than reusing the gallery's launch-time folder. Disable the setting to return to the gallery.
Select the banner's Dismiss (X) button to hide it permanently without switching to classic. To show it again, enable "azureFunctions.showClassicTemplateFeedBanner" in Settings.
This extension integrates with the Azure Functions Core Tools to let you run your project locally before publishing to Azure.
-
To start your project, press F5 or the "play" button
-
If you do not have the Azure Functions Core Tools installed, you will be automatically prompted to install. Follow the specified instructions, or skip to the "Deploy" step if you would rather deploy without running locally.
TIP: The "Terminal" panel should pop up automatically and you know your project is running if you see output
-
Expand your local project in the Azure Workspace explorer to copy your function's url
-
Navigate to a browser, paste the url, and append
?name=worldTIP: Your url should look like this:
http://localhost:7071/api/HttpTrigger1?name=world -
A response of "Hello world" is returned in the browser and you know your function worked!
-
Select the "Detach" button to stop your project from running locally
-
Sign in to your Azure Account by clicking "Sign in to Azure..." in the Azure Resources explorer
If you don't already have an Azure Account, click "Create a Free Azure Account"
-
Select the 'plus' button to open the "Create Resource" menu
-
Choose "Create Function App in Azure..."
-
Enter a globally unique name for your Function App
-
If multiple versions of your language's runtime are supported (i.e. Node.js 10 and Node.js 12), select your desired version (the latest is recommended)
-
Select a location
-
Wait for your Function App to be created. Progress will be shown in the Activity Log panel
-
Once your Function App has been created, reveal the resource in the Resources view.
-
Right click your Function App and select "Deploy to Function App"
-
Once deployment is complete, expand your subscription in the Azure Resources explorer to copy your deployed function's url
-
Navigate to a browser, paste the url, and append
?name=worldTIP: Your url should look like this:
https://<function app name>.azurewebsites.net/api/HttpTrigger1?name=world -
A response of "Hello world" is returned in the browser and you know your function worked!
Every gallery project is initialized for use with VS Code, regardless of language or whether the Function App is at the workspace root or in a subfolder such as src. Initialization configures the language-specific tasks, debugger, and settings for the Function App's location. Discovery uses only the destination's files and settings; if multiple Function Apps are found, the selected default is saved only in the new project's configuration. Confirm any task-overwrite prompt to replace the template's matching tasks; unrelated custom tasks and settings, including those in JSONC files, and parent-workspace configuration are preserved. For an existing project, run Azure Functions: Initialize Project for Use with VS Code... from the workspace root.
The Node.js v4 MCP Resource template requires @azure/functions 4.12.0 or later, and the MCP Prompt template requires 4.14.0 or later, for both JavaScript and TypeScript. Function creation checks the SDK installed in the project, not just the version range in package.json. If the SDK is missing or too old, creation stops before writing the function and displays the required version and an npm install command. Run that command in the project folder and retry. The extension does not upgrade dependencies automatically.
If you're on a corporate network that performs HTTPS/SSL inspection (for example Zscaler, Netskope, Cisco Umbrella, or an internal certificate authority), Azure operations may fail with errors like unable to get local issuer certificate or self-signed certificate in certificate chain. This happens because the extension's Azure calls run in the Node.js extension host, which does not use the operating system certificate store by default.
To resolve it, point Node.js and VS Code at your corporate root CA (typically by setting NODE_EXTRA_CA_CERTS). See the certificate troubleshooting guide in the Azure Resources extension README for the full steps.
There are a couple of ways you can contribute to this repo:
- Ideas, feature requests and bugs: We are open to all ideas and we want to get rid of bugs! Use the Issues section to either report a new issue, provide your ideas or contribute to existing threads.
- Documentation: Found a typo or strangely worded sentences? Submit a PR!
- Code: Contribute bug fixes, features or design changes:
- Clone the repository locally and open in VS Code.
- Run "Extensions: Show Recommended Extensions" from the command palette and install all extensions listed under "Workspace Recommendations"
- Open the terminal (press CTRL+ `) and run
npm install. - To build, press F1 and type in
Tasks: Run Build Task. - Debug: press F5 to start debugging the extension.
This integration uses the published @microsoft/vscode-azext-utils 5.1.0 and @microsoft/vscode-azext-azureappservice 6.1.0 workflow telemetry APIs from microsoft/vscode-azuretools#2418 and microsoft/vscode-azuretools#2426.
The root events are azureFunctions.createNewProject, azureFunctions.createNewProjectWithDockerfile, azureFunctions.templateGallery.createProject, azureFunctions.deploy, azureFunctions.deployProject, azureFunctions.deploySlot, azureFunctions.redeploy, and azureFunctions.deployByFunctionAppId. The additive shared schema (workflowSchemaVersion=1) identifies the bounded workflow and command, generated workflowRunId and attemptId, isWorkflowRoot, and observed stage/outcome. Nested actions have a parentAttemptId; deployment stages and real retries are not additional user workflows. Registered literal step identities are independent of wizard runtime UUIDs. Unregistered template-supplied step names remain unknown.
Use normalized outcome, not the legacy result, to distinguish handedOff to the gallery, blocked on an unavailable prerequisite, genuine canceled dismissal, and failed pre-deploy tasks. Legacy cancellation control flow is preserved. Gallery launch is not completed project creation, and cannot execute classic creation steps. A failed task followed by "Deploy Anyway" remains a failed task stage, not a failed deployment by itself. Deployment mechanism/status and bounded failure categories distinguish task, CLI, transport, and deployment failures without recording raw messages, output, paths, URLs, resource names, or resource identifiers in the new fields.
For creation-outcome denominators, select workflow=createProject and isWorkflowRoot=true, exclude outcome=handedOff, and exclude started/child/stage records. The explicit gallery Create button starts its own root; its internal operations join that root. Measure launcher engagement separately from actual creation outcomes. This schema does not link the earlier gallery launcher to that later click, so it cannot establish cross-handoff conversion attribution. Missing terminal events and unknown outcomes must not be interpreted as success.
Shared stage events record observed active and extension-owned user-wait duration separately, in seconds. Functions-owned native-dependency and trigger-discovery retries contribute to retry/recovery metadata only when actually invoked. Trigger discovery is awaited and can fail the overall workflow even after deploymentStatus=succeeded; bounded networkCategory remains separate from that completion failure code. CLI exit or execution failure determines the command outcome, but remote deploymentStatus remains unknown without an authoritative Azure completion signal. CLI success does not prove Azure trigger/start health. The detached postDeploy notification response is correlated as a child; its wait and later work are excluded from the already-emitted root summary. Unobservable signals are unavailable, not fabricated zeros or completion. Payload tests prove instrumentation behavior, not a production failure-rate or diagnostic-coverage improvement.
When opening a newly created project restarts the extension host, cached postFunctionCreate diagnostics retain only validated, generated workflowRunId and parentAttemptId links and isWorkflowRoot=false. These replay records do not resume the normalized workflow schema, outcome, or timing, and are not creation attempts or evidence that the original root completed. Legacy cache entries without correlation remain readable and unlinked.
Keep PR descriptions brief:
Fixes #<issue>for each issue fixed; useFixes owner/repo#numberfor another repository. If no issue is linked, say so rather than inventing one.- A human-readable one- or two-line reason for the change.
- Before: a real screenshot reproducing the bug or showing the missing feature without the candidate changes.
- After: a real screenshot of the same scenario demonstrating the fix or feature with the candidate changes.
Reviews must first exercise that scenario without the candidate changes and capture a baseline screenshot, then exercise it with the candidate changes and capture a screenshot demonstrating the result. Use an isolated checkout or build; do not overwrite existing work. Screenshots supplement, not replace, regression tests and technical review.
Write each finding as one human-readable line describing the scenario and impact, with a file/line reference, severity, and smallest viable fix; attach a real screenshot showing any reported bug. Redact secrets and sensitive customer data, including resource names and user paths, from all evidence before sharing. Never fabricate screenshots or claim unperformed verification. If execution or capture is blocked, state the blocker and what remains unverified. For documentation-only or nonvisual changes, explain why screenshots do not apply and provide relevant diff, test, or other nonvisual evidence instead.
Before we can accept your pull request you will need to sign a Contribution License Agreement. All you need to do is to submit a pull request, then the PR will get appropriately labelled (e.g. cla-required, cla-norequired, cla-signed, cla-already-signed). If you already signed the agreement we will continue with reviewing the PR, otherwise system will tell you how you can sign the CLA. Once you sign the CLA all future PR's will be labeled as cla-signed.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
Project and function creation telemetry distinguishes the gallery and classic experiences, banner dismissal, template selection, creation outcomes and cancellations, dependency installation, VS Code initialization, and opening behavior. Gallery telemetry uses template IDs from the loaded official catalog and known language/experience values; it does not collect template display names, folder paths, search text, or Copilot prompts. Closing a gallery during creation is recorded separately from cancellation, since closing the panel does not stop file creation.
Language telemetry is restricted to supported language categories; other setting or argument values are reported as unknown. Creation error and exception telemetry is fully redacted in both classic and gallery flows, including the classic-banner handoff. Detailed local errors remain available for troubleshooting.
VS Code collects usage data and sends it to Microsoft to help improve our products and services. Read our privacy statement to learn more. If you don’t wish to send usage data to Microsoft, you can set the telemetry.enableTelemetry setting to false. Learn more in our FAQ.
The Azure Functions extension for VS Code follows the Modern Lifecycle Policy. Follow instructions here to get the latest updates of the extension.
| Version | Start Date | Retirement Date |
|---|---|---|
| 1.x | 10/20/2020 | In Support |








