azure functions with nuget packages that have different versions of the same dependency
I seems like an issue (AFAIK even as late as Oct 2016) that they still haven't figured out a good way of doing binding redirects in azure function.
I ran into a similar issue with my azure function using two different nuget packages with same dependency (but different versions).
There was a similar question asked here : Azure Functions binding redirect
I ended up keeping the least possible number of nugets to avoid binding redirects. If this is not possible with your project try using for webjobs (atleast as a short term solution) till azure functions supports this.