Azure Community Support
Ask questions, get answers and connect with Microsoft engineers and Azure community experts
Introducing Azure on Q&A
Find answers to your technical questions about Azure products and services. Connect with Microsoft and community experts, share feedback, and learn from others. Azure on Q&A, on the Microsoft Q&A site, is replacing the MSDN forum. But you can still browse the forum archives.
MSDN forum archive
Microsoft and community responses to older Azure technical questions
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
Best way to diagnose data quantity mismatch
Forum: Azure Search
StackOverflow
Community responses to development questions
25
Votes
Serverfault
Community responses to Sys/Net admin questions
Azure feedback
Post ideas or suggestions based on your experience with Azure
The pricing and option for app services, not corresponding wiht the real options
Update princing options.
Provide option to boost documents based on click feedback
If for a certain search term, an item is clicked more often than others, then that item should automatically rise in search results ranking, for that search term.This functionality exists in Lucidworks Fusion and is known as 'boost with signals' where signals are the clicks captured along with the search terms. Search terms matching for the boost should not be exact match only, i.e., all variants of the search string should be considered equal when applying the boost. e.g., if for 'buy laptop' search term, article A is clicked the most (the threshold for no. of clicks can vary, it should be configurable), then article A should be boosted for 'buy laptop', 'laptop buying', 'where to buy a laptop' etc. The boosting score for an article, should be a function of matching search terms and the no. of clicks that the article has received for those search terms.
Visibility/metric for the usage of MultiHoming for validating if it works as expected
We are looking to use the Multi-Homing feature for configuring the Azure search instance in the secondary region to retrieve data from the geo-replicated read-region instance of CosmosDB for making sure the dependencies are co-located in the same region. Though multi-homing feature is a great feature to resolve our multi-region requirements, there is no metric or visibility to validate if the setup is working as expected. We would like to have a metric to show which Cosmos DB instance the Azure search is indexing data from.
Merge Collection Feature in Azure Search.Allowing multiple documents with same key to be merge in the single collection when mapping data from two data sources
1652
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.
1385
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.
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/
892
Votes
Support case-insensitive comparison in filters
Searching with text= 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.
Return tag matched on along with asset
We would like to implement UI to be more transparent to users about the tag which the search term matched on. This is important to avoid PR risks with inferences on content and search term with fuzzy search.Currently, to enable this scenario, we would need to do a lot more processing that Azure Search is already doing. Additionally, ours solution would not be as intelligent and prone to error. Requesting the ability for Azure Search to also return the matched tag with the asset.
Increase this throttle limit: Create Index (POST /indexes): 12 per minute per search unit
All the other limits are per second - why such a low limit? We are indexing many documents at once and keep hitting it.
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?