← AI-103: AI apps and agents on Azure
03 / 6 · 40 MIN

Agents, memory, and approvals

Orchestrate work with identity, state, and accountability boundaries.

Concept and mechanism

An agent needs a role, goal, tools, and completion conditions. The Foundry workflows discussed here are in preview. When stages depend on each other, a sequential workflow can be sufficient; dynamic coordination adds decisions and requires explicit control. Persistent memory retains context across sessions, while operational knowledge should come from governed sources. In the preview memory service, scope separates collections. A backend calling for several users must map authenticated identity to the correct scope without trusting an arbitrary client-supplied identifier. The same technical account does not mean the same end user. Define memory retention, correction, and deletion, and check preview limitations before including it in an architecture.

Guided application

In a fictional change, the agent collects state, prepares a proposal, and suspends action until approval. Approval must bind to the presented target, arguments, and version. If the service changes from A to B, a response to the old request does not authorize the new scope. Enforce mandatory rules in code or workflow while the model supports analysis. On recovery after failure, reconcile external effects and use idempotency to avoid duplicate tickets. Also define time, cost, and iteration limits. Tool results can contain malicious instructions; they remain external data and cannot expand permissions. Support must distinguish pending, approved, executed, and confirmed states.

IN PRACTICE

Approval to restart service A does not authorize restarting B even when the called function has the same name.

Common pitfalls

Browser-supplied scope as validated identity; memory as official procedure; timeout as approval; checkpoint as remote transaction rollback.

Related topics: Architecture, project, and release · Generative applications and evaluation · Visual and multimodal content

Take this idea with you

Bind each action to identity, approved scope, and evidence of its outcome.

Create account

Reference: Foundry workflows preview orchestration patterns · AI-103 skills measured2026-04-16; Microsoft Foundry documentation2026-09-30