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. 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 →
  2. Offer reserved pricing on Azure Search (similar to AWS ElasticSearch)

    AWS offers up to 52% discount when committing to a 3 year reserved instance for AWS ElasticSearch.

    There is no reserved pricing option for Azure Search.

    Please provide reserved pricing, similar to Cosmos DB/Azure SQL, at a discount comparable to AWS.

    34 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →
  3. Please make it possible to rename an index.

    Please make it possible to rename an index.

    10 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 →
  4. Storage Optimized tier in the Basic tier pricing range (L0)

    For a small business with low traffic and data just over the 2GB limit of the Basic tier it´s really hard to justify to upgrade to standard tier for 3.3x more cost. The performance and scaling for Basic tier is more the enough but the 2GB limit is just to low.
    It would be nice if you could introduce storage optimized layer(L0) for the lower end of the price range where performance and scaling is not important but the storage amount is more than 2GB.

    115 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →
  5. Support correlated search on complex collections

    Now that Azure Search supports complex types, it would be useful to be able to combine full-text search and strict Boolean filters when querying over complex collections. Currently this is not possible -- search.ismatch()/ismatchscoring() are not allowed in lambda expressions, and using sub-fields of complex collections in full Lucene queries has uncorrelated semantics.

    For example, if you want to search for hotels that have deluxe rooms with city views, none of these gives you exactly what you want:

    search=Rooms/Description:(city views) AND Rooms/Type:(Deluxe Room)

    search=Rooms/Description:(city views)&$filter=Rooms/any(room: room/Type eq 'Deluxe Room')

    $filter=search.ismatchscoring('city views') and Rooms/any(room: room/Type eq 'Deluxe Room')

    Instead, what you'd…

    67 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 →
  6. can we combine custom analyzer with fuzzy search?

    i recently tried the phonetic filter in custom analyser. But it wasnt complete. I also needed words which sounded similar but were also spelled wrong

    1 vote
    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 →
  7. Add malware scanning as part of the ingestion process / connector story

    Scanning content prior to ingestion is not part of the KM pipeline and slows the process down as you have to create separate machines onto which you have to stage and process content. Connectors do not allow for the inclusion of staging and are a risk vector.

    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 →
  8. Re-Indexing framework

    Azure Cognitive Search should allow for ease of rebuilding index from scratch without impacting the existing search. Flexibility in custom ingestion should also be allowed.

    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 →
  9. Multiple matching words listed higher

    Is there a possibility to get search ranked results based on multiple matched words? I will give an example:
    The input is "event test example" and I would like to have the results with more matching words higher than the other.
    So the response could be:
    1. "event test example"
    2. "event example"
    3. "event"
    4. "example"

    Is there a functionality in Azure search for this process?

    Thank you!

    1 vote
    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 →
  10. Make it easier to test custom analyzers

    Today it i cumbersome and time consuming to test a custom analyzer. You have to create it, then test.

    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 →
  11. Selecting subset data from complex collection

    We have the User's data with complex collection storing various groups the user has access to :

    -UserID
    -FirstName (String)
    -LastName (String)
    - Address
    ..
    ..
    -Groups (Complex Type(Collection))
    -- GroupID (int)
    -- Tags (Collection)
    -- GroupName (String)
    --..

    What we want to select is UserID, GroupName & Tags matching the GroupID passed.

    SerchParameter.Filter = "UserID=1 and GroupID in (2,4)"
    SerchParameter.FilterFields = "UserID, Groups" .. FilterFields is something new different form SearchParameter.Fields

    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 →
  12. Suggest API is not returning matching results count

    I am using suggestion API in my application .If there are matching results more than 100 there is no option to identify the match results count.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
  13. How to rename index or indexer? once it is created?

    Correctly it is not possible to rename index or indexer once it is created. It is difficult to admin or developer to create index or indexer from the scratch. Please provide some option on indexer should be update. Also provide some option to create indexer using existing one.

    8 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 →
  14. Azure Blob Storage soft delete is not compatible with Azure Search

    To track deletions, a soft delete policy is required in the data source. Something Azure Storage supports. However, it is not compatible with Azure Search. This should be an out-of-the-box feature in Azure Search.

    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 →
  15. Extract Graph in pdf file

    I would like to suggest to include the function of extract the graph or image in the documents file like PDF, words and PowerPoint .

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
  16. TLS configurable property

    Could we have a configurable property to set the minimum TLS version that search service will accept (as per Redis Cache and other resource types). With the removal of 1.0 and 1.1 on 6th Feb 2020 it would have been useful to set in advance to ensure that all endpoints talking to it were using 1.2 - I would assume that this same scenario will exist in the future when new versions make 1.2+ obsolete.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
  17. Search Explorer in the Portal should interoperate better with SDKs

    Currently, Search Explorer provides the full URL of the GET request for the Search REST API. To use a query from Search Explorer in the SDK, you have to parse out the parameters by hand, and sometimes URL decode them.

    It would be better if Search Explorer could provide code snippets for each supported language (C# and F# for now, Java, JavaScript/TypeScript, and Python when those SDKs are available) that show how to call the Search API using the parameters that the Portal user has typed in.

    4 votes
    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 →
  18. Record Identifier for Child Entities in Highlights

    Currently, only the field name and the snippet of text are returned in the Highlights collection. In scenarios where matches are found in sub or child entities, it can be essential to identify which of the child entities the match was found - more important than the field name in most cases.

    Example 1:
    An index is built with Topics which have collections of Messages associated with them. Topic has fields like Title and Summary, and Message has fields of Author, Heading, Body

    Highlights would only provide a Key of something like "Title", and "Message/Body"
    If the desired rendering of…

    1 vote
    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 →
  19. Auto Suggester field order

    Hi Team,
    We are using Azure search for 2 yaers now. We have a requirement where we want to show auto suggester in some order. Say if we have 3 fields as auto suggestor[Name, title, city]. We want that the value from Name should come first then the remaining ones

    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 →
  20. Allow access to stored term frequencies for searchable fields

    Term frequencies are maintained for searchable fields in order to compute things like TF/IDF quickly. It should be possible to access those term frequencies for additional analysis.

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

    Given the current API surface area of Azure Search, how would you actually use these term frequencies? Said another way, what other capabilities would you require in the API in order for term frequencies to actually be useful?

    Thank you for your feedback. While it is unlikely we’ll address this suggestion in the near future, we’ll reassess based on the number of votes it receives.

    Thanks,
    Mike Carter
    Azure Search Product Team

← Previous 1 3 4 5 12 13
  • Don't see your idea?

Feedback and Knowledge Base