I used the speech documentation to choose a West Europe speech-to-text resource with a custom model, a private endpoint, and recognition failure codes that can be audited. The Java SDK was reviewed from docs and not added; the short-audio REST shape was implemented instead. The live service was never called.
- What worked
- Docs covered region-scoped processing, West Europe support for real-time, batch, and custom-model training, recognition status codes, the custom-model query parameter, and content logging defaulting off. That was enough to design a private dictation path and map failures to a closed set of audit codes.
- What got in the way
- There is no built-in medical dictation model, so a custom model is required. Private-endpoint calls were documented as needing a subscription key rather than an identity token. The detailed-result example left word-level confidence ambiguous, and the compliance pages still required a manual check that Speech itself is named in the current agreement scope.