Speller is not supported in my new Azure Cognitive Search instance

Question

I've got a very strange issue with Azure Cognitive Search. Soms months ago, I've created an Azure Cognitivie Search instance on our test subscription. When I query in the Search Explorer for *&speller=Lexicon&queryLanguage=NL-NL, I successfully receive a list of search results.

Today I created an instance of Azure Cognitive Search on our production environment with the same ARM Template and exactly the same Data Source, Indexer and Index. When I run the same query as above on this instance, it returns this error:

Parameter 'speller' is only supported for search services created on or after 2019-01-01.

It is a pretty clear error... except that I created the instance a few minutes before! I didn't even had access to the subscription in 2019. I've recreated the whole instance, but it keeps throwing me this error.

Does anyone have the same issue and probably a workaround?

Update: It looks like this problem only appears when I create a free plan instance in the production subscription. The free instance on the test subscription works fine and a Basic plan on production also works.

Answer 1

To benefit the community, sharing the offline discussions.

Issue: Created Azure Cognitive Search instance (few days ago), and when running the query '*&speller=Lexicon', it throws an error: 'Parameter 'speller' is only supported for search services created on or after 2019-01-01'.

The availability of speller is inconsistent on free tier services. If you need to guarantee speller for your workloads, then it is recommended that you leverage basic tier or above services.

The Azure doc is now updated, to reflect that the Speller is supported in Basic tier and above : Add spell check - Azure Cognitive Search | Microsoft Learn: A search service at Basic tier or above, in any region

In addition, our product team is also reviewing to update the error message to add more clarity.

And you may post your suggestions and questions over the Azure community channel Azure Search · Community

@Vincent , Thanks again for your feedback on this and much appreciate your co-operation!