An Azure resource that keeps versioned ARM templates (Bicep files are converted to JSON) so they can be shared through Azure RBAC; deploying one needs only read access.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Template spec in context, with comparison tables and the common traps.
Terms in this definition
- ARM
Short for Azure Resource Manager, the control plane Azure uses for deploying and managing resources.
- Bicep
Domain-specific language for declaring Azure infrastructure as code, which is compiled into ARM templates.
- JSON
Text-based format for structured data. ARM templates and Cosmos DB documents are written in it, and most Azure REST APIs exchange request and response bodies as application/json.
- Azure RBAC
Azure's model for granting access: built-in or custom roles are assigned at a scope to users, groups or managed identities. Calling Foundry keylessly with Entra ID requires a data-plane role, for example Foundry User (formerly Azure AI User) or Cognitive Services OpenAI User.
- CRUD
Shorthand for create, read, update and delete, the four basic things you do with data. Data-plane roles in Azure Cosmos DB, for instance, authorise those operations on items.
Related terms
- Bicep module
One Bicep file can deploy another, referencing it by a local path, a br: registry reference or a template spec; the deployed file is known as a module.
- Template Spec Contributor
A built-in Azure role that permits every template spec operation, such as adding new versions, within the scope where it is assigned.