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

How can we improve Azure Search?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

  1. Support for Dictionary DataType

    Dictionary datatype is very common. Often, we'd like to store our data as a dictionary. Currently, I serialize and store it as a string. It'd be great if the dictionary type is supported.

    261 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Data Types  ·  Flag idea as inappropriate…  ·  Admin →

  2. Add support for inheritance ($type)

    Sometimes we have inheritance in our database tables. In my case, I have inheritance mapped to a table using EF Code First, and the table contains a generated column, [Discriminator], that tells the EF which type should be activated when fetching the entity.

    There should be a way for Azure Search (a field transformation function maybe) to map discriminators in the database to fully qualified non-searchable $type fields in the indexes, in order for the SDK to be able to deserialize the types correctly using the TypeNameHandling setting of the Json.net serializer.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Data Types  ·  Flag idea as inappropriate…  ·  Admin →

  3. 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.

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Data Types  ·  Flag idea as inappropriate…  ·  Admin →

  4. Support multi-fields

    It would be nice to have one data value analyzed multiple different ways.

    https://www.elastic.co/guide/en/elasticsearch/reference/current/multi-fields.html

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Data Types  ·  Flag idea as inappropriate…  ·  Admin →

  5. Support spatial data with flat projections

    Today Search supports 2d sphere lat/long spatial data. I would like to see support for flat projections, points, polygons and lines.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Data Types  ·  Flag idea as inappropriate…  ·  Admin →
    unplanned  ·  AdminThe Azure Team on UserVoice (Product Owner, Microsoft Azure) responded

    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.

    With the private preview of complex types (api version 2018-11-11-Preview) you will be able to store a line and leverage it for geospatial queries.

    Thanks,
    Vinod
    Azure Search Product Team

  6. Add combo field support

    Add ability to combine existing fields in index.

    Similar to SQL example below:

    ALTER TABLE SearchData ADD
    Combo As
    [Name] + char(32) +
    [Description] + char(32) +
    [MetaData] + char(32) +
    [OwnerData] + char(32) +
    [CategoryData] + char(32) PERSISTED

    Example in Azure Search:
    e.g.
    idx.FirstName = "John" Edm.String
    idx.LastName = "Doe" Edm.String
    idx.Name = "John Doe"; (Combo, of Firstname and lastname) (Internally could act as Collection(Edm.String) ??)

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Data Types  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Azure Search

Feedback and Knowledge Base

(thinking…)
Hosted by UserVoice