Skip to content

Commit 266d464

Browse files
committed
Clarify image analyzer usage
1 parent c41a9ed commit 266d464

File tree

1 file changed

+2
-4
lines changed
  • articles/ai-services/content-understanding/image

1 file changed

+2
-4
lines changed

articles/ai-services/content-understanding/image/overview.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -42,12 +42,10 @@ Content Understanding offers several key benefits for extracting information fro
4242

4343
## Get started
4444

45-
Get started with processing images with Content Understanding by following our [REST API quickstart](LINK TO IMAGE TAB) or visiting [Azure AI Foundry](https://aka.ms/cu-landing) for a no code experience.
45+
Get started with processing images with Content Understanding by following our [REST API quickstart](../quickstart/use-rest-api.md?tabs=image) or visiting [Azure AI Foundry](https://aka.ms/cu-landing) for a no code experience.
4646

4747
> [!NOTE]
48-
> For best results, image schema should only be used to process non-document-based images.
49-
> Text heavy images of documents should be processed using a document schema.
50-
> Use cases that require extraction of text from document images or scanned documents should be processed using a document field extraction schema.
48+
> Image analyzers are currently not optimized for scenarios where analysis is based primarily on extracted text. If your main goal is to extract and analyze text from images, consider using a document field extraction schema instead.
5149
5250

5351
> [!IMPORTANT]

0 commit comments

Comments
 (0)