Limits set by workspace admins on what compute particular users or groups may create. The nearest thing on serverless is usage policies, which only handle tagging.
Read more: Databricks docs
In the Ultra Transcenders books
Each book explains Compute policies 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.
- Workspace
Teams in Power BI and Microsoft Fabric collaborate in this folder-style container, which groups items such as reports, semantic models and lakehouses, controls who can access them and is assigned a capacity.
- 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.
- Serverless
Compute tier for single Azure SQL databases that scales automatically, pauses when idle and charges by the second. It is offered in General Purpose and Hyperscale, not Business Critical, and reserved capacity does not apply.
- total_tokens
The usage field that sums prompt_tokens and completion_tokens, for example 37 + 86 = 123. Billing applies to both kinds of token.
Related terms
- Policy family
Templates supplied by Azure Databricks that match the default compute policies, such as Personal Compute and Job Compute. Custom policies inherit rules from a family, and families cannot be changed or removed.
- Unrestricted cluster creation
Entitlement allowing any classic compute configuration. Without it, users are limited to compute policies granted to them. Admins of the workspace always have this.