I was trying to create my chat set up with the "Add your data" feature in Azure OpenAI Studio. My data source is an Azure Blob Storage. I also have created an Azure AI Search instance and an embedding model deployed. I have checked the "Add vector search to this search resource" box and I get the following error when the data ingestion started:
Index creation failed. Details: Azure.RequestFailedException: The request is invalid. Details: definition : Error in Vectorizer 'default' : Invalid resourceUri. Provide a valid resourceUri for the Azure Open AI service. Status: 400 (Bad Request) Content: {"error":{"code":"","message":"The request is invalid. Details: definition : Error in Vectorizer 'default' : Invalid resourceUri. Provide a valid resourceUri for the Azure Open AI service."}} Headers: Cache-Control: no-cache,no-store Pragma: no-cache Server: Microsoft-IIS/10.0 client-request-id: xxxx x-ms-client-request-id: xxxx request-id: xxxx elapsed-time: 29 Strict-Transport-Security: REDACTED Date: Mon, 13 May 2024 23:19:00 GMT Content-Length: 191 Content-Type: application/json; charset=utf-8 Content-Language: REDACTED Expires: -1 at Azure.Search.Documents.IndexesRestClient.CreateAsync(SearchIndex index, CancellationToken cancellationToken) at Azure.Search.Documents.Indexes.SearchIndexClient.CreateIndexAsync(SearchIndex index, CancellationToken cancellationToken) at Microsoft.CloudAI.Containers.DataIngestion.Core.ACS.ACSClientManager.CreateIndex(String indexName, List`1 fields, SemanticSearch semanticSettings, VectorSearch vectorSearchSettings, RequestInfo requestInfo) in /__w/1/s/src/DSMService/svc/DataIngestion.Core/ACS/ACSClientManager.cs:line 48
I have done the exact same steps many times before and the data ingestions worked perfectly. I wonder what is the breaking change introduced that this is not working now?
I have also tried to use the "Import and vectorize data" feature from the Azure AI Search side and I am getting the same "Invalid resourceUri" error. This leaves me with no available options to create a vectorized search index from the Azure Portal. Can you help to fix the issue?