The correct indexing approach is to use an indexer to extract image data into a normalized_images collection . In Azure AI Search enrichment pipelines, embedded images in PDFs are not passed directly from the text content field into OCR. Instead, the indexer must perform document cracking and image extraction by enabling the indexer image action. Microsoft’s Azure AI Search documentation states that image-processing skills such as OCR and image analysis expect normalized images, and that enabling imageAction causes embedded images to be extracted and normalized for downstream skills.

The OCR skill is designed to receive image input from /document/normalized_images/*. Microsoft’s skillset tutorial specifically states that the OCR skill assumes a normalized_images field exists and that this field is generated by setting the indexer imageAction configuration to generateNormalizedImages. The document extraction skill reference also confirms that generateNormalizedImages creates an array of normalized images during document cracking for OCR and image analysis.

Option A is incorrect because OCR does not run directly against the index content field. Option B maps outputs after enrichment; it does not extract images. Option D reshapes data but does not create the required normalized image collection. Reference topics: Azure AI Search indexers, AI enrichment, OCR skill, imageAction, and normalized_images.