This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 46%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESD%3C/text%3E%3C/svg%3E)
I have successfully created an index on Azure AI search using blob storage, but since Friday I have been getting an error stating "the version indicated by the api-version query string parameter does not exist." I am using the import and vectorize data option for AI search.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(185.6, 59%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
@Sara D Thanks for reaching here! The error message you are seeing indicates that the API version you are using is not supported by Azure AI search.
To resolve this issue, you can try the following steps:
api-version=2020-06-30. See API versions for more versions.See- https://learn.microsoft.com/en-us/rest/api/searchservice/create-indexer
Let us know.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(134.4, 88%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENM%3C/text%3E%3C/svg%3E)
I am seeing the same behaviour in the Azure portal. In the portal I can't see any way to specify the version. Is this actually a problem in the portal?
I can also confirm that this happens when an indexer is created using the API (following the instructions you supplied in your reply). It appears that when the indexer runs, it uses an invalid API version (probably for embeddings). Is there a way to control this? I can't see anything in the docs.
I can also confirm that the same issue occurs if the index is created using api-version=2020-06-30.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 84%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJC%3C/text%3E%3C/svg%3E)
I am having the same issue. The Indexer was working fine on January 28th. Started getting the error when running the indexer on January 29th.
This started working again today. It looks like MS have fixed it!
Can confirm that it worked for me today also.
@Sara D
Apologies for inconvenience here! This was known issue, expected to resolve in 24hrs-
Please let us know if it persists.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(44.800000000000004, 75%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJL%3C/text%3E%3C/svg%3E)
Guys, I just want to let you know that I've tested many Azure API versions and the only way to be able to create an index for Azure AI Search was the 2024-03-01-Preview, I'd appreciate someone validates it because the latest stable didnt work showing ...
{"error":{"code":"","message":"The request is invalid. Details: The property 'stored' does not exist on type 'Microsoft.Azure.Search.V2023_11_01.SchemaField'. Make sure to only use property names that are defined by the type."}}
I'm afraid of someone removes this preview version in a near future because I have a pipeline that creates and delete a lot of indexes and I depends on the API.
Thank you so much