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.
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 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.
When a RAG agent answers wrong, the model is rarely at fault: the right passage never reached the context. This article splits retrieval into three budgets that fail for different reasons — recall, precision, and passage context — and shows what fixes each one: structure-aware chunking, hybrid search with rank fusion, second-stage reranking, and retrieval measured separately from the answer.
A2A connects independent agents; MCP connects tools and resources. Understand tasks, identity, and trust across delegation, then follow a complete Python example to deploy and call an A2A agent in Microsoft Foundry, with RBAC and explicit preview limitations.
A private endpoint controls ingress; it authenticates nobody and does not decide where the agent writes afterwards. The three boundaries of an AI workload — entrance, identity, and exit —, the three DNS zones Foundry requires, the roles that were renamed, and the egress control almost every project leaves open.
Guardrails contain at runtime; evaluation measures over time — and neither does the other's job. Content Safety, Prompt Shields, evaluators that see the tool call and not just the answer, red teaming with PyRIT, and the maturity signal that separates a demo from a system: a deployment blocked by a number.