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().
Also called Azure Functions Python.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Blueprints in context, with comparison tables and the common traps.
Terms in this definition
- Python v2 programming model
The recommended way to write new Python apps in Azure Functions, using decorators in function_app.py (or blueprints) to declare triggers and bindings rather than function.json files.
- Function app
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.
Related terms
- Agent ID Administrator
Privileged role in Microsoft Entra for managing agent identities and blueprints across their lifecycle. Approving partner agent permissions and granting admin consent are beyond it.
- ARM template
JSON file describing Azure infrastructure declaratively. Once deployed it keeps no live connection to the resources, unlike Blueprints, which retires fully on 31 January 2027.
- Deployment stacks
Azure resources treating a set of jointly deployed resources as a single managed unit; together with Template Specs they replace Blueprints.
- Microsoft Entra Agent ID
Gives AI agents identities in Entra of their own, created from blueprints, so they fall under Conditional Access, ID Protection and governance just like users do.
- mltable Python package
Python library for working with MLTable blueprints. You call
mltable.load()on the folder holding the file, thento_pandas_dataframe()to materialise,take()to sample rows, orsave()to write a blueprint out. - project
In VCF Automation, a unit inside an organisation that decides which people may consume which resources; blueprints and vSphere Namespaces live inside it. It is distinct from an NSX Project.
- Provider Consumption Organization
The provider's own All Apps tenant within VCF Automation. It lets the provider use its own capacity, run workflows through the built-in VCF Operations orchestrator, and share catalogue items and blueprints with other tenants.
- SDK type bindings
With this feature in the Azure Functions Python v2 model, code receives proper client objects like ServiceBusReceivedMessage or BlobClient, not plain strings or bytes.