Azure Speech

Speech to text, text to speech, speech translation and speaker recognition over one endpoint.

Provider: azure
Kind: AI service
Category: Compute
Official docs: https://learn.microsoft.com/en-us/azure/ai-services/speech-service/speech-services-quotas-and-limits

Properties · 5 set by this component

property	type	values	required	kind default	this component
auth	enum	api-key \| oauth \| iam \| none	no	—	▸ api-key
concurrentSpeechToTextRequests · component property	integer	—	no	100	inherited
contentFiltering	boolean	—	no	—	inherited
customModelDeployments · component property	integer	—	no	50	inherited
customerManagedKeys	boolean	—	no	—	▸ false
dataResidency · advanced	enum	us \| eu \| asia \| global	no	—	inherited
dataRetentionDays	integer	—	no	—	inherited
keyStore	boolean	—	no	false	inherited
managed	boolean	—	no	false	▸ true
modality	enum	text \| vision \| speech \| multimodal \| structured \| image \| video \| audio \| embedding \| rerank	no	—	▸ speech
publicEndpoint	boolean	—	no	—	▸ true
quotaUnitsPerMinute	integer	—	no	—	inherited
rateLimitRpm · advanced	integer	—	no	—	inherited
rateLimitTpm · advanced	integer	—	no	—	inherited
textToSpeechTransactionsPerSecond · component property	integer	—	no	30	inherited
tier · component property	enum	f0 \| s0	no	—	inherited
viaGateway	boolean	—	no	false	inherited

Rules that apply · 2

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

AI API key not managedwarning

ai-api-key-unmanaged

This AI vendor is reached with an API key, and nothing in the design holds or rotates that key. It ends up in environment files or code, every caller shares it, and a single leak runs up the vendor bill until someone notices. Put the key in a key-management component, or say it is held there with keyStore.

— all of these hold:
— the node's `auth` is "api-key"
— the node's `keyStore` is false
— the node has at least one incoming edge from an app-server, worker or client
— this does not hold:
— the design contains a node of kind key-management

Stateful node without zone redundancyerror

stateful-node-without-zone-redundancy

A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.

— all of these hold:
— the node's `stateless` is false
— the node sits inside exactly 1 availability-zone group
— this does not hold:
— the node sits inside at least one cell group

Use it in a design

nodes:
  - { id: "ai-speech", component: "azure-ai-speech" }

Other AI service products · 125

and 85 more → AI service page

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Azure Speech: speech to text, text to speech, translation and speaker features on a Foundry Tools resource.
3# "Quotas and Limits for Azure Speech" gives the Standard (S0) defaults: 100 concurrent real-time speech-to-text requests, 30 text-to-speech transactions per second and 50 custom model deployments; "Configure Virtual Networks for Foundry Tools" states the resource accepts connections from any network by default.
4schemaVersion: "1"
5type: "component"
6id: "azure-ai-speech"
7kind: "ai-service"
8provider: "azure"
9docs: "https://learn.microsoft.com/en-us/azure/ai-services/speech-service/speech-services-quotas-and-limits"
10defaults:
11  auth: "api-key"
12  managed: true
13  modality: "speech"
14  publicEndpoint: true
15  customerManagedKeys: false
16properties:
17  tier:
18    type: "enum"
19    values: ["f0", "s0"]
20  concurrentSpeechToTextRequests:
21    type: "integer"
22    default: 100
23  textToSpeechTransactionsPerSecond:
24    type: "integer"
25    default: 30
26  customModelDeployments:
27    type: "integer"
28    default: 50

The same page as markdown, for an agent: /catalogue/components/azure-ai-speech.md