Merge pull request #233202 from gmndrg/main

Update search-howto-indexing-azure-blob-storage.md

Author: prmerger-automator[bot]

articles/search/search-howto-indexing-azure-blob-storage.md

@@ -9,7 +9,7 @@ manager: nitinme
 
 ms.service: cognitive-search
 ms.topic: how-to
-ms.date: 03/30/2023
+ms.date: 04/03/2023
 ---
 
 # Index data from Azure Blob Storage
@@ -61,6 +61,11 @@ If you don't set up inclusion or exclusion criteria, the indexer will report an
 
 An indexer typically creates one search document per blob, where the text content and metadata are captured as searchable fields in an index. If blobs are whole files, you can potentially parse them into [multiple search documents](search-howto-index-one-to-many-blobs.md). For example, you can parse rows in a [CSV file](search-howto-index-csv-blobs.md) to create one search document per row.
 
+A compound or embedded document (such as a ZIP archive, a Word document with embedded Outlook email containing attachments, or an .MSG file with attachments) is also indexed as a single document. For example, all images extracted from the attachments of an .MSG file will be returned in the normalized_images field. If you have images, consider adding [AI enrichment](cognitive-search-concept-intro.md) to get more search utility from that content.
+
+Textual content of a document is extracted into a string field named "content". You can also extract standard and user-defined metadata.
+
+
 <a name="indexing-blob-metadata"></a>
 
 ### Indexing blob metadata