The response log keeps what the agent said, not the path it took. The Foundry trace keeps the order of the steps, the failures and the tokens of each turn, and leaves the content to a protected table. See what the trace shows, who can see the content and what changed in Agent Framework 1.22.0, with an example run locally.
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.
Learn to discover paths, inspect schemas, and read messages with Work IQ MCP. A read-only example shows why fewer tools do not remove access, coverage, and authorization boundaries.
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.
The deploy went green, and a full refresh wiped the bronze table that Kafka could no longer replay. In Databricks Lakeflow, the bundle carries the code from dev to prod, but state stays in each environment: the deployment record, the streaming checkpoints, the tables themselves and the identity that runs the pipeline. This article shows the four states the bundle does not carry, what each command can delete and the guards you declare in the bundle before the first production deploy.
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.
The user prompt was clean. The hostile instruction came in through the content the tool brought back — and that is the door almost no security review looks at. This article gathers what moved in the 2026 OWASP Top 10, the two Prompt Shields intervention points, the spotlighting that ships off by default, what the MCP specification protects and what it leaves to you — and shows what has to be in place so a successful injection does not become impact.
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.