Key requirements for HTTP triggers in Azure Functions: Anonymous needs no key, Function accepts a function or host key, and Admin requires the master key.
Also called Azure Functions, Anonymous.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Authorisation levels in context, with comparison tables and the common traps.
Terms in this definition
- Index field attributes
Settings applied to each field in an Azure AI Search index:
searchablefor full text,retrievableto return it,filterablefor exact-match$filter,sortable,facetablefor counts, andkeyfor the unique document ID. - HTTP
Hypertext Transfer Protocol, which sends data in clear text; VCF interfaces and APIs instead use HTTPS.
Related terms
- allowBlobPublicAccess
Account-level storage property; setting it to false blocks anonymous reads on all containers regardless of what each container's access level says.
- Anomaly detection policy
Out-of-the-box policies in Defender for Cloud Apps that learn what normal looks like for each user and then alert on deviations, for example impossible travel, sign-ins from anonymous IP addresses or behaviour resembling ransomware.
- Azure Cosmos DB change feed
An ordered log, kept persistently, of what changes in a Cosmos DB container. Event-driven designs use it: Azure Functions, for example, can read it and respond.
- Azure Logic Apps
Microsoft's low-code option for automating processes and joining up applications, data and services. Each workflow is drawn on a visual canvas: it starts when something happens, then performs steps using any of hundreds of ready-made connectors, and a step may hand work to Azure Functions.
- Built-in authentication for App Service and Container Apps
Easy Auth: sign-in handled by the platform itself (as a sidecar for Container Apps), working with Entra ID, Google, GitHub, Facebook, X or any OpenID Connect provider. Turning on Require authentication turns away anonymous callers; pair it with HTTPS only.
- Consumption
Serverless, event-driven Azure Functions hosting plan charged per execution; runs are capped at 10 minutes and VNet integration isn't available.
- Consumption plan
Older serverless hosting option for Azure Functions where you pay each time code runs. Microsoft points new apps to Flex Consumption instead, and Linux apps can run under this plan only until 30 September 2028.
- Cosmos DB change feed
Durable, ordered log of what has been inserted or updated in an Azure Cosmos DB container, plus deletes when all versions and deletes mode is on. Consumers include the Azure Functions Cosmos DB trigger and the change feed processor.