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-dotnet.md

Azure Document Intelligence — .NET SDK Quick Reference

Condensed from azure-ai-document-intelligence-dotnet. Full patterns (custom models, classifiers, layout extraction) in the azure-ai-document-intelligence-dotnet plugin skill if installed.

Install

dotnet add package Azure.AI.DocumentIntelligence

Quick Start

using Azure.AI.DocumentIntelligence;
var client = new DocumentIntelligenceClient(new Uri(endpoint), credential);
var adminClient = new DocumentIntelligenceAdministrationClient(new Uri(endpoint), credential);

Non-Obvious Patterns

  • Analyze is async LRO: await client.AnalyzeDocumentAsync(WaitUntil.Completed, "prebuilt-invoice", uri)
  • Field access: document.Fields.TryGetValue("VendorName", out DocumentField field)
  • Custom model build: BuildDocumentModelOptions(modelId, DocumentBuildMode.Template, blobSource)
  • Entra ID requires custom subdomain, not regional endpoint

Best Practices

  1. Use DefaultAzureCredential for local development only. In production, use ManagedIdentityCredential — see auth-best-practices.md
  2. Reuse client instances — clients are thread-safe
  3. Handle long-running operations with WaitUntil.Completed
  4. Check field confidence — always verify Confidence property
  5. Use appropriate model — prebuilt for common docs, custom for specialized
  6. Use custom subdomain — required for Entra ID authentication