Displaying 20 to 40 from 59 results

azure-functions-python-samples - Azure Functions Python Sample Codes

  •    Python

Sample codes are Python2 compatible by default as default Python platform version that Azure Functions support is Python 2.7.X (as of July 1st, 2017). Some of the samples in the project also support Python 3.X. Please see the table below for supporting Python version of each sample.

serverless-azure-functions - Serverless Azure Functions Plugin – Add Azure Functions support to the Serverless Framework

  •    Javascript

This plugin enables Azure Functions support within the Serverless Framework. Deploy your new service to Azure! The first time you do this, you will be asked to authenticate with your Azure account, so the serverless CLI can manage Functions on your behalf. Simply follow the provided instructions, and the deployment will continue as soon as the authentication process is completed.

azure-functions-core-tools - Command line tools for Azure Functions

  •    CSharp

The Azure Functions Core Tools provide a local development experience for creating, developing, testing, running, and debugging Azure Functions. Both v1 and v2 of the runtime can be installed on Windows.

azure-functions-templates - Azure functions templates for the azure portal, CLI, and VS

  •    CSharp

This repository contains the templates used by the Azure Functions Portal and Visual Studio 2017 tooling. Templates are pre-defined functions that demonstrate a working scenario and could be used as a starting point for more complex ones. A template requires specific metadata files and folder structure so that Azure Functions Portal and Visual Studio 2017 tooling can understand and graphically present it. Certain C# templates cater only to portal whereas others are applicable to both Portal and Visual Studio 2017 tooling. The templates that are consumed by both hosts (Portal and Visual Studio) are structured differently. Please find more information on template format, individual files and their contents below.

cortana-intelligence-customer360 - This repository contains instructions and code to deploy a customer 360 profile solution on Azure stack using the Cortana Intelligence Suite

  •    Python

The Customer 360 solution provides you a scalable way to build a customer profile enriched by machine learning. It also allows you to uniformly access and operate on data across disparate data sources (while minimizing raw data movement) and leverage the power of Microsoft R Server for scalable modelling and accurate predictions. Ingestion and Pre-processing: Ingest, prepare, and aggregate live user activity data.

sherlock - :cloud: Integration testing sandbox environment provisioning tool for Microsoft Azure

  •    Javascript

Sherlock will create one or more resource groups in a subscription, and create a corresponding service principal that has rights only in that/those resource group(s). There is also a cleanup process that will routinely run to delete resource groups and service principals from past integration test runs. In essence, this is a turn-key solution that requires no administration overhead for an integration testing environment. This tool is an Azure Function app, with two functions: the first one is a web API that listens for requests to create a sandbox environment (and respond with the necessary connection information). The second Function is a cleanup process that is the cron job to remove sandbox environments in the subscription when they expire.

ailab - Experience, Learn and Code the latest breakthrough innovations with Microsoft AI

  •    Javascript

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com. When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

FunctionLibrary - A set of common use cases for Azure Functions & LogicApps that are ready to deploy!

  •    Javascript

Create an ARM template. This ARM template generator quickly creates one for Azure Functions. LogicApps code is contained in the ARM templates, so build the LogicApp in the Azure portal & commit the generated template to your Git repo.


  •    CSharp

Looking for the client SDKs? You can find them in the Azure.iOS and Azure.Android repos. Azure.Mobile is a framework for rapidly creating iOS and android apps with modern, highly-scalable backends on Azure.

azure-functions-durable-js - JavaScript library for using the Durable Functions bindings

  •    TypeScript

This library provides a shim to write your Durable Functions orchestrator functions in Node.js, using Durable's out-of-proc execution protocol. JS orchestrators have the same code constraints as C# orchestrators. Not all functionality has been implemented yet and there may be significant changes to both this library and the protocol.

azure-functions-iothub-extension - IOT Hub Extension for Azure Functions

  •    CSharp

Direct Method assumes that the device has a method matched with the specified method's name given in the argument. Otherwise, Function throws an exception. Executing direct method that takes longer than the lifetime of a Function (5 minutes by default and can be set up to 10 minutes) can never be completed.

azure-functions-language-worker-protobuf - Protobuf definitions for the gRPC connections between the script host and the language workers


This repository contains the protobuf definition file which defines the gRPC service which is used between the Azure WebJobs Script host and the Azure Functions language workers. This repo is shared across many repos in many languages (for each worker) by using git commands. To use this repo in Azure Functions language workers, follow steps below to add this repo as a subtree (Adding This Repo). If this repo is already embedded in a language worker repo, follow the steps to update the consumed file (Pulling Updates).

durablefunctions-apiscraping-nodejs - Build an Azure Durable Functions that will scrape GitHub for opened issues and store them on Azure Storage

  •    Javascript

The project requires the latest version of the Azure Functions CLI. More installation options are also available.

AzureContainerInstancesManagement - Manage Azure Container Instances using Azure Functions and Event Grid

  •    Javascript

This project allows you to manage Docker containers running on Azure Container Instances. Suppose that you want to manage a series of running Docker containers. These containers may be stateful, so classic scaling methods (via Load Balancers etc.) would not work. A classic example is multiplayer game servers, where its server has its own connections to game clients, its own state etc. Another example would be batch-style projects, where each instance would have to deal with a separate set of data. For these kind of purposes, you would need a set of Docker containers being created on demand and deleted when their job is done and they are no longer needed in order to save costs. Project contains some Functions/webhooks that can be called to create/delete/get logs from Azure Container Instances (called ACICreate,ACIDelete,ACIDetails respectively). There is a Function, called ACISetSessions, which can be used to set/report running/active sessions for each container. These sessions could be game server sessions or just 'remaining work to do'. When we create a new container, it takes some time for it to be created. When it's done and the container is running successfully, our project is notified via an Event Grid message. This message is posted to the ACIMonitor method, whose sole purpose is to listen to this messages and act appropriately. There is also a Function (ACIList) that retrieves a list of the running containers, the number of their active jobs/sessions as well as their Public IPs. This can be used to see the load of the running containers.