title: How to secure azure function with http trigger?
body: <p>I've a .net based azure function with http trigger that is just doing some basic db queries. I am invoking the function from my azure-pipeline.yml file in deploy stage.</p>
  <p>The issue right now is that the function is not secure and anyone can call it. I want to secure it somehow so that I can only call it from my pipeline (using the token probably). But I want to know what's the best approach for this? Any sample link would be appreciated.</p>
  <p>Also should I go with AD based authentication (probably client credential flow)? If yes, what's the best way to store credentials?</p>