Issue with using AIAgent class and agents in the new Microsoft Foundry

[michelschep]

When using an agent in the "old" Foundry I can use the following instructions to chat:

PersistentAgentsClient persistentClient = new("https://xyz.services.ai.azure.com/api/projects/my-project",
        new AzureCliCredential());
IChatClient chatClient = persistentClient.AsIChatClient("asst_my-agent-id");
    
AIAgent agent = new ChatClientAgent(
        chatClient,
        instructions: "You are a helpful AI assistant.",
        name: "MyLeetAgent");

var result = await agent.RunAsync("Can you please help me?");
Console.WriteLine(result.Text); 

However when I try to do the same with agents created in the new Foundry MAF is complaining about the ID.
It expects ids to start with "asst_"

To be able to use MAF agents I cannot migrate my agents to the new Foundry.
Somebody knows when it is possible to create an AIAgent with a new Foundry agent instance?

[markwallace-microsoft]

Here is an example showing how to create a Foundry V2 Agent: https://github.com/microsoft/agent-framework/tree/main/dotnet/samples/GettingStarted/AgentProviders/Agent_With_AzureAIProject

[michelschep]

That already works better! Thx @markwallace-microsoft !

 const string projectEndpoint = "https://xyz.services.ai.azure.com/api/projects/xyz-ai-foundry-project";
 AIProjectClient projectClient = new(endpoint: new Uri(projectEndpoint), tokenProvider: new AzureCliCredential());
    
 AIAgent agent = projectClient.GetAIAgent(name:"TheNewFoundryAgent");
 AgentThread thread = agent.GetNewThread();

 var result = await agent.RunAsync("Are you a real NFA (New Foundry Agent)?", thread);
 Console.WriteLine(result);

Now the agent (AIAgent) works and answers! (I also needed to add the System.Memory.Data nuget package).

The only thing that does not work yet is the conversation data in Azure.
The IDE shows as ConversationId "resp_09b2..."
The New foundry in Azure shows this id as the responseId. The conversationId in Azure is empty.
With another trace in Azure I see that the conversationId starts with "conv_"

The traces section in Azure: