Unable to connect Azure AI search to Knowledge of an Agent.

(3) Share

Report

Posted on by SN-10032033-0

Hi

When attempting to connect Azure AI Search to the Knowledge of an Agent in Azure CoPilot Studio, I encounter the following error message: "Something went wrong. Try reloading the page. If the problem persists, contact your admin. Reloading the page causes the browser to crash completely, requiring a full reload. Network logs indicate that the Invoke for this step receives a 404 error response.

The Azure AI Search connection is done using API key and that does seem to work correctly since I do see the green tick. The indexes have also been made on Azure AI search already.

Could someone please assist?

Attachments:

Screenshots of the error message
Network logs showing the 404 error response

Categories:

General topics

I have the same question (1)

All responses (6)

Answers (0)

Sort by

FM-25031336-0 2 on at

Like (0)

Report
Copy link

Link copied!

I'm experiencing the exact same problem (except that the 404 on the invoke is https://europe. ...). Did you find a solution yet, for this problem?

Are you also in a trial license?

I'll keep you posted If I would find any solution.

Was this reply helpful? Yes No
CU28031240-0 2 on at

Like (0)

Report
Copy link

Link copied!

I have same also same problem

Was this reply helpful? Yes No
Suggested answer

MJ-02041225-0 2 on at

Like (0)

Report
Copy link

Link copied!

Hi,

I had the same problem with an index create with a free plan. When creating an identical index with the standard plan, I could successfully connect it as a knowledge to copilot...

Did you use also a free plan?

BR, Marcel

Was this reply helpful? Yes No
Mike Allen 9 on at

Like (1)

Report
Copy link

Link copied!

I'm having this problem as well. Has anyone fixed it. Sould I raise a support call on this?

Was this reply helpful? Yes No
JT-08041633-0 6 on at

Like (0)

Report
Copy link

Link copied!

I looked into what what @MJ-02041225-0 suggested as we are getting the same error, but we are already using the standard plan. If anyone finds a solution and shares it here, I would appreciate it so much! In the meantime, I'll keep digging.

Was this reply helpful? Yes No
Arian K 21 on at

Like (0)

Report
Copy link

Link copied!

I'm getting this error as well and it's incredibly frustrating. The error doesn't provide anything useful so I have no idea what's wrong with my Azure Search Index. I'm using integrated vectorization, and it's not hidden behind a private network. Can you PLEASE display something useful if it's somehow not compatible? It really needs to provide more useful guidance here. As it is, I'm assuming it's just broken since my index isn't weird in any way. Or, help me to get it working if it's legitimately pointing out an error. Thanks.

Was this reply helpful? Yes No