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 IP firewall\service endpoints

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

    34 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  2. Change hit higlighting to handle line breaks as well as sentences

    It looks like the highlighting feature returns the full sentence around the highlighted term. This makes sense and works when the content has full stops in it.

    We are indexing documents which have bullet points and lists which do not have a full stop. As a result Azure search returns a large amount of content around the highlighted term.

    33 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. 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 →
  4. 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 →
  5. 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 →
  6. 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 →
  7. Proper support for DateTimeOffset

    Search should ingest and support a true implementation of DateTimeOffset. The current implementation merely converts an incoming DateTimeOffset to a DateTime in UTC, subsequently resulting in the loss of data, as the original offset can no longer be retrieved. The currently implementation necessitates persisting a related sidecar attribute of the original offset and subsequently requires the consumer to convert and rehydrate the property. This is exceptionally tedious, especially for use cases with several dozen DateTimeOffset attributes with varying offsets.

    26 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 →
  8. 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 →
  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

    24 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. 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 →
  11. 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 →
  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.

    18 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. 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 →
  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.

    15 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. Indexer(crawler) on Sharepoint document library or any external data source

    Customer has a lot of documents in sharepoint document library.Unlike pushing data to an index, crawling all the documents from external data source(here it is sharepoint) and creating an index in azure search so that we can leverage cognitive services.

    We understood sharepoint integration with azure search is present in your roadmap, but if there is a possibility to leverage index(crawler) to index external data source it would be great. There are lot of clients approaching for this usecase.

    Thanks for your time.

    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 →
  16. 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 →
  17. Ability to iterate over all documents in an index

    Other search engines have the ability to examine the contents of an index by simply iterating over the document collection. This is extremely use for maintenance operations like reconciling the contents of the index to records in a database. It is quite easy for records to be left behind in the index which no longer have relevance. The only way to accomplish this now is by searching and paging through the results. My current index has over 100,000 entries which is the limitation of the Skip directive. The recommended workaround is to filter the data on another field, however this…

    13 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 →
  18. Allow to rename search index column

    Allow to rename search index column

    13 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

  19. 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 →
  20. 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 →
  • Don't see your idea?

Feedback and Knowledge Base