Azure resources treating a set of jointly deployed resources as a single managed unit; together with Template Specs they replace Blueprints.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Deployment stacks in context, with comparison tables and the common traps.
Terms in this definition
- Set
Secret permission in Key Vault for writing secrets; some older material refers to it as Create.
- Template Specs
Azure resources that hold versioned ARM templates. Alongside deployment stacks, they are the successor to Azure Blueprints.
- 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().
Related terms
- Azure Blueprints
Deprecated service bundling policies, roles and templates, each assignment staying live-linked and scoped to a single subscription. Nothing new could be defined after 31 July 2026, and on 31 January 2027 it retires in favour of deployment stacks and Template Specs.
- Azure Deployment Stack Contributor
Can manage deployment stacks, but has no right to add or remove deny assignments; an Azure built-in role.
- Deny assignments
Azure RBAC entries that block actions even where a role assignment allows them. Once only Azure services such as deployment stacks made them; users can now create them too (New-AzDenyAssignment or az role deny-assignment create), covering write, delete and action operations but not groups.