Databricks Genie Comes to Teams: Why Definitions Matter
Resumen
Pixel’s announcement covers the Databricks Genie app launching in Microsoft Teams, Genie’s public preview in Microsoft 365 Copilot, and recent releases including Genie Ontology, Search, and Pages. With Fabric data agents and Genie able to query the same lakehouse, consistent, machine-readable metric definitions matter to prevent conflicting answers.
DEV Community
Databricks Genie Is in Microsoft Teams Now. Your Metric Definitions Just Became Production Code.
On November 9, the Databricks Genie app for Microsoft Teams went generally available. Two days later, the Genie plugin for Microsoft 365 Copilot landed in public preview. So nobody needs a notebook, a SQL editor or a Power BI report anymore. They type "how many active customers did we have last month" into the same Teams window where they argue about the sprint, and something answers. Here is the part that should make you uncomfortable. Fabric data agents already answer that question from a Power BI semantic model. Genie now answers it from Unity Catalog. Both can sit on top of the same lakehouse, and since OneLake external locations hit public preview on November 2, they can sit on top of literally the same files. Two agents. One copy of the data. Two definitions of "active customer". Both answers delivered with complete confidence, in a channel, in front of whoever happens to be reading. This is not a model problem. Both engines write decent SQL and decent DAX. The problem is that your business definitions were never written down anywhere a machine could read them, and now there are two machines reading two different places. What actually shipped in the last two weeks Worth being precise here, because the dates matter: Genie Ontology, GA on November 9. The context layer that combines knowledge you model in Unity Catalog semantics with knowledge Genie extracts from your assets and usage. Genie Search, GA on November 9. Indexes Google Drive, Jira, Confluence and Workday, and indexes each document's permissions alongside its content. Genie app in Microsoft Teams, GA on November 9. Direct message or @Databricks Genie in a channel. Pages, GA on November 11. Governed definitions of business concepts, organized by domain, with certification, deprecation, a REST API, and a new MANAGE PAGES permission. Genie plugin for Microsoft 365 Copilot, public preview on November 11. Copilot Chat talks to Genie One without an at-mention. External knowledge sources, Beta on November 5. You can pull metadata from Power BI semantic models into Azure Databricks, and Genie can use your Power BI measure definitions when it answers. Read that last one again. Databricks shipped a feature whose entire purpose is to read your Power BI measures. That is a fairly direct admission that for a lot of shops, the real semantic layer has been living in Microsoft's stack for years. The model is not the bottleneck Databricks published a benchmark for the Genie Ontology launch, built with Turing: Genie passed 91% of tasks, against 45% and 58% for two frontier agents, in roughly 100 seconds instead of 300 to 435, using fewer tokens. It is a vendor benchmark on a simulated workspace for a fictional energy supplier, so weigh it accordingly. But the caveat Databricks puts next to it is the honest and interesting part: the results "reflect an established deployment where teams have accumulated that knowledge." That sentence is the whole article. The score is not a property of the model. It is a property of how much of your business somebody bothered to write down. Genie Ontology splits that into two halves. Learned knowledge is mined from dashboards, queries and notebooks, turned into reusable snippets, ranked by authority, certification, popularity and recency, and it inherits the permissions of the asset it came from, so nobody gets context they could not already query. Modeled knowledge is what you author: metric views, domains, Pages. Learned knowledge buys you coverage. Modeled knowledge buys you authority. Only the second one is yours, and only the second one can be tested. The part you own, written down A metric view is the smallest useful piece of that. One expression, versioned, in the catalog: CREATE OR REPLACE VIEW main.sales.customer_metrics
WITH METRICS
LANGUAGE YAML
AS $$
version: 1.1
source: main.sales.fact_orders
filter: order_status <> 'CANCELLED'
joins:
- name: customers
source: main.sales.dim_customers
on: source.customer_id = customer...
Powered by Readybot.io