An issue with Azure AI Content Understanding (API version 2025-05-01-preview) in the West US region. Deploying a custom analyzer intended for verbatim transcription, including filler word detection, speaker diarization, and word-level timestamps. While the analyzer schema is accepted and the analyzer status returns "ready", the resulting configuration silently defaults to "mode": "standard" and omits the requested features.
Submitted analyzer schema:
{
"kind": "speechContentRecognizer",
"version": "2025-05-01-preview",
"displayName": "verbatim-tx-audioAnalyzer",
"description": "Verbatim transcription using prebuilt-audioAnalyzer to include fillers, diarization & timestamps",
"baseAnalyzerId": "prebuilt-audioAnalyzer",
"config": {
"returnDetails": true,
"disableContentFiltering": true
},
"properties": {
"mode": "verbatim",
"includeFillerWords": true,
"includeSpeakerDiarization": true,
"includeWordTimestamps": true,
"enablePunctuation": true
}
}
Analyzer response received:
{
"analyzerId": "verbatim-tx-157520ed-87c9-4eda-b166-f2ab407xxxxx",
"description": "Verbatim transcription with fillers, diarization & timestamps",
"createdAt": "2025-08-23T19:08:04Z",
"lastModifiedAt": "2025-08-23T19:08:04Z",
"baseAnalyzerId": "prebuilt-audioAnalyzer",
"config": {
"returnDetails": true,
"disableContentFiltering": false
},
"warnings": [],
"status": "ready",
"processingLocation": "geography",
"mode": "standard"
}
Issue Summary
- Analyzer deploys successfully but silently ignores key schema fields
-
"mode" reverts to "standard" despite "verbatim" being declared
-
"includeFillerWords" and "includeSpeakerDiarization" etc. appear unsupported or inactive, although subsequent transcriptions using this analyzer does include diarization and word timestamps, but no filler words, hence not verbatim.
- No warnings or errors are returned to indicate schema rejection
Requests
- Are these properties (
mode: verbatim, includeFillerWords) currently supported in the West US region (or elsewhere) under 2025-05-01-preview?
- Is there a limitation with
prebuilt-audioAnalyzer that prevents these properties from being applied?
- Are additional feature flags or subscription-level permissions required to activate these preview capabilities?
Any information is greatly appreciated, thanks!