Microsoft Foundry: the response log does not explain the path

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.

Continue ReadingMicrosoft Foundry: the response log does not explain the path

Microsoft IQ: four layers, four questions

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.

Continue ReadingMicrosoft IQ: four layers, four questions

Microsoft Work IQ: the agent stops indexing Microsoft 365

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.

Continue ReadingMicrosoft Work IQ: the agent stops indexing Microsoft 365

Entra ID in Foundry: agent identity is provisioned, accountability is not

Microsoft Entra Agent ID reached general availability, and in Microsoft Foundry the agent identity is provisioned for you. Understand blueprints, the shared project identity and the RBAC that does not carry over on publish, why a sponsor is required at creation, how leaver workflows transfer sponsorship to prevent orphaned agents, and why the token subject decides where a Conditional Access policy actually lands.

Continue ReadingEntra ID in Foundry: agent identity is provisioned, accountability is not

A2A in production: delegating work does not transfer trust

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.

Continue ReadingA2A in production: delegating work does not transfer trust

Guardrails and agent evaluation: what separates a demo from a production system

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.

Continue ReadingGuardrails and agent evaluation: what separates a demo from a production system

Artificial Intelligence: a reflection on use, careers, security and how to put it to work for us

AI adoption stopped being a technology problem and became an operations and accountability problem. An executive guide to governance, the real dangers of AI, and the shift from application developer to AI engineer.

Continue ReadingArtificial Intelligence: a reflection on use, careers, security and how to put it to work for us