What is Budgets? · Ultra Transcenders glossary

In Cost Management, spending limits you can scope and filter by tag, which raise alerts when actual or forecast spend nears or passes them.

In the Ultra Transcenders books

Each book explains Budgets in context, with comparison tables and the common traps.

Cost Management
Azure's service for analysing costs, setting budgets and reporting by tag on resources that already run in Azure; it can't forecast what a migration will cost beforehand.
Scope
Where an access or policy assignment takes effect. It can be set on a single resource, a resource group, a subscription or a management group, and settings flow down from higher levels.
FILTER
Returns just those rows of a table that meet a condition. In CALCULATE it handles conditions too complex for a Boolean filter argument, though a Boolean filter is faster whenever one will work.
Tag
Key-value label on compute (for cost tracking) or on a Unity Catalog securable or column, applied with SET TAG or SET TAGS and requiring APPLY TAG. Governed tags restrict allowed keys, values and assigners across the account.

Action group
Azure Monitor's reusable definition of contacts and automated responses for when an alert or budget fires. Contacts can be reached by email, SMS, push or voice; responses include webhooks, Functions, Logic Apps and Automation runbooks. Budgets alone can only send notifications.
Cloud governance team
Team that evaluates the risks of using the cloud, writes rules to address them and then makes sure those rules are applied and watched everywhere. It partners with the strategy team on budgets and who is accountable for spending.
Cost reporting
Tracking spending across subscriptions by tagging resources and then grouping Cost Management budgets and reports on those tags.
Databricks budgets
Spending trackers in the account console, under Usage > Budgets, that follow monthly cost either account-wide or filtered by workspace and custom tag, emailing warnings at as many as four levels. They only alert: no compute is ever stopped.
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.usage and budgets. Classic compute isn't tagged by it.