15b - Creates successfully, but Agents page does not load.

[DamienMorganSmithBCM]

Upon a successful deployment of the 15b sample through Terraform, we are unable to access the Agents page, or connect to resources via Foundry IQ.

Private Endpoints are working (can perform API requests to model endpoints, access storage over private endpoints etc, chat with chat playground for deployed models). Private DNS is operational, and working over Express Routes.

For the Agents page:

• Remains stuck on "Loading Agents"
• Request in developer menu that fails: "https://deployment_name.services.ai.azure.com/api/projects/project_name/agents?api-version=v1&limit=50"

When attempting to add Knowledge Sources (like Blob):

"Failed to create knowledge source. Failed to create or update Knowledge Source"

[JanKnipp]

Facing the same issue and I've already put probably 100 hours to get to this point and these resources feel so messy.
Why must it be so complicated to setup a resource of this type?
The 15* bicep samples also do things differently with the capability host as they create a foundry capability host with a subnet reference and I'm always wondering which is the right way as nothing works properly and every sample does it differently.

[DamienMorganSmithBCM]

Agreed - I've actually had a Microsoft case raised for over 3 weeks on this, and have made absolutely zero progress. Very infuriating. Getting no updates from the Product Group.

[JanKnipp]

And i forgot to mention that this works a bit when switching to the "old" Foundry experience. if I then create a new agent i can at least verify in playground that the basic wiring seems to be ok (things are stored in cosmosdb, storageaccount). Sadly this does not really help with my initial use case of creating an agentic RAG solution. Seach Service when using it only inside the Knowledge Base also seems to work fine but now wiring everything together is just miserable. Search Service also had some weired issues where the service inserted incorrect urls and stuff.
We also had opened a case about a month ago but that manly resolved in ==> try the samples or make everything public

[JanKnipp]

ok, now it is getting even more strange. i went back to the "old" portal and created a new agent. After some testing i went back to the "new" Portal and it asked me to import the new agent. I did so and now agents load. I'm pretty sure i already had a "new" agent in there which seems gone but now i can see the new one and work with it (for now).

[T128CL216]

Hey @JanKnipp
Did you manage to find a solution?

I'm hitting the same wall — spent hours on this. At first I thought my capability host was wrong, but I think it's somehow the Foundry itself that doesn't bootstrap the Foundry (nextgen) features during deployment.

Everything seems to be working fine in classic Foundry, but as soon as I try to list agents in the new Foundry, I get the same 503 as you.

I read somewhere that the agent service is a nextgen Foundry feature, and the fact that the assistant service works fine really makes me think the issue lies with the cognitive service account deployment — which somehow gets deployed the old way, making it incompatible with nextgen.