Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

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. Support add-ins for custom file types (e.g. DICOM)

    Would like to have DICOM files indexed for search in the Azure Portal. Support for adding custom logic for parsing arbitrary file types would be sufficient.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →

    This functionality is now available to all customers as a part of Cognitive Search feature of Azure Search, using “custom skills”. See:
    - Introduction to Cognitive Search: https://docs.microsoft.com/azure/search/cognitive-search-concept-intro
    - Integrate custom skills: https://docs.microsoft.com/en-us/azure/search/cognitive-search-custom-skill-interface

    Please try it out and give us your feedback.
    Thanks!
    Your Azure Search team

  2. Create a Sitecore Azure Search Provider

    Sitecore comes with/supports Lucene and SOLR sitecore search providers.
    Coveo have built/supports their own Sitecore search provider.
    Could Microsoft build/support a Sitecore Azure Search provider?

    Currently are a few open source implementations, e.g. https://github.com/jscott1277/SitecoreAzureSearchProvider

    In a recent press release
    http://www.sitecore.net/about/press-and-media/press-releases/2016/07/sitecore-partners-microsoft-transform-digital-experience-at-speed-microsoft-azure.aspx
    "the two companies plan to expand their long-standing strategic alliance to enrich Sitecore’s Microsoft Azure cloud offerings over the next two years"
    Might this be included as part of that?

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  3. Blob Indexer should continue indexing documents after encountering an error

    This is related to...

    https://feedback.azure.com/forums/263029-azure-search/suggestions/11628435-blob-indexer-should-be-able-to-skip-unsupported-co

    ...whilst a change has been added to easily configure the indexer to exclude unsupported document formats, this is inadequate. Bugs in the indexer and corrupt documents are going to ensure that there will always be a percentage of documents that can't be processed by the indexer. This shouldn't stop the indexer from processing data it can index.

    When the indexer encounters an error processing a document it should log the error then proceed with indexing of the rest of the documents in storage.

    A run shouldn't be halted until the indexer has attempted to index…

    34 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  4. Open source the Azure Search .NET SDK

    It would be helpful if Azure Search team opened source the .NET SDK like Azure Storage team did on GitHub: https://github.com/Azure/azure-storage-net

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Client SDK  ·  Flag idea as inappropriate…  ·  Admin →
  5. Why can't I add new indexers or data sources using the portal

    The portal will let me see a list of indexers or data sources but it won't let me add new ones. Every time a feature is added to the REST interface it needs to be supported in the portal UI the same day. Stop making me build an app just to send REST requests to get things done. The UI should have 100% feature parity with the REST OM.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Portal  ·  Flag idea as inappropriate…  ·  Admin →
  6. Make it so SearchMode=All matches if stop words are present even when querying across multiple analyzers

    Not all of the documents in our corpus are localized so we must search the default language (English) and the user's locale with the provided user query. Queries that contain a stop word for either default or user language analyzer causes no results to be returned.

    Example:
    The documents contain 2 searchable fields (plus an ID field).
    TitleEN -> English Analyzer
    Title
    ES -> Spanish Analyzer

    A document exists with the following values:
    TitleEN -> "The best document"
    Title
    ES -> "Un documento excelente"

    When a user inputs a query, we search on TitleEN and TitleES.…

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  7. 2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  8. Expose search quality metrics like CTR (click-through rate) in the Search Traffic Analytics dashboard

    That would require collecting information about user clicks. The dashboard could also show the number of unique users over time and MRR (mean reciprocal rank).

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  9. Get documents from an array of IDs

    an equivalent feature to that of the Ids Query in Elasticsearch (https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-ids-query.html) to retrieve all documents whose Ids appear in a provided array of Ids.

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Ability to index more than 1M documents in Basic

    I have a basic account for $40\month, and have 1.1M documents. But I'm not able to add an additional partition. My only options are a) limit my documents to 1M (what's the point?) or b) upgrade to Standard which supports 15M documents (overkill) for $250/month?!? Of course, I could sign up two basic accounts for less, but then have to write specific code to query two search accounts. Please add the ability to add more partitions to the Basic Tier.

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →
  11. Support indexing of append blobs

    It seems Azure Search doesn't currently work with append blobs. We use append blobs for logging and Azure search would help a lot if it could handle the blobs.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  12. Move service between subscriptions

    In response to the Azure Portal team's comment in this (https://feedback.azure.com/forums/223579-azure-portal/suggestions/5608987-move-services-between-subscriptions) thread, I'd like to propose to enable/implement this feature for the Search service asap.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →
  13. Extend the Azure Search indexer for Azure tables to allow a search index to be sourced from multiple tables

    Would it be possible to extend the Azure Search indexer for Azure tables to allow a search index to be sourced from multiple tables? I have a search that, currently, I build from a ProductAnnotation and a ProductWholesale table (both share a common Id for lookup and this Id is stored in the search index).

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →

    Hi Keith,

    This is already possible in a slightly different form: you can create multiple datasource / indexer pairs all writing into the same index. As long as you stagger their schedules so that the indexers are unlikely to overlap on the same document at the same time, you’ll get the functionality this suggestion asks for.

    Hope this helps!
    Your Azure Search team

  14. Most common searches by Analytics

    PowerBI can parse the Analytics data to obtain the "Most common search queries".
    It'd be awesome if the REST API could provide this information too.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
  15. 25 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  16. Add OData syntax support for startswith, contains, and endswith queries

    This is essentially a duplicate of another suggestion: https://feedback.azure.com/forums/263029-azure-search/suggestions/6470849

    The original suggestion mentioned odata support, and while it was marked as complete, it was only added to lucene searches.

    I'm sure many of the 178 votes where for specifically odata support.

    58 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  17. 80 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  18. 2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  19. Provide .NET API for key operations

    Currently, there's no .NET API to perform key management operations (generate new admin keys, list keys, etc.)

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add facial recognition to blob storage file indexer capabilities

    Based on the facial recognition technology used in Windows Photo Gallery provide indexers with the ability to perform some form of facial recognition.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →

    We recently released this in “public preview” as part of “Cognitive Search”. Essentially you can select an analyze image skill to identify well known faces (such as celebrities).

    You can see a demo of this at https://www.youtube.com/watch?v=Wh5Dt8wnEhg

    Also, if you want to create your own custom face recognition model, you could train a model using the Cognitive Service Face API, and then call that from a “custom skill” — see an example of how to create a custom skill here:

    https://docs.microsoft.com/en-us/azure/search/cognitive-search-create-custom-skill-example

    Thanks!

    Luis Cabrera
    Azure Search Product Team

  • Don't see your idea?

Feedback and Knowledge Base