Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

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. Detailed Request Monitoring

    We use Sitecore CMS which now supports Azure Search indexes. During our implementation we have discovered that re-index process fails. Using Fiddler we found the Azure Search REST requests that returned 207 (Multi status) responses and then reviewed the response body to determine the errors.

    Beyond Fiddler running as a proxy and capturing the HTTPS traffic from Sitecore - we found no other way to get insight into the requests/responses from Azure Search service.

    We enabled Operation Log monitoring but the Operation Log monitoring does not provide details about request body and response body.

    We looked into Search Traffic Analytics,…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  2. Connector for local on-premises file shares

    We need to create an index from data that is stored on-premises file shares.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  3. Support to custom indexers

    Hi there,

    I believe it would be great to have the ability to create indexers to custom data sources, where maybe we can provide some mapping configuration between data source fields and Search index fields, and the indexers would be able to automate the process of extracting, converting the data and storing it.

    Thank you.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  4. On bulk merge/upload, response should be 200 ok if document was successfully re-indexed

    The issue is documented here:
    https://stackoverflow.com/questions/50746146/does-mergeorupload-action-on-azure-search-index-takes-some-re-indexing-time-even

    Azure search should respond back with success message on successful re-indexing of the merged\uploaded data as against current behavior which seems to indicate "Merge \Upload request is taken up and would be indexed after unknown time, please keep looking"..

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your feedback. We understand the value this would bring, but there is concern about keeping an update request open the entire time it takes to index everything contain within it. What we may consider here is an API to request the status of the indexing queue to determine what has/hasn’t been processed. We’d like to know if this would be useful to you.

    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
    Azure Search Product Team

  5. Using request body in Postman against Sitecore Indexes

    It would be really cool if Postman could be used to query Sitecore Azure indexes with a request body instead of long querystrings. Post requests to /indexname/docs do not work

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  6. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  7. base64encode adds a 0 at the end.

    I use fieldMapping like following:

    {
          "sourceFieldName": "f1",
          "targetFieldName": "f2",
          "mappingFunction": {
            "name": "base64Encode",
            "parameters": null
          }
        }
    

    Field f2 always has a trailing zero.

    In my C# application I use 'Convert.ToBase64String' which doesnt have the 0 and the code fails to do what it needs to do.

    Please document why 0 is being added and how to handle it.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  8. Allow for metadata that disappeared from the original document to be also removed from the indexed document

    This is a user suggestion to allow for metadata that disappeared from the original document to be also removed from the indexed document:
    [Azure Search] Remove field value from index when not present in data source · Issue #6761 · Azure/azure-sdk-for-net (github.com)
    https://github.com/Azure/azure-sdk-for-net/issues/6761

    Currently we always do updates in mergeOrUpload mode:
    Add, Update or Delete Documents (Azure Cognitive Search REST API) | Microsoft Docs

    https://docs.microsoft.com/en-us/rest/api/searchservice/addupdate-or-delete-documents

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  9. Add tagging to each token such as POS, allowing to filter on them and receive them in results

    In Lucene you can add metadata to each token, which is then returned on search results.

    It would be great to be able to add predefined tags/metadata during indexing that will be later returned on search results. Filtering results based on these tags would also be great.

    Examples of tags can be:
    Part of Speech
    Dates
    Numbers
    Entities (person names, organizations)
    Locations (city, country names)

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  10. Indexing Collection data type from azure data factory copy activity is not supported.

    Hello,
    I have a use case to index collection (list) data into azure search index. I am using azure data factory to load data into azure search index. But it seems azure data factory copy activity does not support copy of String Array data type. The support is only available with primitive data types. Could you please add this functionality as many real life use cases have array/list in the data set.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  11. Visibility/metric for the usage of MultiHoming for validating if it works as expected

    We are looking to use the Multi-Homing feature for configuring the Azure search instance in the secondary region to retrieve data from the geo-replicated read-region instance of CosmosDB for making sure the dependencies are co-located in the same region. Though multi-homing feature is a great feature to resolve our multi-region requirements, there is no metric or visibility to validate if the setup is working as expected. We would like to have a metric to show which Cosmos DB instance the Azure search is indexing data from.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  14. Review of Knowledge Store

    I wrote a technical review of the Knowledge Store preview feature and wanted to share it with you. See attached.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  15. Allow Index Management by Azure CLI

    Implement create/delete/update indexes via the Azure CLI in addition to Azure REST Api capabilities. You can create the search service itself of course, but i see no way to create the index or indexers (e.g.) using Cli

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  16. Allow limiting blob documents to be indexed based on a specific metadata value

    We only want to index a subset of documents in our blob container and in order to do so now, we have to have two blob containers and manage them. Similar to how you can limit document types to be indexed or not, the ability to restrict the scope of Blob objects based on a metadata value would help reduce our operating expenses and document management overhead. We could add a new Metadata name called "AzureSearch" and if set to "true", would be picked up by the indexer. Removing it from the index would simply require changing that value and…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  17. Dynamic Field Indexing

    dynamic field indexing .. *string or *myindex columns to be auto indexed.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  18. Dynamic Field Indexing

    dynamic field indexing .. *string or *myindex columns to be auto indexed.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
1 3 Next →
  • Don't see your idea?

Feedback and Knowledge Base