AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

azure-ai

Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-ai at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 16

references/sdk/azure-ai-document-intelligence-ts.md

Azure Document Intelligence — TypeScript SDK Quick Reference

Condensed from azure-ai-document-intelligence-ts. Full patterns (custom models, classifiers, batch polling) in the azure-ai-document-intelligence-ts plugin skill if installed.

Install

npm install @azure-rest/ai-document-intelligence @azure/identity

Quick Start

Auth: DefaultAzureCredential is for local development. See auth-best-practices.md for production patterns.

import DocumentIntelligence, { isUnexpected, getLongRunningPoller, AnalyzeOperationOutput } from "@azure-rest/ai-document-intelligence";
const client = DocumentIntelligence(endpoint, new DefaultAzureCredential());

Non-Obvious Patterns

  • REST client — DocumentIntelligence is a function, not a class
  • Analyze path: client.path("/documentModels/{modelId}:analyze", "prebuilt-layout").post({...})
  • Must use getLongRunningPoller(client, initialResponse) then poller.pollUntilDone()
  • Local file: send as base64Source in body, not as binary stream
  • Pagination: import { paginate } from "@azure-rest/ai-document-intelligence"

Best Practices

  1. Use getLongRunningPoller() — document analysis is async, always poll
  2. Check isUnexpected() — type guard for proper error handling
  3. Choose the right model — prebuilt when possible, custom for specialized docs
  4. Handle confidence scores — set thresholds for your use case
  5. Use paginate() helper for listing models
  6. Prefer neural mode for custom models over template