AdminThe Azure Team on UserVoice
(Admin, Microsoft Azure)
My feedback
-
29 votes
Thank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Liam
Azure Search Product Team -
740 votesAdminThe Azure Team on UserVoice
(Admin, Microsoft Azure)
supported this idea
·
-
64 votesAdminThe Azure Team on UserVoice
(Admin, Microsoft Azure)
supported this idea
·
-
16 votesAdminThe Azure Team on UserVoice
(Admin, Microsoft Azure)
supported this idea
·
-
247 votes
Exclude disk functionality for Write accelerator(WA) enabled disks is available now. No action is required from the user. During VM backup, Azure backup service automatically excludes the WA enabled disk and backs up the rest of the disks in a VM.
Exclude disk functionality for Write accelerator(WA) enabled disks is available now. No action is required from the user. During VM backup, Azure backup service automatically excludes the WA enabled disk and backs up the rest of the disks in a VM.
-
529 votes
Thank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Mike
Azure Search Product TeamThanks for the feedback. We would consider this the same request as aggregation support. Please let us know if you disagree.
Thanks,
Mike Carter
Azure Search Product TeamAdminThe Azure Team on UserVoice
(Admin, Microsoft Azure)
shared this idea
·
-
103 votes
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,
Vinod
Azure Search Product TeamAzure Search does support an analyze API which helps you understand what different analyzers, both out of box or custom, process text during indexing or query time. While not a full Explain API, this does help understand why a search term didn't return the results you expect. Doc link: https://docs.microsoft.com/en-us/rest/api/searchservice/test-analyzer
-
300 votesplanned · 12 comments · Azure Backup » Retention and Storage · Flag idea as inappropriate… · Admin →AdminThe Azure Team on UserVoice
(Admin, Microsoft Azure)
supported this idea
·
Hi,
Thank you for reaching out! Due to multiple threads referring to similar suggestions, we have merged them into one. Votes received on all previously existing ideas regarding archive storage shall not be disregarded and will continue to be used for prioritization.
-
11 votes
Are you asking for a calculated field who's value is populated while the indexer runs? This could either be a constant or potentially change based on the other values in the document.
I would suggest that we will deliver a form of this with Cognitive Search custom skills, which is currently in preview: https://docs.microsoft.com/en-us/azure/search/cognitive-search-custom-skill-interface
Please take a look and let us know if this is what you are looking for.
AdminThe Azure Team on UserVoice
(Admin, Microsoft Azure)
shared this idea
·
-
6 votes
This looks like feedback for the storage team. Moved to the appropriate team.
-
2 votes
Hi,
Thanks for the feedback! Can you tell us more about what is it that you're backing up?
Thanks,
Utsav -
19 votes
Backup pre-check is already available in the Azure portal. Are you referring to alerts/notification or a programmatic feedback while using Powershell/CLI?
-
38 votes
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,
Luis Cabrera
Azure Search Product TeamThanks for the feedback on creating Indexers standalone.
With regards to your other questions about editing existing Indexer properties (schedule, etc) from the portal, this functionality is supported today. Simply go into the Indexer section of the Portal, select an existing indexer and then click the 'Edit' button. This will let you modify the existing indexer schedule as well as many other properties.
-
42 votes
Thank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Elad
Azure Search Product TeamAdminThe Azure Team on UserVoice
(Admin, Microsoft Azure)
shared this idea
·
-
1,285 votes
We are ready to onboard more customers who are interested in participating in the private preview of Complex Types. If you’re interested, please contact us at azuresearch_contact@microsoft.com.
Please note that the private preview of Complex Types is only accessible via the REST API. We are working on .NET SDK support for the Public Preview.
Also, if you get an error message when you email azuresearch_contact, don’t worry — we are receiving your requests and will reply to you individually.
Thanks!
We have received your requests, even though you're getting an error message back. It looks like our public distribution list includes a private list as a member, which is why you're seeing the error. I'll see if we can get it fixed. Please let us know by posting here if you do not receive a reply from us. Thanks!
-
39 votes
Thank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Liam
Azure Search Product TeamAdminThe Azure Team on UserVoice
(Admin, Microsoft Azure)
shared this idea
·
-
1 vote
We need more information in order to respond to this feedback. The search.in is a great option for filtering a field based on multiple values. Please take a look and let us know if it does not suit your needs.
Can you give an example of the kind of query you'd like to be able to write? Could the search.in function help (documented here: https://docs.microsoft.com/rest/api/searchservice/odata-expression-syntax-for-azure-search)?
-
19 votes
Please let us know if the below connector doesn’t meet your needs.
You can use Azure Data Factory PostgreSQL connector (https://docs.microsoft.com/azure/data-factory/data-factory-onprem-postgresql-connector) as the source and Azure Search connector (https://docs.microsoft.com/azure/data-factory/data-factory-azure-search-connector) as the sink to move data from PostgreSQL to Azure Search.
-
117 votes
This item has been marked as Started by mistake. We don’t have a short-term plan to deliver this feature but it is on our roadmap.
The synonyms functionality is now available in the preview api-version '2016-09-19-Preview'. Please see https://docs.microsoft.com/en-us/azure/search/search-synonyms for more details.
We are still looking into supportability of custom analyzer during lexical analysis. We will let you know once we have an update.
-
20 votes
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,
Vinod
Azure Search Product TeamAdminThe Azure Team on UserVoice
(Admin, Microsoft Azure)
supported this idea
·
One of the major reason to have support for other highlighters is limitations of Postings highlighter especially around highlighting of wild card and regex queries. The Postings highlighter doesn't return any terms from the index scan for wildcard queries when a scoring profile is applied on top of them.
Refer to more details here - https://stackoverflow.com/questions/54917754/azure-search-highlighting-doesnt-work-for-wildcards-with-scoring-profiles/54917926