anchor.diff:  
   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 
positive.code: ) 
  ----
  
  Input 
  The HTTPTrigger attribute on the req param tells Azure that this function should be exposed as a HTTP endpoint, the HttpRequest is available in the req object, allowing you full access to headers, form data, etc.  
  
  Output 
  The ServiceBus attribute allows you to add messages to the Service Bus queue defined by the name and connection string in the attribute properties. 
  
  To ge the service bus binding you need https://www.nuget.org/packages/Microsoft.Azure.WebJobs.ServiceBus/3.0.0-beta5 
  
  [source, csharp]
  ----
  
negative.code: 
  ====== Bindings 
  
  Defore I get into the code I should call out the https://docs.microsoft.com/en-us/azure/azure-functions/functions-triggers-bindings[bindings and triggers] that Azure provides for interacting with Functions. There is a https://github.com/Azure/azure-functions-host/wiki/function.json[function.json] file that defines the configuration for a Function. The bindings sesiont of this json file tells Azure how the Function should be triggered and how it's output should be treated. Theres a simple example here: 
  
  [source, json]
  ----
  