• When asked to choose how to Publish, choose Code.
• Restrictions apply when creating multiple apps in the same resource group. For details, see the Microsoft documentation: Azure app service.
• Snowflake provides a sample “echo” function in Node.js. To use this sample function to get started.
• If asked for the Runtime stack, select Node.js.
• And for the version of Node.js, select version 12.
• When asked which OS to run the function on, choose “Windows” or “Linux”.
• If you are only creating a demo function, Snowflake recommends selecting Windows.
• Linux Function Apps cannot be edited in the Azure Portal. Users must publish the code through the Visual Studio Code interface.
• If you want to run your Azure Function on Linux rather than Microsoft Windows, see the Microsoft documentation: Azure Functions.
• Azure AD authentication is not available on Linux when using the “Consumption” pricing plan for Azure Functions. You must use an “App Service” pricing plan or “Premium” pricing plan in order to authenticate with Azure AD.

Step 2-Create an HTTP-Triggered Azure Function

After you create your Azure Function app (container), you need to create an Azure Function in the container. This function acts as the remote service. Microsoft allows Azure Functions to be called (“triggered”) different ways. A Snowflake external function invokes a remote service via an HTTP POST command, so the Azure Function you create must be an “HTTP-triggered function”.

Perform the tasks described in this section, you should be in the Function App screen in the Azure Portal. The name of your Azure Function app should be displayed, typically near the upper left corner of the screen.

To create the HTTP-triggered function:

• In the left-hand side menu tree, look for the section titled Functions. In that section, click on the item labeled Functions to add a function.
• Click on the + Add button.
• Select HTTP trigger from the list of potential triggers on the right.
• Enter the name to use for your HTTP-triggered function.
• Record this name in the “HTTP-Triggered Function name” field in your tracking worksheet.
• Enter the Authorization level.
• Snowflake recommends choosing Function as the authorization level.
• For more information about possible authorization levels, see the Microsoft documentation: HTTP-triggered functions.
• Click on the button titled Add.
• This takes you to a screen that shows the function name and, below that, the word Function.
• In the tree menu on the left-hand side, click on Code + Test.
• Replace the default code with your own code.
• Sample code for a JavaScript “echo” function is provided below.
• The function reads each row, then copies the row to the output (results). The row number is also included in the output. The output is returned as part of a multi-level dictionary.
• This function accepts and returns data in the same format (JSON) that Snowflake sends and reads. For more details about data formats, see Remote Service Input and Output Data Formats .
• Normally, the function returns HTTP code 200. If no rows are passed to the function (i.e. if the request body is empty), the function returns error code 400.

module.exports = async function(context, request) {
    context.log('JavaScript HTTP trigger function processed a request.');   if (request.body) {
        var rows = request.body.data;
        var results = [];
        rows.forEach(row => {
            results.push([row[0], row]);
        });

        results = {data: results}
        context.res = {
            status: 200,
            body: JSON.stringify(results)
        };
   }
   else {
       context.res = {
           status: 400,
           body: "Please pass data in the request body."
       };
   }
};