Azure Community Support
Ask questions, get answers and connect with Microsoft engineers and Azure community experts
MSDN Forum
Microsoft response to Azure technical questions
Azure Search scoring with document in different shards
Forum: Azure Search
Azure Search Service for multiple data source
Forum: Azure Search
Azure search indexing null value after adding a column with data in cosmos db
Forum: Azure Search
Search highlighting works differently on fields with special characters
Forum: Azure Search
9
Votes
Forum: Azure Search
6
Votes
Unable to Install SDK 2.9 from Web Platform Installer and VS2015
Forum: Azure Search
6
Votes
Handling scoring and priority with search across multiple indexes
Forum: Azure Search
4
Votes
Forum: Azure Search
15
Replies
Forum: Azure Search
13
Replies
Forum: Azure Search
13
Replies
Forum: Azure Search
12
Replies
Highlights == null in search results??
Forum: Azure Search
StackOverflow
Community responses to development questions
23
Votes
Serverfault
Community responses to Sys/Net admin questions
Azure Feedback
Do you have an idea or suggestion based on your experience with Azure?
Dear Team, Please introduce a 'minimum should match' parameter in Azure Search REST API (Lucene docs: https://lucene.apache.org/solr/8_5_1/solr-core/org/apache/solr/util/doc-files/min-should-match.html and Elasticsearch docs: https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-minimum-should-match.html#query-dsl-minimum-should-match )
Adding comments to the existing fields
Currently there is no option to add comments to the existing fields in Azure search, can we make this feature available?
Support contains/startswith/endswith in collection matching lambda expressions
It would be great if you support more operators in collection matching lambda expressions. For example, Members/any(m: m contains 'a'). Since there's no correlation between the query and the filters, this can be very useful.
Support bigger scope of returned highlights from complex types
When a document has a field which is a collection of a complex type, like: Students-> Collection of complex(age, gender, name) When we find a match in a name of a given student, the hit highlight returns the name. It would be great to get the entire Student complex type record in the highlight, so we'll have the context of the highlight and not just the name.
1528
Votes
Allow to upgrade the pricing tier
Everywhere in the portal, we can increase/decrease the pricing tier based on our needs. With the introduction of Azure Search Basic, we need a way to upgrade to the next level (Standard) when we are close to reach the service limits. The only way today to go around this is to bring the index down and create another one.
1344
Votes
Modelling Complex Types in Indexes
When modelling an index the data types are restrictive. There are simple types and collections. There is nothing that allows us to model complex types e.g. ... "name": { "first": "Ericka", "last": "Banks" },...... The oData spec allows for complex types http://www.odata.org/documentation/odata-version-2-0/overview/
1308
Votes
Provide a local emulator or increase the number of indexes on the free tier for development use
It sucks that if I have more than 3 indexes I have to create a paid tier for development. We do not need performance or size. Just more index to simulate the production environment which contains more indexes.
821
Votes
Support case-insensitive comparison in filters
Searching with text=<xyz> performs a case-insensitive search. However, testing string fields in filters is case-sensitive. There should be a way to do a case-insensitive string comparison in filter expressions.
Dear Team, Please introduce a 'minimum should match' parameter in Azure Search REST API (Lucene docs: https://lucene.apache.org/solr/8_5_1/solr-core/org/apache/solr/util/doc-files/min-should-match.html and Elasticsearch docs: https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-minimum-should-match.html#query-dsl-minimum-should-match )
Adding comments to the existing fields
Currently there is no option to add comments to the existing fields in Azure search, can we make this feature available?
Proper support for DateTimeOffset
Search should ingest and support a true implementation of DateTimeOffset. The current implementation merely converts an incoming DateTimeOffset to a DateTime in UTC, subsequently resulting in the loss of data, as the original offset can no longer be retrieved. The currently implementation necessitates persisting a related sidecar attribute of the original offset and subsequently requires the consumer to convert and rehydrate the property. This is exceptionally tedious, especially for use cases with several dozen DateTimeOffset attributes with varying offsets.
Offer reserved pricing on Azure Search (similar to AWS ElasticSearch)
AWS offers up to 52% discount when committing to a 3 year reserved instance for AWS ElasticSearch. There is no reserved pricing option for Azure Search. Please provide reserved pricing, similar to Cosmos DB/Azure SQL, at a discount comparable to AWS.