Don’t worry about the infrastructure and provisioning of servers, especially when your Functions call rate scales up.
Write your code in the Functions editor and click run for immediate execution.
Bind into services
Easily click and add bindings to Azure services and external services (Box, DropBox, OneDrive, SendGrid, …) to get input into or output from Functions.
Develop your way
Quickly and easily iterate on Azure Functions with continuous deployment using Visual Studio Team Services, GitHub, or BitBucket. Plus, use the embedded logging environment to monitor and troubleshoot.
Pay only for what you use
Pay only for the time your code is running. You’ll be charged based on the number of resources Azure Functions needs, only for as long as it takes your code to execute.
Built for business
Use Azure Functions when events occur in internal APIs or business systems and deliver results directly to your on-premises databases or business solutions.
Common scenarios for Azure Functions
Azure Functions supports an event based on a timer using CRON job syntax. For example, you could execute code that runs every 15 minutes and cleans up a database table based on custom business logic.
Azure service event processing
Azure Functions supports triggering an event based on an activity in an Azure service. For example, you could execute serverless code that reads newly discovered test log files in an Azure Blob Storage container and transforms this into a row in an Azure SQL Database table.
SaaS event processing
Azure Functions supports triggers based on activity in a SaaS service. For example, when a file is saved in OneDrive, this triggers a function that uses the Microsoft Graph API to modify the spreadsheet, creating additional charts and calculated data.
Serverless web application architectures
Azure Functions can power a single page app. The app calls functions using the WebHook URL, saving user data and deciding what data to display. Or, you can do simple customizations, such as changing ad targeting by calling a function and passing it user profile information.
Serverless mobile backends
A mobile backend can be just a set of HTTP APIs that are called from a mobile client using the WebHook URL. For example, a mobile application could capture an image, then call an Azure Function to get an access token for uploading to blob storage. A second Azure Function is triggered by the blob upload and resizes the image to be mobile-friendly.
Real-time stream processing
For example, IoT devices send messages to Azure Stream Analytics, which then calls an Azure Function to transform the message. This function processes the data and creates a new record in an Azure SQL Database.
Real-time bot messaging
Azure Functions can be used to customize the behavior of a bot using a WebHook. For example, you can create an Azure Function that processes a message using Cortana Analytics and call this function using Bot Framework.