Azure Search

Azure Search is a search-as-a-service solution that allows developers to incorporate a sophisticated search experience into web and mobile applications without having to worry about the complexities of full-text search and without having to deploy, maintain or manage any infrastructure

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  2. 21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  3. asciifolding support

    I have some content that contains diacritics like Caffè, which azure search would not be able to pick up if user searches Caffe. Elastic search has asciifolding support.

    Is it possible to implement or configure somewhere? http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/asciifolding-token-filter.html

    17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  4. HTTP POST based search query

    I can see only HTTP GET is supported.
    Hope I don't get a 414 (Request-URI Too Long) status if a URI is longer than the server can handle

    79 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →

    Azure Search now supports invoking Search and Suggest REST APIs via HTTP POST (previously you could only invoke them using GET). This is useful in scenarios where you have large filters and/or many facets and may be constrained by the 8 KB limit on the length of request URIs.

    The new endpoints are now available in the 2015-02-28-Preview API version, documented here:

    https://azure.microsoft.com/documentation/articles/search-api-2015-02-28-preview/#SearchDocs

    https://azure.microsoft.com/documentation/articles/search-api-2015-02-28-preview/#Suggestions

  5. add extra transactions

    the 5,000 transactions are depleted in few hours, for a new website, that because of the crawling bots, i have 0 visitors on the website and all 5,000 transactions gone. The search api is useless!!!!

    123 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →
  6. Provide a startup-friendly billing model

    For startups it might be interesting to split billing in 2: queries and storage (similar to the Windows Azure Storage billing model).
    Our customer will have lots of records from day 1 (minimum 4 million), but the number of QPS will be very low the first weeks/months.

    So we might want to start with a shared instance in terms of QPS, but not for data / # documents.

    716 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    28 comments  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →
  7. Blob Indexing w File Crackers

    We would love to have blob containers indexed. One option may be to use iFilter support.

    205 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  11 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  8. Support for 2 Billion Documents

    We have 2B very small records with relatively low QPS rate. The overhead with the crawl database alone is a massive challenge.

    135 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  9. Azure Search and SQL Server integration

    Integrating SQL Server (Azure and on-prem) with Azure Search. A search in table/column that is Azure Search enabled would fall into a Azure Search query in the background, not visual for the developer.

    Only Azure Search enabled columns and tables would be handled by Azure Search and it would not be visible for the database consumer.

    Only a Azure Search Package that is installed on a on-prem machine that would enable the DBA to define which tables or columns that should be Azure Search enabled. Database triggers for SELECT, INSERT, UPDATE and DELETE would translate into Azure Search REST based…

    174 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  10. Sort results by rank

    We had also requested sort results by rank

    54 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  11. REST and/or PowerShell equivalent for options in the Azure portal

    For the same reason that it's good to have the script options in SSMS, it would be great to have a REST and/or PowerShell equivalent for options in the Azure portal. (It would be REALLY good to have that right across the portal but your team could take the lead on it :-))

    49 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Client SDK  ·  Flag idea as inappropriate…  ·  Admin →
  12. Auto-indexing of DocDB

    Lately, I've been working a lot with Cloudant, which is a distributed CouchDB platform with integrated Lucene search. I absolutely love the fact that you can define some sort of triggers that, when a document is inserted or updated, update the index to reflect that operation. Likewise, when a document is deleted, the corresponding indexes are deleted from Lucene.

    This is particularly convenient as you don't have to manually sync your DB and your search index, everything happens automatically under the cover. It would be great to have that on top of Azure Storage or the upcoming DocDB (even though…

    40 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  13. Include search functionality

    Incorporate Lucene/SOLR or microsoft search server into appfabric to allow searching across files (table/azure storage), databases, objects cached items, etc. Allow for cost effective cloud based storage + caching.

    71 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Proximity ranking

    when searching for two or more terms, give a higher rank value to terms near to each other

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Scoring  ·  Flag idea as inappropriate…  ·  Admin →
  15. Noise Word (stopwords) List

    Noise word list (or equivalent) creation

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  16. Localization

    Multilanguage support

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Internationalization  ·  Flag idea as inappropriate…  ·  Admin →
  17. Provide searching of phrases

    Without this capability, azure search may not be able to effectively search "dense" content (e.g., msw). Another example is an index I have with scientific journal docs. When I search for "back pain", the best I could do (please correct me if I'm wrong) is:

    text=back,pain&textmode=all

    Even though each query result contains "back" and "pain", most of them are irrelevant and have nothing to do with "back pain".

    Boosting the rank scoring of finding multiple adjacent terms could help but the query results would still mostly be irrelevant.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  18. Support for parsing html/xml string content

    Many documents to be indexed already contain HTML or XML content.

    An example for us would be something like the following

    Article
    - string: Title
    - string/html: Summary
    - string/html: Body
    - string: author
    - datetime: created/updated date

    etc.

    It would be very helpful if the indexer could ignore HTML/XML/CSS/JavaScript content in the string. The current suggested alternative is to provide a surrogate field with the html tags stripped out of it and use that for the index.

    The challenge is then with hit highlighting, where we'd like to display the matching content. We'd rather not have to then find…

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  19. Define target language for index

    in terms of internationalisation (internationalization), it would be great if there was a way to indicate a target language in the same way that a document type can currently be indicated when creating a full text index ie: be able to indicate that another column or attribute is holding details of the language. Auto-language detection is great but often isn't enough. What it is good for is multi-lingual documents.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Internationalization  ·  Flag idea as inappropriate…  ·  Admin →
  20. Customize highlights

    Right now it returns matched text between <em> tags. Instead would it be possible to return it as start and end postion value pairs in a given field. We can convert the current output in that format but wanted to know if there are customization options in the service itself.

    We are finding that consuming the current format is not very useful (<em> means italics, we want to show matched text in bold and in different color) and quite heavy to render (having html controls rather than native). We are currently looking to parse the string and finding start/end index…

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base