Forum Discussion

NewStarterKickoff's avatar
NewStarterKickoff
Copper Contributor
Feb 12, 2026

New Foundry Agent Issue

Hi all,

 

I’m creating my first agent via New Foundry, so my questions are probably basic. As always, everything seemed straightforward… until deployment.

I created an agent using gpt-4.1, added a list of instructions, and then used the Tools → Upload files functionality to attach a selection of reference documents.

Everything worked perfectly in Preview mode.

I then used the default option to Create a bot service, and it deployed successfully.

To test it, I used the Individual Scope option (with the intention to share later with a couple of people — I haven’t worked that part out yet).

Like magic, it appeared in my Teams and M365 Copilot, which was amazing… and then I ran my first search.

It thought for a long time and then returned an error. 

In Co-pilot: 

and Teams: Nothing happens at all

 

 

I’ve looked around for help but drawn a blank. I’m fairly sure it’s some kind of permissioning / access issue somewhere, but I can’t find where.

 

Any help would be hugely appreciated.

1 Reply

  • Because Preview works, the model and instructions are probably fine. The published bot uses the agent’s stable endpoint and a different authorization path, so I would check versioning and identity first.

     

    1. Confirm the active/published version is the same version that has File Search enabled and the vector store/files attached. A working draft in Preview does not prove the endpoint is serving that version.

    2. Test a question that does not require the uploaded documents. If that works, inspect the published agent identity and grant it the required data-plane roles on every backing resource the tool uses, such as Search or Storage.

    3. “Individual/Just you” publishing uses RBAC. Confirm your user has an appropriate Foundry role on the project, then sign out and back in after role changes.

    4. Start a fresh Copilot chat. In Teams, send /foundry_new_preview to reset a conversation stuck after a tool error.

     

    Finally, check the agent trace/diagnostics for the failed timestamp; the generic Copilot message hides the real authorization or tool exception.