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. Increase Blob Indexer file size limits

    The "Blob indexer: maximum characters of content extracted from a blob" limit seems rather restrictive, 32K for free, 64K for standard and 4MB for everything else. Plus when this limit is reached all you see in the azure portal is

    [{ "key": null, "message": "Truncated extracted text to 32768 characters." }]

    It'd be useful to know which documents are affected.

    31 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  2. sintax highlight length

    Could we get a parameter to specify the length of a highlight fragment that is returned when the highlight parameter is used on a field? The string returned is too short for some of our users because they are searching very techincal data and need more context. It would be very useful to be able to return longer fragments depending on the field we're searching so we need control over this.

    30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add an API for Text extraction from a file (or string/stream with file content)

    Indexer https://azure.microsoft.com/en-us/documentation/articles/search-howto-indexing-azure-blob-storage/ does extraction of text from a file (document).
    Instead of using azure blob (extra implementation and usage charge) and delay with processing a document from there, client will have possibility to extract text from document and do mergeOrUpload content.

    We know when file content was changed (or a new file created) and would like to handle that our self.

    30 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 →
  4. MicrosoftLanguageStemmingTokenizer cannot process word 'F#' correctly

    'F#' is a well-known programming language, but if you tokenize sentence contains 'F#' with "en.microsoft" analyzer, it will be omitted. However, 'C#' works fine and does not have such issue.

    28 votes
    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 →
  5. Enable indexing of gzip compressed blobs

    https://stackoverflow.com/questions/46245505/indexing-gzipped-blobs-in-azure-search

    I am trying to setup Azure Search over Azure Blob. The json blobs are compressed using gzip.

    When I try to index the blobs as-is, I get the exception :

    "Error detecting index schema from data source: "Error processing blob https://mystorageaccount.blob.core.windows.net/mycontainer/urlencodedname with content type ''. Status:UnsupportedMediaType, error:""

    Looks like Azure Search blob indexer does support indexing ZIP archives (application/zip MIME type), but not gzip-compressed files.

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  6. Support IP firewall\service endpoints

    Our enterprise requires 2 factor auth for all remote services. Please support IP based firewall and service endpoints!

    27 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  7. Improve Faceting accuracy by having an option to count all records

    For fields that have a large distinct value diversity, the faceting feature gives inaccurate results unless the count parameter is set to a number greater than the number of distinct values in a field. There should be an option in an index field that indicates to the search engine to count and facet all the values in a column. I realize this would hurt performance so it should be optional. But sometimes accuracy is more important than raw performance for consumers of your service.

    26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  8. OpenSearch support for search federation

    Many companies use SharePoint as their entry point for search but federate actual searching across other data stores/sources.

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Enterprise  ·  Flag idea as inappropriate…  ·  Admin →
  9. Extend spatial features to allow indexing and searching of polygons and multi-polygons

    Extend spatial features to allow indexing and searching of polygons and multi-polygons

    20 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 →
  10. Add support to Blob indexer for OpenOffice formats

    Enable searching of OpenOffice documents stored in Azure Blob storage by adding support for indexing OpenOffice formats such as .odt, .ott, .oth, .odm, .ods, .ots, .odp, .odg, and .otp.

    18 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 →
  11. Support Edm.Date type

    Azure Search only supports Edm.DateTimeOffset. This is great for timestamps and other point-in-time data. However, it's horrible for things like birthdays, invoice dates, and other whole-date scenarios.

    1976-08-27 is very different than 1976-08-27T00:00:00Z.

    Edm.Date was added to OData v4 for this exact reason. It should be a primitive type in Azure Search as well.

    16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Data Types  ·  Flag idea as inappropriate…  ·  Admin →
  12. Managed service identity support

    Indexing Azure Storage requires a storage account key which makes it more cumbersome to rotate that storage account key. Indexing Azure SQL DB requires a username/password making it more cumbersome to rotate that password. Please allow us to enable a Managed Service Identity (MSI) for Azure Search so that we can index data sources using that identity rather than with account keys and passwords.

    14 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 →
  13. Add xpath syntax to promote out interesting values from source [XML] documents to predefined index fields

    I have lots of structured blobs (XML, JSON), I would like a mechanism to promote/extract a given field so it can be present in a specified index field rather than just rely on text in the content field? Or must I still run an external process to parse and write these promoted values instead of using built-in Azure Search features and the Data Source / Import process?

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  14. Enable browsing the index with only read permissions.

    With only read access I am not able to see indices, view or search in the index.

    12 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 →
  15. Return partial match for highlights

    Currently the highlight option return full word even if there was a partial match with the query text.

    For example for search text ‘gupt ashgu’ we get ‘Gupta’ and ‘ashgupta’ as the highlights. Instead it would be good to have only the matching parts to be highlighted so that user knows why those suggestions are being surfaced.

    "highlights":{
    "displayName":[
    "Ashish <em>Gupta</em> (WP)"],
    "mailNickname":[
    "<em>ashgupta</em>"]
    }

    Simple user scenario is, when user searches for ‘ashgu’ and we currently return top result as "Ashish Gupta, 'ashgupta’".

    The expected user experience is to show "Ashish Gupta, 'ashgu'pta", ie the exact things that…

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  16. Support synonym updates in Azure Portal

    synonym map operation is not frequency in Search opitmization operation. Customer can use Postman or so, but it also maintanance synonym map on Azure Portal is so helpful.

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Portal  ·  Flag idea as inappropriate…  ·  Admin →
  17. Add support for indexing PDF Custom meta data

    PDF Files allow custom meta data fields. In an archive it is good practice that the meta data is not separated from the document and hence we use the custom fields. We do however want to be able to search our archives don't want to have to write custom extractors to add the meta data to the index

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  18. index/crawl OneNote with deep links for results

    Be able to crawl OneNote with deep links for results

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  19. Allow to rename search index column

    Allow to rename search index column

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

    Thank you for your feedback. This is a fair suggestion and something I’d agree we should support. We’re considering this for a future release of Azure Search. Suggestions are typically addressed based on the total number of votes received.

    Thanks,
    Mike Carter
    Azure Search Product Team

  20. New Suggestions metadata in response (2014-10-20-Preview)

    Right now when you use the new suggestions feature, you get a match with some optional pre/post tags and a list of fields you indicated in OData select.

    For example, using names from AdventureWorksLT and a suggestor that searches the FirstName and LastName fields, I could make this query:

    https://[instance].search.windows.net/indexes/[index]/docs/suggest?api-version=2014-10-20-Preview&search=bon&suggesterName=namesuggestor&highlightPreTag=%3Cmark%3E&highlightPostTag=%3C%2Fmark%3E&$top=10&$select=FirstName,LastName

    {
    "value": [

    {
    
    &quot;@search.text&quot;: &quot;&lt;mark&gt;Bon&lt;/mark&gt;ifaz&quot;,
    &quot;FirstName&quot;: &quot;Luis&quot;,
    &quot;LastName&quot;: &quot;Bonifaz&quot;
    }

    ]
    }

    The payload is amazing already! For client libraries, it would be incredibly useful to also have an option to return an additional metadata field @search.field. This could indicate which field was "matched" when providing the result. So…

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base