The container in Azure Functions that is deployed, scaled and managed as one. Every function inside it shares a single hosting plan, deployment approach and runtime version.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Function app in context, with comparison tables and the common traps.
Terms in this definition
- Container
Something that groups data. Blob Storage containers sit inside a storage account and hold blobs much as folders hold files; Cosmos DB containers hold items and set the scope for partitioning and throughput.
- Authorisation levels
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.
- Model deployment
Inside a resource, each deployment is a named copy of a Foundry model with its own TPM quota and deployment type. Requests identify the model by this deployment name.
Related terms
- Blueprints
Python v2 programming model objects (func.Blueprint) for splitting a function app's functions across several modules, which are then added to the main FunctionApp by calling app.register_functions().
- Container Apps hosting
Deploying a function app as a container into a Container Apps environment, where it runs next to other microservices yet still uses the Functions programming model. Container Apps, not Functions, looks after scaling and revisions.
- Zip deployment
Pushing a .zip package to a function app, which is how Dedicated, Premium and Consumption plans deploy by default. Setting WEBSITE_RUN_FROM_PACKAGE=1 runs the app directly from that package.