How to let my AI Agent created from AI Foundry listed in Entra Agent ID (Enterprise Apps) automatically?

Question

I would like to test how the latest feature just be announced in #MSBuild last week, Entra Agent ID, would work, especially to see the newly created AI Agents enlisted as Agent ID in Microsoft Entra ID Enterprise Application.

I created new two AI Agents in Azure AI Foundry as follows:

But until now (few days already) there is no Application Type == Agent ID listed:

I tried both newly created agent with no other setting, and another agent that I set some details like instruction and knowledge, but none of those happened to be enlisted in Microsoft Entra ID Enterprise App automatically, even I remove the Agent ID filter.

So, I would like to know if it has to do any extra things to let this new feature work?

Answer 1

Hi saranSaran (Sarah) Hansakul , thanks for bringing this up to here, really for me its kind of super interesting question, especially with the new entra agent id feature ))

ok, so what I'm think, the auto-listing thing can be a bit tricky right now since the feature’s still fresh out of msbuild :) i checked the docs, and it looks like there’s a tiny gap between creating an ai agent in azure ai foundry and seeing it pop up in entra’s enterprise apps as an "agent id" type. here’s how u can nudge it along

1. permissions & sync make sure the azure ai foundry service has the right permissions in entra id to register apps. sometimes the sync isn’t instant, but u can manually trigger it by editing the agent’s connected resources in ai foundry and hitting "refresh."
2. app registration check head over to entra id’s "app registrations" (not just enterprise apps) and see if the agent shows up there first. if it does, u might just need to wait a bit longer for the enterprise apps list to catch up. or, u can manually add it as an enterprise app by selecting "new application" and searching for the agent’s name.
3. api permissions if the agent needs to access other services (like graph api), u gotta add those permissions in the app registration. this might kickstart the visibility in enterprise apps manage api permissions.
4. private preview quirks since this feature’s still rolling out, there might be some delays or extra steps. u could try recreating one of the agents or check the ai foundry’s activity logs to see if the registration attempt even went through.

let me know how it goes, and yes , microsoft’s docs are a lifesaver here, even if the features so new it’s practically still warm from the oven :) really, i just know what I'm talking about.

Best regards,

Alex

and "yes" if you would follow me at Q&A - personaly thx.
P.S. If my answer help to you, please Accept my answer
PPS That is my Answer and not a Comment

https://ctrlaltdel.blog/