Databricks Genie billing starts July 6, 2026: a cost-control playbook for admins

Summary. On July 6, 2026, Databricks began charging for Genie usage beyond a free monthly allowance, moving its text-to-SQL and AI-BI tools to a pay-as-you-go model billed in Databricks Units (DBUs). The price covers Genie Spaces, Genie Code, and Genie One together. Every identified user keeps a free monthly amount of large language model usage; service principals get none and are billed from the first DBU. Community analyses put the free allowance near 150 DBUs, about $10.50 per user each month at US East rates, but Databricks publishes the current number on its pricing page. Compute that runs the generated SQL, such as a SQL warehouse, is billed separately. Account admins can now set budgets in Unity AI Gateway with shared and per-user thresholds, alerts, and hard blocks. This playbook covers what changed, how to cap spend per user, and one SQL query that reports Genie cost by day and by person before a rollout surprises finance.

Genie is the conversational, text-to-SQL layer that lets a business user ask a question in plain English and get a governed answer from data in Unity Catalog. Until this month, that convenience was effectively free once you paid for the underlying warehouse. From July 6, 2026, the model call itself carries a price, and a wide internal rollout now has a per-user meter attached. The mechanics are worth learning before the first invoice lands, because the controls are opt-in and an admin has to turn them on.

What actually changed on July 6, 2026

Databricks documents the change plainly: "Starting July 6, 2026, Azure Databricks begins charging for Genie product usage beyond a free monthly allowance." Three products share the same pay-as-you-go pricing model, per the Genie budgets documentation: Genie Spaces (the conversational rooms analysts build over a dataset), Genie Code (the agentic coding surface), and Genie One. Usage above the free amount is billed in DBUs based on the underlying LLM consumption.

Two details decide most of the budget math. First, the free monthly allowance applies to identified users, meaning people, not to service principals. A service principal that runs a scheduled Genie query receives no free allowance and is billed for all of its usage. Second, the DBU price covers the model call only. The compute that executes the generated SQL, such as a Databricks SQL warehouse, is billed separately and is not counted inside a Genie budget. A team that reads "Genie is now metered" and assumes the warehouse bill is included will misjudge the total.

The precise free-allowance figure is the one number Databricks keeps on its pricing page rather than in the how-to. The vendor documentation says only that "each user receives a free amount of LLM usage every month" and points to the Databricks pricing page for the current value. Independent write-ups, including a Dev Genius breakdown and posts in the Databricks community, estimate the allowance at roughly 150 DBUs per user, near $10.50 a month at US East list rates. Treat that as an estimate and confirm the live figure for your region before you model a fleet.

Genie cost item	How it is billed	What an admin should note
Free monthly LLM allowance	Free, per identified user	People only; a budget cannot remove or extend it
Usage above the allowance	Pay-as-you-go in DBUs	Tracked by Unity AI Gateway budgets
Service principal usage	Billed from the first DBU	No free allowance at all
SQL warehouse compute	Billed separately	Not included in a Genie budget
Genie Spaces, Code, and One	One shared price and tag	All roll up under databricks-product: genie

How Genie billing works, in DBUs

A DBU is Databricks' unit of processing, and its dollar value depends on the SKU and tier you run. Public pricing summaries such as Costbench show Databricks products spanning a wide DBU range across tiers, so a Genie DBU is not the same dollar amount everywhere. For a Genie budget you rarely need the raw per-DBU rate up front, because budgets are set in dollars and the platform converts usage for you. You do need the rate when you reconcile the bill, which is where the billing system tables come in later.

The important behaviour is that the meter runs per person and resets monthly. A ten-analyst team where three people live in Genie all day and seven touch it occasionally will show a very uneven spend curve. Without per-user caps, the three heavy users can consume most of a shared pool while the platform keeps answering. That is the pattern budgets exist to catch.

Set a Genie budget in Unity AI Gateway

Budgets for Genie live in Unity AI Gateway and are created in the account console. You need to be an account admin, and the Unity AI Gateway Budget public preview has to be enabled for your account. The steps below follow Databricks' own procedure.

1. In the account console sidebar, open Usage, then the Budgets tab, then Create budget.
2. Under Scope, name the budget and choose the workspaces it covers. Leave the workspace field empty to track the whole account.
3. Set the Resource type to Unity AI Gateway.
4. Under Resource tags, add the key databricks-product with the value genie. Do not add any other tag. Extra tags stop the budget from tracking Genie usage.
5. Add a shared threshold if you want a single pool across everyone in scope, then add per-user thresholds so each person carries their own cap.
6. For each threshold, choose Send alert, Block usage, or both, and enter the email addresses that should receive alerts.
7. Add per-user overrides for teams that legitimately need a higher cap.

