Index of every page on this site: llms.txt
All skills
microsoft avatar

/azure-ai

@0d60658
by microsoftmicrosoft/skills3.2k stars
373
Run it yourself

Build and troubleshoot Azure AI Search, Speech, Document Intelligence, Content Understanding, Translator, Content Safety, and OpenAI apps. WHEN: AI Search, vector search, hybrid search, semantic search, indexer, speech-to-text, text-to-speech, fast or batch transcription, Speech SDK logs, session ID, result ID, OCR, document translation, glossary.

Use this Skill: https://skilld.dev/gh/microsoft/skills/azure-ai

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencescontent-understandingcustom-analyzers.md

≈1.1k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Content Understanding custom analyzers: create, label, tune and copy

For designing or improving custom analyzers in Azure Content Understanding (GA 2025-11-01 unless noted): field schema, extraction methods, confidence and grounding, labeled samples, classification, guardrail warnings and analyzer lifecycle. Setup and model defaults are in overview and setup.

Create and replace

  • PUT {endpoint}/contentunderstanding/analyzers/{analyzerId}?api-version=2025-11-01 returns 200/201 with Operation-Location; poll it before analyzing.
  • Base analyzers: prebuilt-document, prebuilt-image, prebuilt-audio, prebuilt-video.
  • Learn conflicts to plan around: analyzer ID characters ([a-zA-Z0-9._] in service limits vs hyphen allowed in the REST reference, so avoid hyphens), and reusing a name (migration guide: delete first; REST: allowReplace).
  • Limits: 100,000 analyzers per resource, 1,000 fields, 64-character field names, 4,096-character descriptions, 300 classify categories per field.

Field schema

  • Methods: extract (documents only; set estimateSourceAndConfidence: true on the field), generate, classify. If method is omitted the service picks one. Learn conflict: best practices say set it explicitly; the migration guide says add it only when you need verbatim extraction. Decide per field and test both on your validation set.
  • Descriptions drive quality: be specific, list aliases and abbreviations used in your documents, phrase affirmatively, and write in the document language.
  • Confidence and grounding are opt-in (estimateFieldSourceAndConfidence, documents only; extract, classify and generate fields). returnDetails defaults to false.

Labeled samples

  • Add labeled documents in CU Studio; the API represents them as knowledgeSources of kind labeledData (containerUrl, prefix, fileListPath). Documents only; not used for generate fields.
  • GA analyzers keep the labeled data and use it at analysis time; 2026-06-01-preview distills it into the analyzer (and preview analyzers with labeled data are billed at the advanced contextualization rate).
  • Storage and identity for Studio projects: Studio and storage.

Classification

GA classification lives in the analyzer (contentCategories, enableSegment): up to 200 categories for documents. Without an "other" category every input is forced into one of the defined categories.

Tune with evidence

  1. Keep a fixed validation set that reflects production variation.
  2. Change one thing per iteration (description, method, labeled samples).
  3. Compare per-field presence, confidence and grounding across analyzer versions; do not share field values. result.infos LLMStats entries show model usage per call.
  4. Promote by analyzer ID only after the new version matches or beats the old one.

Guardrail warnings

CU applies the guardrails of your model deployment and can return Succeeded with fields suppressed. Branch on result.warnings[].code and target, not on the message: HarmfulContentDetected (review) vs HarmfulContentFiltered (fields suppressed). Change the guardrail on your deployment; annotate-only mode needs approval.

Copy and delete

Copy is two calls in the opposite direction from Document Intelligence: :grantCopyAuthorization on the source (returns expiresAt), then :copy on the target. Delete with DELETE on the analyzer path (CU Contributor cannot delete analyzers; CU Owner can).

Sources (retrieved 2026-11-18): CU Studio quickstart · Analyzer improvement · Best practices · Analyzer reference · Service limits · Guardrails · Migrate preview to GA

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning11d4 checks · Risk SAFE
  • Gen Agent Trust Hub11d

    This skill provides tools and guidance for developing and troubleshooting Azure AI services. It includes a local diagnostic script for analyzing Speech SDK logs with robust safety controls, along with comprehensive references for official Azure SDKs and secure authentication practices.

  • Socket11d

    No alerts

  • Snyk11d

    Risk: LOW · No issues

  • Runlayer9mo

    15/15 files flagged

Signed by skilld at 0d60658. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 days ago
metadata
{
  "author": "Microsoft",
  "version": "1.2.6"
}

README badge

README badge for microsoft/skills/azure-ai