This module was all about integrating data and services into your functions. We started off with a quick tour of the binding types that show up when you add them to a function. We then looked at reading data from an Azure Cosmos DB by using an input binding. The platform takes care of managing connection strings, and we saw how easy it is to read data in our code by using the binding. Finally, we focused our attention on writing data to different sources with the help of output bindings. This journey is summarized in the following table:

Unit Triggers Input bindings Output bindings
Explore input and output binding types HTTP HTTP HTTP
Read data with input bindings HTTP HTTP
Azure Cosmos DB
Write data with output bindings HTTP HTTP
Azure Cosmos DB
Azure Cosmos DB
Azure Queue Storage

You can apply the approaches you have learned here to add and test bindings in your functions. Here are a few interesting ideas to get more practice with bindings and to build on what you have learned here.

  • Create another function to read from Blob storage and other input bindings that we haven't used in this module.

  • Create another function to write to more destinations by using other supported output binding types.

  • In the preceding unit, we introduced a queue and posted messages to it with an output binding. As a next step, consider adding another function that reads the messages in the queue and prints out the MESSAGE TEXT to the console with console.log().

As we saw in this module, the Azure portal offers easy-to-use features to start building functions and connecting them to data and other services.

If you're interested in doing serverless integrations like these with visual workflows and little or no custom code, check out Azure Logic Apps as well.

Clean up

The sandbox automatically cleans up your resources when you're finished with this module.

When you're working in your own subscription, it's a good idea at the end of a project to identify whether you still need the resources you created. Resources left running can cost you money. You can delete resources individually or delete the resource group to delete the entire set of resources.

Additional Resources

Although this is not intended to be an exhaustive list, the following are some resources related to the topics covered in this module that you might find interesting:

Check your knowledge


Which of the following is an advantage of using bindings in your Azure Functions to access data sources and data sinks?


What is the name of the file that contains function configuration data?


How many triggers must a function have?


Which of the following lines of JavaScript writes "hello" to an Azure Queue Storage queue using a function parameter called myQueueItem?