From f08b5d8272c7e39d3b708e6c2c29766b6db1715c Mon Sep 17 00:00:00 2001 From: Roger Barreto <19890735+rogerbarreto@users.noreply.github.com> Date: Mon, 19 Jan 2026 14:29:49 +0000 Subject: [PATCH 1/3] Improve readme for agents V2 --- dotnet/samples/GettingStarted/FoundryAgents/README.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/dotnet/samples/GettingStarted/FoundryAgents/README.md b/dotnet/samples/GettingStarted/FoundryAgents/README.md index daeb2db8df..c22c684cc1 100644 --- a/dotnet/samples/GettingStarted/FoundryAgents/README.md +++ b/dotnet/samples/GettingStarted/FoundryAgents/README.md @@ -15,6 +15,15 @@ For more information about the previous classic agents and for what's new in Fou For a sample demonstrating how to use classic Foundry Agents, see the following: [Agent with Azure AI Persistent](../AgentProviders/Agent_With_AzureAIAgentsPersistent/README.md). +## Agent Versioning and Static Definitions + +One of the key architectural changes in the new Foundry Agents compared to the classic experience is how agent definitions are handled. In the new architecture, agents have **versions** and their definitions are established at creation time. This means that the agent's configuration—including instructions, tools, and options—is fixed when the agent version is created. + +> [!IMPORTANT] +> Agent versions are static and strictly adhere to their original definition. Any attempt to provide or override tools, instructions, or options during an agent run or request will be ignored by the agent, as the API does not support runtime configuration changes. All agent behavior must be defined at agent creation time. + +This design ensures consistency and predictability in agent behavior across all interactions with a specific agent version. + ## Getting started with Foundry Agents prerequisites Before you begin, ensure you have the following prerequisites: From 3efa4ac0182744517b1befa7e036a6d0613ad3f2 Mon Sep 17 00:00:00 2001 From: Roger Barreto <19890735+rogerbarreto@users.noreply.github.com> Date: Mon, 19 Jan 2026 14:37:39 +0000 Subject: [PATCH 2/3] Architectural justification --- dotnet/samples/GettingStarted/FoundryAgents/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/dotnet/samples/GettingStarted/FoundryAgents/README.md b/dotnet/samples/GettingStarted/FoundryAgents/README.md index c22c684cc1..19bafb5d1b 100644 --- a/dotnet/samples/GettingStarted/FoundryAgents/README.md +++ b/dotnet/samples/GettingStarted/FoundryAgents/README.md @@ -24,6 +24,8 @@ One of the key architectural changes in the new Foundry Agents compared to the c This design ensures consistency and predictability in agent behavior across all interactions with a specific agent version. +The Agent Framework intentionally ignores unsupported runtime parameters rather than throwing exceptions. This abstraction-first approach ensures that code written against the unified agent abstraction remains portable across providers (OpenAI, Azure OpenAI, Foundry Agents) without requiring provider-specific conditional logic. Teams can adopt Foundry Agents without rewriting existing orchestration code—configurations that work with other providers will gracefully degrade rather than fail when the underlying API does not support them. + ## Getting started with Foundry Agents prerequisites Before you begin, ensure you have the following prerequisites: From a796695e1da670f822e24a8b041261a2985a54a1 Mon Sep 17 00:00:00 2001 From: Roger Barreto <19890735+rogerbarreto@users.noreply.github.com> Date: Mon, 19 Jan 2026 14:53:53 +0000 Subject: [PATCH 3/3] Update dotnet/samples/GettingStarted/FoundryAgents/README.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- dotnet/samples/GettingStarted/FoundryAgents/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dotnet/samples/GettingStarted/FoundryAgents/README.md b/dotnet/samples/GettingStarted/FoundryAgents/README.md index 19bafb5d1b..ba5af8de5a 100644 --- a/dotnet/samples/GettingStarted/FoundryAgents/README.md +++ b/dotnet/samples/GettingStarted/FoundryAgents/README.md @@ -24,7 +24,7 @@ One of the key architectural changes in the new Foundry Agents compared to the c This design ensures consistency and predictability in agent behavior across all interactions with a specific agent version. -The Agent Framework intentionally ignores unsupported runtime parameters rather than throwing exceptions. This abstraction-first approach ensures that code written against the unified agent abstraction remains portable across providers (OpenAI, Azure OpenAI, Foundry Agents) without requiring provider-specific conditional logic. Teams can adopt Foundry Agents without rewriting existing orchestration code—configurations that work with other providers will gracefully degrade rather than fail when the underlying API does not support them. +The Agent Framework intentionally ignores unsupported runtime parameters rather than throwing exceptions. This abstraction-first approach ensures that code written against the unified agent abstraction remains portable across providers (OpenAI, Azure OpenAI, Foundry Agents). It removes the need for provider-specific conditional logic. Teams can adopt Foundry Agents without rewriting existing orchestration code. Configurations that work with other providers will gracefully degrade, rather than fail, when the underlying API does not support them. ## Getting started with Foundry Agents prerequisites