Voice Agent Common Invariants
Rules shared by GPT-Live Voice, Prompt Voice, and Hosted Voice services in azure.yaml. Determine the subtype first with Voice Agent subtypes.
Required Rules
- Place Voice fields directly under
services.<service-key>; never use a nestedconfig:block. - Follow the selected subtype's YAML reference; stop instead of combining subtype-specific shapes.
- Never use obsolete
modelType: hosted_agentortargetAgent. - Keep hosted target and Voice wrapper service keys and
namevalues distinct. - Preserve existing optional settings and omit optional fields the user did not request. Do not write unused optional fields as
null.
Lifecycle Boundaries
- Deploy Voice services with azd.
- Do not invoke a Voice service with
azd ai agent invoke. - GPT-Live Voice uses
/protocols/voice/live/sessions?api-version=v1; never send it through the ordinary/protocols/voicehelper. - Prompt Voice has no local container.
- Hosted target testing validates only its Voice Live Bridge handler; the Voice wrapper still requires end-to-end testing over the managed
voiceWebSocket.
Load only the selected subtype reference: