One of the hippest tech around right now might be Microsoft foundry. It has MCP, and agent integrations in a very easy UI friendly way.

We use Microsoft foundry Workflows to make multi agent conversations that check Compliance, risk, and other things we might need a multi agent flow for.

Why multi agent. Agents are confidently wrong sometimes, we therefor step inn as humans when in a one to one conversation and tell it to “check that again”. But what if we had a agent that had its entire job to argue with the reasoning, quality, and accuracy of the other agents and make them try again to justify their answers. This is why multi agent flows may be better at providing correct answers.

But the agent-foolery does not stop there. When our data reaches Fabric we can use fabric data agents to ground the reasoning for our multi agent flows. The fabric data agent has the ability to do queries in fabric, and figure out complex questions, and provide a data driven answer. Now THAT is hip.

Most of these resources are directly API compatible, and can be in some way or form be directly integrate with Terraform. but some need dirty workarounds because sometimes we fool with tech that is so hip it does not have a API.

We are also atempting to claim The Existential Risk badge with this post.

Our agents does have guardrails. Jailbreak is a part of this and should handle attempts at injecting commands inn to the permit application.

Testing this proved that when it can argue why it should not follow the instructions it will, but when it decides that it is “grounds for blocking” it will also do that.