Controlling access to Azure Functions using function keys
You have now learned how to enable the authorization of an individual HTTP trigger by setting the Authorization level field with the Function value in the Integrate tab of the HTTP trigger function. It works well when we use only one Azure function as a back-end web API for one of the applications and we don't want to provide access to the public.
However, in enterprise-level applications, we will end up developing multiple Azure functions across multiple function apps. In those cases, we need to have fine-grained granular access to Azure Functions for our own applications or for some other third-party applications that integrate our APIs in their applications.
This recipe will focus on understanding how to work with function keys within Azure Functions.
How to do it…
Azure supports the following keys, which can be used to control access to Azure functions:
- Function keys: These can be used to...
