MicrosoftThank you for sharing. In all my tests only Microsoft Copilot agents (and older Power Virtual Agents) show up in the 'Agent ID' category. Newly created Azure AI Foundry agents do not show up. Is there any troubleshooting information out yet to figure out the cause for this? Thanks!
dmusil I had the same issue. I think the "see in action video" is outdated.
The Azure AI Foundry project creates a new Managed Identity, which is visible in Enterprise apps, not the agent in the project.
The documentation mentions something about it:
Agents are scoped at the project level, which ensures data isolation—agents within the same project share access to the same resources.
You can easily filter all the Agent ID service principals with Microsoft Graph. I wrote a post about it: Get insights into Microsoft Entra Agent ID apps with Microsoft Graph
TobiasAT that's some very helpful information right there, thank you. Your blog post is extremely valuable. I will go ahead and try this with PowerShell as you've described. Although I am now also thinking that the reason I am not seeing our Azure AI Foundry projects as managed identities in Entra ID, is that all projects have been created way before Microsoft introduced this change. So, I will also simply create a new project and check back under Enterprise Apps whether the project shows up, like yours do as shown in your blog. Thanks a lot!
Also, if you watch the action video carefully, you will see that the project is named "MyFoundryAgent". The demo was not adequately prepared. Microsoft named the agent with the same title as the project, but what the customer is seeing is the project name, not the modified agent.
Alex_Simons I think you should correct (or remove) the action video for the Foundry demo. It appears to be a misunderstanding.
