title: Scalable Azure Function with blob trigger
body: <p>I made an Azure Function on a Consumption Plan with a blob trigger. Then I add lots of files to the blob and I expect the Azure Function to be invoked every time a file is added to the trigger.</p>
  
  <p>And because I use Azure Function and Consumption Plan, I would expect that there is no scalability problem, right? WRONG.</p>
  
  <p>I can easily add files to the blob faster than the Azure Function can process them. Hundred users can add to the blob but there seems to be only one instance of the Azure Function working at any one time. Meaning it can easily fall behind.</p>
  
  <p>I thought the platform would just create more instances of the Azure Function as needed. Well, it seems it doesn't.</p>
  
  <p>Any advice how I can configure my Azure Function to be truly scalable with a blob trigger?</p>