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. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Hi Kent,

    If you’re referring to indexer warnings / error messages, please let us know the context and we’ll fix them to refer to in-encoded blob paths.

    If you’re referring to indexing the in-encoded metadata_storage_path property in your search index, you can create a field mapping, for example:
    “fieldMappings” : [ { “sourceFieldName” : “metadata_storage_path”, “targetFieldName” : “path” } ]

    For details about field mappings, see https://docs.microsoft.com/azure/search/search-indexer-field-mappings

    Also, you can open GitHub issues for the documentation on the doc pages directly by clicking [Give Documentation Feedback] button. This lets you use your UserVoice votes for making / voting on feature requests, and lets us understand more contextually which docs need improvement.

    Thanks!
    Eugene Shvets

  2. Ability to schedule reset of index

    In order to clean up an index, it would be useful to schedule periodic full index reset.

    3 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 →
  3. Indexing shouldn't fail for all documents when one exceed size limit

    Scenario:
    1. We have a production application using Azure Search with Basic Pricing Tier
    2. The indexer is already configured with these parameters:
    "parameters": {
    "maxFailedItems": 10,
    "maxFailedItemsPerBatch": 5,
    "configuration" : { "failOnUnsupportedContentType": false }
    },
    3. indexing runs once every 60 minutes

    Since we are using the Basic pricing tier, file size limit is 16MB and this is acceptable for the business.

    When a system administrator uploads several documents, and one of them exceeds the 16MB limit, indexing breaks and stops for all documents, even the good ones.

    Logs show this kind of error messages:
    [
    {
    "key": null, …

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    The desired functionality is already available using ‘indexStorageMetadataOnlyForOversizedDocuments’ configuration property.

    PUT https://[service name].search.windows.net/indexers/[indexer name]?api-version=2016-09-01
    Content-Type: application/json
    api-key: [admin key]

    {
    … other parts of indexer definition
    “parameters” : { “configuration” : { “indexStorageMetadataOnlyForOversizedDocuments” : true } }
    }

    Thank you for using Azure Search!

  4. Support more delimiters when indexing CSV blobs

    When indexing CSV blobs with Azure Search blob indexer, please add support for delimiters other than ",". We have many blobs that use | and \t as delimiters.

    1 vote
    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 →
  5. Indexers convert uniqueidentifier to lower case

    Indexers convert uniqueidentifier to lower case which should not happen.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  6. import data form

    Resolve Import Data Grid Bugginess

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Portal  ·  Flag idea as inappropriate…  ·  Admin →
  7. Document Level Security Trimming

    An Index contains data from a source (Blob Store, SQL DB, DocumentDB, say DropBox one day?). Different sources may have different and detailed security on each document.

    We index these sources normally as a 'super-user' of some kind so the index may contain information from any indexed doc (like 'the bosses salary').

    At index query time of course the original document source is not available. It should be possible though to allow one or more 'roles' to be added to each document as it is indexed and to specify roles in the Search query.

    In this way a middleware search…

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  8. base64decode method should handle standard strings

    Azure Search indexer base64decode method should handle standard URL Safe Base64 encoded strings, and not the out-of-standard strings returned by classic System.Web.HttpServerUtility.UrlTokenEncode method, which is not even available in latest versions of the framework. This method is returning non-standard strings, as it replaces padding characters '=' with a digit indicating the number of = signs that were removed. Azure Search base64 decode method expects this non-standard strings, rather than standard URL safe Base64 encoded strings, otherwise it breaks with error: "Error applying mapping function 'base64Decode' to field 'aaa': Array cannot be null.\r\nParameter name: bytes". Which means that using JavaScript or…

    6 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 →
  9. Allow custom defined Field Mapping Function

    Currently when defining the indexers, one can specify the field mappings from source to target fields. Only a limited set of functions such as Extract token at position etc are supported. It would be desirable to support Func syntax such that each row is passed onto the func which then decide the target field value based on developer defined logic in func.

    Eg: we have a cosmo db source and a azure table storage data source. The partition key for cosmo db collection is combination of tenantId:studentId for efficient read/writes across partitions based on our data. The azure table storage…

    15 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 →

    We recently introduced a capability of Azure Search that we call Cognitive Search.

    Cognitive Search allows you to apply enrichment and transformation steps to your data that we call Cognitive Skills. You can select from predefined skills or apply your own custom skill.

    The best way to transform your input data when you want to define your own function would be through a custom skill that you run as part of your enrichment pipeline.

    You can read how to do this at https://docs.microsoft.com/en-us/azure/search/cognitive-search-custom-skill-interface

    Thanks!
    -Luis Cabrera

  10. Cover Azure Search in the HIPAA BAA

    Please add Azure Search to the HIPAA BAA so we can use it in healthcare software.

    56 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  11. Import Data Exceeded the free quota of 3 indexers BUG

    I am now stuck at recreating indexes. I was told to delete one of my index to create another, but it didn't work. The funny thing is that, I am only having just 1 active index in that Azure Search Repo.

    Response that i get when I want to 'Import Data':
    'You have exceeded the free quota of 3 indexers. Please delete one to continue'

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    Hi, the error message refers to indexers, not indexes. An indexer is a resource separate from an index. So in your case, you need to delete some indexeRs.

    Also, please use MSDN forums or StackOverflow (azure-search tag) to ask questions like this – you’ll get a much faster response on those forums.

    Thanks!
    Eugene Shvets
    Azure Search team

  12. DocumentDB indexer should be able to index MongoDb collections

    If I create a MongoDB collection backed by DocumentDB, I should be able to use the DocumentDB indexer to ingest it into Azure Search.

    69 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  13. configurable (or unlimited) hit highlights

    Per https://docs.microsoft.com/en-us/rest/api/searchservice/search-documents "Azure Search returns only up to 5 highlights per field. This limit is not configurable" >> this should be changed. Either by offering a configurable threshold, by pagination or any other way. We'd need to be able to access all hit results and not just a partial subset

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  14. Return all the highlights and not just 5

    Today Azure Search returns only the first 5 highlight for each field. It would be great to get all the highlights.

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

    Financial institutions are supposed to audit all of their transactions and detect the illegal entities out of free format financial texts by means of a LOB search engine. The list of entities are published by the governmental units such as US OFAC SDN list.

    https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx

    The regular search engines including Azure Search fails to address this need. The blog post below illustrate what is actually expected.

    "Is Google Really Unrivaled When It Comes to Search?"
    https://goo.gl/6Dg1mv

    Below is a demo application to test and highlight the features of such search engine addressing this need. Below is a sample query to…

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

    Thanks for the feedback. Azure Search now support the ability to extract entities as part of its new “Cognitive Search” capability. If our built in custom entity skills don’t meet your particular needs, you could also create a custom skill with your own entity extraction code.

    Learn more about Cognitive Search in this Ignite Session:
    https://myignite.techcommunity.microsoft.com/sessions/66240

    Here is a complete list of Cognitive Search Resources:
    https://docs.microsoft.com/en-us/azure/search/cognitive-search-resources-documentation

    Thanks!
    Luis Cabrera
    Azure Search Product Team

  16. Analyzer with Automatic language detection

    Our use case is that users upload files which can be in any languages, hence we have to do language identification on the content. Each file only exists in one language, meaning we don't have multiple translations of the same file.

    For now that means we have to create one field per potential language in the index and assign them corresponding language analyzers. Then when we index the file we upload it's content to the field matching the language. Then when we add more field with the same language requirements we end up with spending a huge number of fields…

    62 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 →
  17. Smallint and Tinyint not recognized as integral types for SQL Server deletion detection

    I've been trying to create an auto indexer over a view. The column I want to use for deletion detection is type Tinyint, but the indexer throws an error saying this isn't an integral type.

    I've also tried with smallint, but it only seems to accept int and bigint.

    1 vote
    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 →
  18. Azure Search reset button in indexer blade

    It would be good to add a button to do reset indexer operation in indexer blade.
    https://msdn.microsoft.com/en-us/library/azure/dn946897.aspx

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Portal  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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
    Sign in
    (thinking…)
    Sign in with: Microsoft
    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

  20. 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
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 6
  • Don't see your idea?

Feedback and Knowledge Base