Azure Community Support

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.

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 .

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.

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 the results was to show a Topic, with the snippet of each Message with matching search text, and provide the user with the option to click on each Message snippet to be taken to the full Message, there is no way to do this with the current Highlights information. While a workaround might in some cases be to build an index at the Message level, with the Topic data copied over and over along with each document, this doesn't address if the parent has multiple child entities associated with it. Example 2: Topic has fields of Title and Summary Topic has a collection of 0-to-many Message entities, with Author, Heading, and Body fields. Topic also has a similar collection 0-to-many Category entities tied to it, with fields like Title and Description. Topic also has a collection of Reference entities with lots of text fields. In this scenario, a search for a text value may find hits in Topic, multiple Message entities within the Topic, multiple Category entities within the Topic, and multiple Reference entities within the Topic. Building separate indexes at the Message, Category, and Reference level with the Topic information copied over and over again becomes ineffective and impractical.

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.

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 .

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.

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 the results was to show a Topic, with the snippet of each Message with matching search text, and provide the user with the option to click on each Message snippet to be taken to the full Message, there is no way to do this with the current Highlights information. While a workaround might in some cases be to build an index at the Message level, with the Topic data copied over and over along with each document, this doesn't address if the parent has multiple child entities associated with it. Example 2: Topic has fields of Title and Summary Topic has a collection of 0-to-many Message entities, with Author, Heading, and Body fields. Topic also has a similar collection 0-to-many Category entities tied to it, with fields like Title and Description. Topic also has a collection of Reference entities with lots of text fields. In this scenario, a search for a text value may find hits in Topic, multiple Message entities within the Topic, multiple Category entities within the Topic, and multiple Reference entities within the Topic. Building separate indexes at the Message, Category, and Reference level with the Topic information copied over and over again becomes ineffective and impractical.

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.

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 .

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.

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 the results was to show a Topic, with the snippet of each Message with matching search text, and provide the user with the option to click on each Message snippet to be taken to the full Message, there is no way to do this with the current Highlights information. While a workaround might in some cases be to build an index at the Message level, with the Topic data copied over and over along with each document, this doesn't address if the parent has multiple child entities associated with it. Example 2: Topic has fields of Title and Summary Topic has a collection of 0-to-many Message entities, with Author, Heading, and Body fields. Topic also has a similar collection 0-to-many Category entities tied to it, with fields like Title and Description. Topic also has a collection of Reference entities with lots of text fields. In this scenario, a search for a text value may find hits in Topic, multiple Message entities within the Topic, multiple Category entities within the Topic, and multiple Reference entities within the Topic. Building separate indexes at the Message, Category, and Reference level with the Topic information copied over and over again becomes ineffective and impractical.

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.

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 .

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.

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 the results was to show a Topic, with the snippet of each Message with matching search text, and provide the user with the option to click on each Message snippet to be taken to the full Message, there is no way to do this with the current Highlights information. While a workaround might in some cases be to build an index at the Message level, with the Topic data copied over and over along with each document, this doesn't address if the parent has multiple child entities associated with it. Example 2: Topic has fields of Title and Summary Topic has a collection of 0-to-many Message entities, with Author, Heading, and Body fields. Topic also has a similar collection 0-to-many Category entities tied to it, with fields like Title and Description. Topic also has a collection of Reference entities with lots of text fields. In this scenario, a search for a text value may find hits in Topic, multiple Message entities within the Topic, multiple Category entities within the Topic, and multiple Reference entities within the Topic. Building separate indexes at the Message, Category, and Reference level with the Topic information copied over and over again becomes ineffective and impractical.