Your own key-value labels, attached to compute, pools, SQL warehouses or whole workspaces. They appear in usage records and in Azure cost reports, which makes it possible to charge spending back, and a compute policy can insist on them.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Custom tags in context, with comparison tables and the common traps.
Terms in this definition
- 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.
- Compute policy
Limits, set by an admin, on what can be chosen when people create classic compute; they help contain cost and require particular custom tags, libraries or init scripts.
Related terms
- Serverless usage policy
A Public Preview feature that automatically attaches custom tags to the serverless notebooks, jobs, pipelines and serving endpoints a user runs, letting their cost be traced in
system.billing.usageand budgets. Classic compute isn't tagged by it.