Databricks recommends a specific pattern: use Send alert on the shared threshold, then use per-user thresholds and overrides to do the actual blocking. A blanket block on the shared pool stops Genie for everyone the moment the account total is reached, which turns one heavy user into an outage for the whole company.

The per-user cap, with Databricks' own example

The documentation walks through a concrete configuration that is worth copying. A budget scoped to Genie in one workspace sets a shared threshold of $5,000 and a per-user threshold of $100. Per-user overrides then give the genie-code group a higher limit of $200 and the power-users group $300 a month. If a user belongs to both genie-code and power-users, they inherit the more permissive limit of $300.

That last point is the rule that trips people up. Within a single budget, when a user matches more than one group threshold, the most permissive limit applies. Across separate budgets, the logic reverses: the most restrictive limit wins. If one budget grants a user $200 and another grants the same user $100, the platform blocks them at $100. Model your groups with that asymmetry in mind, or a user will hit a lower cap than you expected.

Query Genie cost in SQL

Alerts tell you when a threshold is reached. To see where the money actually went, query the billable usage system table after pay-as-you-go billing begins. The following query, from the Databricks documentation, totals DBUs and list-price cost for Genie, grouped by date, user, and Genie metadata. It joins system.billing.usage with system.billing.list_prices so each usage record gets the correct price.

SELECT
  u.usage_date,
  u.identity_metadata.run_as,
  u.usage_metadata.genie,
  SUM(u.usage_quantity) AS total_dbus,
  SUM(u.usage_quantity * lp.pricing.effective_list.default) AS total_cost
FROM system.billing.usage u
JOIN system.billing.list_prices lp
  ON u.cloud = lp.cloud
  AND u.sku_name = lp.sku_name
  AND u.usage_start_time >= lp.price_start_time
  AND (lp.price_end_time IS NULL OR u.usage_start_time < lp.price_end_time)
WHERE
  u.billing_origin_product = 'GENIE'
GROUP BY ALL

Filtering on billing_origin_product = 'GENIE' isolates Genie from the rest of your Databricks usage, and grouping by run_as gives you a per-person cost table you can hand to finance. Schedule it as a daily job and you have a chargeback feed without waiting for the monthly invoice. The same billable-usage table underpins broader cloud cost chargeback work, so a Genie feed slots into an existing FinOps dashboard rather than living on its own.

Alert or block: choose per threshold

Every threshold carries an action. Send alert emails the listed addresses and lets the user keep working. Block usage stops Genie for that user until the budget resets or an admin raises the limit, and the user sees a message that their budget is exhausted. Both keep the free monthly allowance intact; a budget can never remove it.

Behaviour at the threshold	Send alert	Block usage
User can keep querying	Yes	No, until reset or an override
Who is notified	Listed email addresses	The user sees an in-product message
Free monthly allowance	Preserved	Preserved
Best use	Shared pool, early warning	Per-user or per-group hard cap
Risk if misused	Spend continues silently	A blanket block can stop everyone

One caveat matters for anyone relying on a hard stop. When Block usage fires, a small amount of spend beyond the threshold can still occur. Active Genie requests already in flight are not interrupted, and there is a brief delay before the block is enforced. Treat the cap as a firm ceiling with a little give, not a to-the-cent guillotine, and leave a margin below the number that would actually hurt.

A cost-control playbook before you scale Genie

The controls only help if they are in place before adoption climbs. Run this sequence before you invite a wide user base into Genie.

1. Enable the Unity AI Gateway Budget preview and confirm you have account admin rights.
2. Create one budget scoped to Genie with the databricks-product: genie tag and nothing else.
3. Set a per-user threshold that matches a sane monthly ceiling for a typical analyst, and alert rather than block on the shared pool.
4. Add overrides only for the groups that genuinely need them, and document why each exists.
5. Convert every shared service principal to a named, budgeted identity where you can, because service principals have no free allowance and are billed from the first DBU.
6. Schedule the billing-table query daily and route the output into your existing cost dashboard.
7. Remember that the SQL warehouse behind Genie is a separate line item, and size or auto-stop it as part of the same review.

Teams already running a cloud FinOps practice for Indian teams will recognise the shape of this: meter, cap, chargeback, review. Genie simply adds a new metered product to the same loop, in the way Azure FinOps and Copilot cost controls and the AWS FinOps agent preview added theirs earlier in 2026.

India-specific considerations

