Declaring a quality rule is not blocking the data. In Delta, NOT NULL and CHECK block; in Lakeflow, an expectation with no action retains the row; keys and unique only declare; MERGE ignores the new column. See what each layer does, how to build a quarantine and how to read the count, with an example run locally.
An agent can consume Copilot Credits in Work IQ, capacity in Fabric, and tokens or PTUs in Foundry. Examine the meters, a calculated example, and how to separate consumption, attributed cost, and the invoice without counting an operation twice.
The slide had a single box labeled Microsoft IQ, and the relationship manager's agent got one question right out of four. Microsoft IQ is the name of a set: Work IQ, Fabric IQ, Foundry IQ and Web IQ, each with its own question, data home, status per component, identity and boundary. This article maps the four layers: what is GA and what is in preview, who answers in each one, where they meet and how far the data goes.
RAG over Microsoft 365 used to be your pipeline: a connector, a vector index, a sync job and permissions re-created by hand. Microsoft Work IQ takes that pipeline out of your hands — and charges in identity: there is no application-only authentication, every call runs as a person and tenant policy blocks writes by default. This article shows what changes, what stays with you and how to compose Work IQ with Foundry, Microsoft Fabric data agents and Databricks Genie without swapping the identity on the way.
The demo convinces, the workspace disagrees. In Microsoft Fabric the ontology is now a real item: a REST API, a definition in files and a child graph created on its own — and it is that child that issues the bill. This article gathers what the item really is, why every refresh is full and freshness became a cost decision, the four capacity meters, how far binding actually reaches, three points where the official documentation contradicts itself — and what has to be in place before switching this on in production.
Five sources per agent, answers capped at 25 rows by 25 columns, documented support for English only, and read-only queries: the Fabric data agent has an entry contract no prompt renegotiates. This article gathers the six source categories, the output limits, the asking user's identity, and the two retirements of 26 August — and shows what has to be in place before the pilot becomes a commitment to the business.
A vector index is a copy, and a copy inherits no permissions: the Databricks AI Search documentation states that row and column level permissions are not supported. The two routes an agent takes to the data — RAG and text-to-SQL —, where the access rule lives on each one, the Genie Agent's two credentials, and the metric layer that stops the number from changing.
Federating, mirroring, and ingesting are not synonyms — and in Fabric "mirroring" already means three different mechanisms. When to use Lakehouse Federation, when to mirror a catalog or a database into Microsoft Fabric, when to ingest with Lakeflow Connect, what is actually free, and why source permissions do not cross the OneLake boundary.
The bottleneck of enterprise AI is not the model, it is governed business context. How Unity Catalog Metric Views, Genie Ontology and Fabric IQ form a single semantic layer over one copy of the data — with an FSI use case, cost model and roadmap.