AI-103: Developing AI Apps and Agents on Azure

By Microsoft · Question Mode

QuestionQ48

VerifiedImplement generative AI and agentic solutions

You have a customer support agent that uses the Microsoft Foundry Agent Service.

Customers sometimes return to a session days later to continue the same support case, and the agent must resume with the full historical context. The agent must provide:

  • Multi-turn continuity within the session.
  • Cross-session continuity for the same case.
  • Access to the full interaction history, including user messages, agent messages, tool calls, and tool outputs.

You need to ensure that the agent automatically reloads the complete history on every new turn.

What should you do?

Explanation

The Foundry Agent Service persists the full interaction history — user messages, agent messages, tool calls, and tool outputs — server-side under a durable conversation identifier. Storing that conversation ID and supplying it on every subsequent request causes the service to automatically reload the complete history for that case on each new turn, giving both multi-turn continuity within a session and cross-session continuity when the customer returns later. Persisting only the final model response discards all tool-call and tool-output detail, and enabling memory summarization condenses the history into a summary rather than reloading it in full.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!