anchor.diff:  
   Depending on SDK you are using (C# here but the Java SDK is very similar) the bindings into a Function can be autogenerated from attributes on the parameters. A future version of the runtime will remove the need for having the bindings section and the just the attributes will be used. 
   
  -The bindings list here gives a good view as to what is supported for interacting with other Azure products. The HTTP and Timer are probably the two simplest bindings. 
  +The bindings list https://docs.microsoft.com/en-us/azure/azure-functions/functions-triggers-bindings#supported-bindings[here] gives a good view as to what is supported for interacting with other Azure products. The HTTP and Timer are probably the two simplest bindings. 
   
   In my examples below I'm mostly working with HTTP, Service Bus, CosmosDB and Blob inputs/outputs. 
  -
  -https://docs.microsoft.com/en-us/azure/azure-functions/functions-triggers-bindings#supported-bindings 
   
   Disclaimer, all these examples are trivial and contrived, none even resemble a prototype. 
   
   ====== Trigger Movie Process 
  +
  +.
  +image:azure_functions/part1/seq1.png[]
   
   The first Azure Function is triggered by a HTTP call and sends an event to Service Bus when the function is triggered. 
   
  
positive.code: 
  return; 
  ----
   
  
  In the snippet above I grab the data from a CSV hosted on github and upload it to the blob on Azure Storage. 
  
  
negative.code: 
  The runtime gives some good logs around which Functions have been detected and what URLs HTTP triggered Functions can be invoked from. 
  
  image:azure_functions/part1/detecting_functions.png[]
  image:azure_functions/part1/http_trigger_functions.png[]
  
  That’s all I'm going to cover in this part, in the next article I'll look at Functions that process the blob and Write to CosmosDB 