Summary

In this chapter, we walked through creating multiple HTTP endpoints inside a single Azure Function, adding a route template to assist with managing differing URI segments at runtime. Then, we added configuration options to our project, deployed it to Azure, and adjusted the configuration options after deployment. To limit the potential cost of a deployed, live HTTP endpoint, we adjusted two settings until authorization was in place.

Now that you understand how HTTP triggers work in Azure Functions, in the next chapter, we’ll explore other types of triggers we can use to build reliable, stateful, and scalable workflows.