For Indian data teams, two points deserve attention. The first is currency planning. Databricks bills in US dollars against DBU list prices, so a rupee budget has to absorb foreign-exchange movement. If you set an internal ceiling of, say, ₹8,000 per analyst each month, convert that to a dollar per-user threshold in the budget and re-check the rate each quarter rather than assuming a fixed conversion.

The second is data protection. Budget email notifications include the budget name, the user identity for per-user thresholds, and any custom tags you defined. That means a person's name and their month-to-date Genie spend leave the platform in an email to whichever addresses you list, and recipients do not have to be Databricks users. Under the Digital Personal Data Protection Act, 2023 (DPDP), that is personal data moving to named recipients, so keep the alert distribution list tight, avoid putting sensitive labels in budget or tag names, and treat the notification list as you would any other export of employee data. Genie's answers themselves stay governed by Unity Catalog permissions, which is a separate control from the budget.

FAQ

When did Databricks Genie start charging, and for which products?

Databricks began pay-as-you-go billing for Genie on July 6, 2026. The single price covers Genie Spaces, Genie Code, and Genie One, which share one pricing model and the databricks-product: genie tag. Usage above each user's free monthly allowance is billed in DBUs based on the underlying large language model consumption.

What is the free monthly allowance for Genie?

Every identified user receives a free monthly amount of LLM usage. Databricks keeps the exact figure on its pricing page rather than in the documentation. Community analyses estimate it near 150 DBUs, about $10.50 per user each month at US East list rates. Confirm the current number for your region before modelling a fleet.

Do service principals get a free Genie allowance?

No. The free monthly allowance applies only to identified users, meaning people. A service principal receives no free allowance and is billed for all of its Genie usage from the first DBU. Where you run scheduled or automated Genie queries under a service principal, budget for that usage separately and expect no free tier.

Is the SQL warehouse compute included in a Genie budget?

No. A Genie budget tracks the LLM usage that powers the conversational layer. The compute that runs the generated SQL, such as a Databricks SQL warehouse, is billed separately and does not count against the Genie budget. Size and auto-stop that warehouse as part of the same cost review to control the full spend.

How do I cap each user's Genie spend?

Create a budget scoped to Genie in Unity AI Gateway and set a per-user threshold, for example $100 a month. The cap applies to every user in scope on top of their free allowance. Add per-user or per-group overrides for teams that need more, and choose Block usage to enforce a hard stop.

What happens to in-flight queries when a block triggers?

Block usage stops new Genie requests once the threshold is reached, but a small amount of spend can still occur. Requests already in progress are not interrupted, and there is a brief delay before the block takes effect. Set the cap a little below the figure that would genuinely hurt, so the spillover stays harmless.

Which limit applies when a user matches several thresholds?

Within one budget, the most permissive threshold wins: a user in two groups set to $200 and $300 gets $300. Across separate budgets, the most restrictive limit wins: $200 in one budget and $100 in another blocks the user at $100. Design group membership with that asymmetry in mind.

How do I see exactly where Genie spend went?

Query the system.billing.usage table, joined to system.billing.list_prices, filtered on billing_origin_product = 'GENIE'. Group by usage date and the run_as identity to get a per-person, per-day cost table. Schedule it daily and route the output into your FinOps dashboard for a chargeback feed that does not wait for the monthly invoice.

How eCorpIT can help

eCorpIT is a Gurugram software and data engineering organisation with senior-led teams and an ISO 27001:2022-certified delivery process. We help data platform teams roll out Genie and other AI-BI tools with cost governance built in from day one: Unity AI Gateway budgets scoped correctly, per-user and per-group caps that match real usage, a scheduled billing-table feed into your FinOps dashboard, and a service-principal review so nothing bills silently. If a metered Genie rollout is on your roadmap and you want the guardrails set before adoption climbs, talk to our engineering team about a cost-control and analytics-governance review.

References

1. Manage budgets and cost controls for Genie, Azure Databricks documentation
2. Manage budgets and cost controls for Genie, Databricks on AWS
3. Manage budgets and cost controls for Genie, Databricks on Google Cloud
4. What's coming, Azure Databricks release notes
5. Unity AI Gateway, Azure Databricks documentation
6. Billable usage system table reference, Azure Databricks
7. Create and monitor budgets, Azure Databricks documentation
8. Databricks pricing page
9. Databricks Genie pricing: what actually changes in July 2026, Dev Genius
10. Databricks Genie pricing, Databricks community MVP article
11. Databricks pricing tiers overview, Costbench

Last updated: July 29, 2026.