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
Best way to diagnose data quantity mismatch
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
19
Votes
Serverfault
Community responses to Sys/Net admin questions
Azure Feedback
Do you have an idea or suggestion based on your experience with Azure?
Suggest API is not returning matching results count
I am using suggestion API in my application .If there are matching results more than 100 there is no option to identify the match results count.
How to Search with Full-text and partial text
I want to search by sending partial or full -text along with other parameters. and also is there any option for Phrase search with full text or partial text.
I wrote a technical review of the Knowledge Store preview feature and wanted to share it with you. See attached.
Allow Index Management by Azure CLI
Implement create/delete/update indexes via the Azure CLI in addition to Azure REST Api capabilities. You can create the search service itself of course, but i see no way to create the index or indexers (e.g.) using Cli
1402
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/
1220
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.
758
Votes
Support case-insensitive comparison in filters
Searching with text=
Storage Optimized tier in the Basic tier pricing range (L0)
For a small business with low traffic and data just over the 2GB limit of the Basic tier it´s really hard to justify to upgrade to standard tier for 3.3x more cost. The performance and scaling for Basic tier is more the enough but the 2GB limit is just to low. It would be nice if you could introduce storage optimized layer(L0) for the lower end of the price range where performance and scaling is not important but the storage amount is more than 2GB.
Support correlated search on complex collections
Now that Azure Search supports complex types, it would be useful to be able to combine full-text search and strict Boolean filters when querying over complex collections. Currently this is not possible -- search.ismatch()/ismatchscoring() are not allowed in lambda expressions, and using sub-fields of complex collections in full Lucene queries has uncorrelated semantics. For example, if you want to search for hotels that have deluxe rooms with city views, none of these gives you exactly what you want: search=Rooms/Description:(city views) AND Rooms/Type:(Deluxe Room) search=Rooms/Description:(city views)&$filter=Rooms/any(room: room/Type eq 'Deluxe Room') $filter=search.ismatchscoring('city views') and Rooms/any(room: room/Type eq 'Deluxe Room') Instead, what you'd ideally want is something like this (exact syntax TBD): $filter=Rooms/any(room: search.ismatch('city views', room/Description) and room/Type eq 'Deluxe Room')
Suggest API is not returning matching results count
I am using suggestion API in my application .If there are matching results more than 100 there is no option to identify the match results count.
Search Explorer in the Portal should interoperate better with SDKs
Currently, Search Explorer provides the full URL of the GET request for the Search REST API. To use a query from Search Explorer in the SDK, you have to parse out the parameters by hand, and sometimes URL decode them. It would be better if Search Explorer could provide code snippets for each supported language (C# and F# for now, Java, JavaScript/TypeScript, and Python when those SDKs are available) that show how to call the Search API using the parameters that the Portal user has typed in.
File a support ticket
Create an incidentTweet at us @AzureSupport
Connect on TwitterHelp us improve. Is this page helpful?