Deploying the Functions runtime as a private site extension

If you already have a Function App, you can use the following steps to deploy your own Functions runtime as a private site extension. Note that these steps only work on Classic Functions Apps and not on Dynamic Function Apps.

• First you need a Functions.Private.zip site extension package in the proper format
  • you can get one from our CI machine output for a particular build, e.g. https://ci.appveyor.com/project/appsvc/azure-webjobs-sdk-script-y8o14/build/1.0.10650/artifacts
  • or you can build the private package yourself:
    • In VS, right click the WebJobs.Script.WebHost project and choose Publish
    • Select the existing File System profile and click Publish. This will create the bits under src\WebJobs.Script.WebHost\Publish
• Go to the Kudu Console for the function app that you want to use your bits on. Make sure you use a Function App in Classic mode (i.e. not Dynamic), or it will not work.
• Drag and drop the SiteExtensions folder from your machine (in src\WebJobs.Script.WebHost\Publish), into the root of your Kudu Console. i.e. this should create d:\home\SiteExtensions\Functions
• In the Kudu Process Explorer, kill the main site (the w3wp that doesn't say scm)

You are now using your private Functions runtime.