MS Azure - Unable to create an index in AI Search service

Question

I am in the Azure Open AI Studio > Chat Playground. My objective is to Add my own data source for analysis using the chat bot. I have created a specific Blob Storage and container in the same subscription and placed my excel file in there which has the data to analyse. When I go to chat playground and select the option 'Add a data source' then I select 'Azure Blob Storage'. I fill in the required information which is all accepted but however 'Enter the index name' field is greyed out and when I input rest of the information, it starts to load and gives an error: "Failed to retrieve information about the selected search resource. Please try again later or choose a different resource."

I understand that I need to create an index, so I go to my Open AI Search service but no matter from where ever I try to create an index or even add a data source I get the following error:

I get the same error when I try to create index from AI Search 'Overview' screen or if I click on 'Indexers' or even if I click on 'Data sources'. I have checked network and firewall settings and it all looks ok to me although I am no expert in that area hence any help would be much appreciated. Thanks, Raja

Answer 1

@Raja Usman Abdullah Thanks for reaching here!

If I have understood right you are facing below error when trying the Chat Playground in AI studio, and trying to add your own data.

Failed to retrieve information about the selected search resource. Please try again later or choose a different resource.

Could you please go to cognitive search service and when trying create an index, If it shows the following error?

Error message:The client XXX with object id XXX does not have authorization to perform action 'Microsoft.Search/searchServices/listAdminKeys/action' over scope '/subscriptions/XXX/resourceGroups/XXX/providers/Microsoft.Search/searchServices/XXX' or the scope is invalid. If access was recently granted, please refresh your credentials.

If so, this could be due to permissions issue of the Azure AD application or service principal that you are using to access the Azure Cognitive Search resource.

You can follow these steps to verify if you have the required permissions:

• Go to the Azure portal and navigate to the Azure Cognitive Search resource that you are trying to access.
• Click on the "Access control (IAM)" tab in the left-hand menu.
• Check if your Azure AD application or service principal is listed under the "Role assignments" tab. If not, you will need to add it as a Contributor or Owner to the resource.
• If your Azure AD application or service principal is listed, click on it to view the assigned role. Make sure that it has the "Contributor" or "Owner" role assigned to it. If you are still having issues after verifying the permissions, you can try refreshing your credentials by signing out and signing back into the Azure portal. You can also try regenerating the admin keys for the Azure Cognitive Search resource and updating the connection string in your application.

Please let us know if issue remains.

Answer 2

It looks like you have a private endpoint for your search service. If that's the case, you can edit the host file on your computer for the public DNS of your search service. Not the private link, though you'll want to be sure you can resolve that as well.

Hit f12 while the page is open and hit the refresh icon next to the AI search resource, you'll eventually see the timeouts and the correct fqdn to add, since public access is disabled.

 Update the following for your environment, then add it to c:\windows\system32\drivers\etc\hosts then give the page a refresh.

10.10.10.x    searchserviceexample.search.windows.net

Answer 3

It looks like you have a private endpoint for your search service. If that's the case, you can edit the host file on your computer for the public DNS of your search service. Not the private link, though you'll want to be sure you can resolve that as well.

Hit f12 while the page is open and hit the refresh icon next to the AI search resource, you'll eventually see the timeouts and the correct fqdn to add, since public access is disabled.

10.10.10.x searchserviceexample.search.windows.net