You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
.NET: Would it be possible to support using the Foundry agent name as the executor ID in .NET workflow events #1743
When an Azure AI Foundry agent is used as an executor without being declared, the workflow event shows the agent ID (like asst_xxx) as executor ID, whereas Python uses the agent name instead.
Since the agent ID isn’t readable and can’t be set manually, when there are many agents in a workflow, it becomes hard for users to tell them apart in the events. Would it be possible to support using the Foundry agent name as the executor ID in .NET events?
changed the title [-].NET: Would it be possible to support using the Foundry agent name as the executor ID in .NET workflow events[/-][+]Python: .NET: Would it be possible to support using the Foundry agent name as the executor ID in .NET workflow events[/+]on Oct 28, 2025
changed the title [-]Python: .NET: Would it be possible to support using the Foundry agent name as the executor ID in .NET workflow events[/-][+].NET: Would it be possible to support using the Foundry agent name as the executor ID in .NET workflow events[/+]on Oct 28, 2025
Activity
[-].NET: Would it be possible to support using the Foundry agent name as the executor ID in .NET workflow events[/-][+]Python: .NET: Would it be possible to support using the Foundry agent name as the executor ID in .NET workflow events[/+]lokitoth commentedon Oct 28, 2025
The Python way seems like what we should be doing by default.
Since
Namecan be null in .NET, I am going to still have it fall back toId.[-]Python: .NET: Would it be possible to support using the Foundry agent name as the executor ID in .NET workflow events[/-][+].NET: Would it be possible to support using the Foundry agent name as the executor ID in .NET workflow events[/+]stephentoub commentedon Oct 28, 2025
For reference, DisplayName does that
TaoChenOSU commentedon Dec 5, 2025
Closed by #1840