
Azure Speech to Text
FreeEfficient audio transcription using Azure AI.
Free · Opens the source repo
What Azure Speech to Text does
The Azure Speech to Text skill enables developers and designers to transcribe audio files into text using Azure's Fast Transcription REST API. This skill is particularly useful when working with audio or video content that needs to be converted into a text format, such as generating subtitles or processing spoken content within projects like OpenMontage. By leveraging Azure's capabilities, users can achieve synchronous transcription with word-level timestamps, speaker diarization, and multi-language identification, making it versatile for various applications.
To utilize this skill, users must configure their Azure Speech resource by setting the AZURE_SPEECH_KEY and AZURE_SPEECH_REGION environment variables. Once configured, the azure_stt tool becomes available for use in transcription tasks. If Azure services are unavailable or if an offline solution is preferred, the skill automatically falls back to using the local transcriber tool based on faster-whisper, ensuring that users always have a reliable transcription method at their disposal.
The skill is designed to handle audio files up to approximately two hours in length and a few hundred megabytes per request. It is optimized for clean audio input, making it ideal for high-quality recordings such as interviews, podcasts, and presentations. The output from the Azure service matches the schema used by the local transcriber, allowing seamless integration into existing workflows without the need for additional adjustments.
In summary, this skill is an essential tool for anyone needing to convert audio content into text efficiently, whether for accessibility, content creation, or data processing purposes. Its integration with Azure's robust capabilities ensures high-quality results and flexibility in handling various audio formats.
When to use it
Use this skill when you need to transcribe audio files into text for subtitles, documentation, or analysis, particularly when leveraging Azure's cloud capabilities.
When not to use it
Avoid using this skill for real-time transcription of live audio streams, as it is designed for pre-recorded audio files only.
What you can build with it
Generating Subtitles for Videos
Use the Azure Speech to Text skill to transcribe video audio into text, creating accurate subtitles for accessibility.
Processing Interviews and Podcasts
Transcribe recorded interviews or podcasts to produce written content, making it easier to share insights and quotes.
Creating Text-Based Content from Audio
Convert audio presentations or lectures into text for documentation or further analysis, enhancing content accessibility.
How to install Azure Speech to Text
View source1. Install with the skills CLI
npx skills add calesthio/openmontage/azure-speech-to-text --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by calesthioAzure AI Speech — Speech-to-Text
Transcribe audio to text with Azure Fast Transcription — synchronous,
word-level timestamps, speaker diarization, and multi-language identification.
In OpenMontage this is exposed through the azure_stt tool (capability=analysis,
provider=azure). It is an optional cloud STT provider — when
AZURE_SPEECH_KEY is configured, prefer it for cloud transcription. The local
transcriber tool (faster-whisper) remains the default offline path and the
fallback when Azure is unavailable.
Why Fast Transcription (not Batch)
Azure exposes three STT surfaces. OpenMontage uses Fast Transcription because the pipeline transcribes local audio files:
| Surface | Input | Latency | Needs |
|---|---|---|---|
| Fast Transcription (used here) | local file, multipart POST | synchronous, sub-real-time | key + region |
| Batch Transcription | audio at a URL (Blob + SAS) | async job + polling | Blob storage plumbing |
Speech SDK (spx) | mic / stream / file | streaming | native azure-cognitiveservices-speech package |
Fast Transcription needs no Blob storage, no SAS URLs, and no native SDK — just
requests and the two env vars.
Setup
Create a Speech resource in the Azure portal; copy the key and region from its Keys and Endpoint page.
export AZURE_SPEECH_KEY=your_speech_resource_key
export AZURE_SPEECH_REGION=eastus # your resource's region
# export AZURE_SPEECH_ENDPOINT=https://... # optional: overrides region
azure_stt reports AVAILABLE once AZURE_SPEECH_KEY plus either
AZURE_SPEECH_REGION or AZURE_SPEECH_ENDPOINT are set.
Using it in a pipeline
Prefer azure_stt over transcriber unless the run must be offline. Its output
matches the transcriber schema exactly, so it is a drop-in for subtitle_gen
and any stage that consumes a transcript.
from tools.tool_registry import registry
registry.discover()
stt = registry._tools["azure_stt"]
result = stt.execute({
"input_path": "projects/my-video/assets/audio/narration.mp3",
# "language": "en", # ISO 639-1 or BCP-47 ("en-US"); omit for auto-ID
# "diarize": True, # speaker labels, no HuggingFace token needed
# "max_speakers": 4,
"output_dir": "projects/my-video/artifacts",
})
if result.success:
segs = result.data["segments"] # [{id,start,end,text,words:[...]}]
words = result.data["word_timestamps"] # flat [{word,start,end,probability}]
If azure_stt is unavailable (no key) or errors, fall back to transcriber
(local whisper) — its execute signature and output are identical.
Parameters that matter
language— pass an ISO code ("en") or a full locale ("en-US"). Pin it when you know the language; it is faster and more accurate than auto-ID.candidate_locales— whenlanguageis omitted, Azure runs language identification across this shortlist. Narrow it to the languages you actually expect; a huge list slows detection and invites misclassification.diarize/max_speakers— enable for multi-speaker audio (interviews, podcasts). Setmax_speakersto the real upper bound.profanity_filter—None|Masked(default) |Removed|Tags.
Response shape (mapped to the transcriber schema)
The raw Azure response (phrases[] with offsetMilliseconds / words[]) is
converted to seconds and the OpenMontage transcript schema:
{
"segments": [
{"id": 0, "start": 0.0, "end": 2.4, "text": "Hello world",
"speaker": 1,
"words": [{"word": "Hello", "start": 0.0, "end": 0.5, "probability": 0.98}]}
],
"word_timestamps": [{"word": "Hello", "start": 0.0, "end": 0.5, "probability": 0.98}],
"language": "en-US",
"duration_seconds": 2.4,
"provider": "azure"
}
Note: Fast Transcription has no per-word confidence, so each word carries the
phrase confidence in probability.
Limits & tips
- Single file up to ~2 hours / a few hundred MB per request. For longer or bulk jobs, use Azure Batch Transcription instead.
- Send clean audio (16 kHz+ mono is plenty). Transcode video to audio first if you only need speech — smaller upload, same result.
- Verify timing: word timestamps drive subtitle cues in
subtitle_gen. Spot-check the first and last cues against the source audio.
Frequently asked questions about Azure Speech to Text
Similar skills
WinMD API Search
Easily find and explore Windows desktop APIs.
WebMCPify
Transform any web app into an agent-ready platform.
Phoenix Tracing
Instrument LLM applications with OpenInference tracing.
Foundry Hosted Agent CopilotKit
Guidance for developing agentic web apps on Azure.
Power Automate Foundation
Connect AI agents to Power Automate seamlessly.
Power Automate Flow Builder
Efficiently build and deploy Power Automate flows programmatically.
