Azure Functions is a serverless compute service that lets you run event-triggered code without having to explicitly provision or manage infrastructure, in other words, Microsoft’s Azure Functions is a modern serverless architecture, offering event-driven cloud computing that is easy for developers to use. This blog is about Azure Functions triggers and bindings.

You may know my series of blog posts about BizTalk Server Tips and Tricks that I normally write in the BizTalk360 blog. Well, the goal of this Logic Apps Tips and Tricks series will be the same; to provide simple tips or tricks that may improve your performance on developing Logic Apps workflows, avoiding issues, apply best practices and so on. But you may think, “What a strange way to start this topic, deprecated actions? Why should I use deprecated actions?”.

It is really exciting to see the Azure Functions team back again to the monthly live webcast after quite a long time. Here is a bit of introduction about this webcast who is new to the community, the Azure Functions team at Microsoft has been conducting a webcast every month to let the community stay up-to-date on the latest developments. This is a nice way for them to reach out and engage with the community to gain feedback on the features.

This blog focuses on implementing the Dependency Injection design pattern to the Azure Functions. For a better understanding of Dependency Injection and Azure Function, Let’s take a simple Cab booking validation scenario, in which there will be a Function app implemented with the Dependency Injection that validates the user email Id that is valid or not. Before diving into the orchestration, let us know what the Dependency Injection is.