A unified Azure platform for creating and managing AI models, agents, and applications with built‑in enterprise security, monitoring, and governance
Hello @Kojok
Welcome to Microsoft Q&A .Thank you for reaching out to us.
This behavior is most likely occurring because the deployment can be successfully resolved by the service, but the runtime execution path for gpt-realtime-translate is not completing successfully through the Realtime API flows that were tested.
The key observation is that the same environment, authentication method, audio format, and overall workflow successfully work with gpt-realtime-whisper, while gpt-realtime-translate consistently returns OperationNotSupported, InvalidSessionType, HTTP 500 responses or unsuccessful WebSocket sessions. Since the same pattern is reproducible across multiple regions, the behavior does not appear to be related to a deployment configuration, authentication issue, audio formatting issue or a single-region scenario.
- The correct supported way to invoke gpt-realtime-translate The currently available guidance references the standard Realtime API patterns and points to the Realtime WebSocket and WebRTC workflows used by other Realtime models. However, a validated Azure-specific end-to-end example demonstrating successful translation inference with gpt-realtime-translate is not currently available.
- Endpoint and session type to be used The available guidance does not currently define a dedicated translation-specific session type such as session.type="translation" This aligns with the observed InvalidSessionType response. The recommended approach remains:
- Use the standard Realtime API workflow.
- Use the deployment name as the model identifier.
- Follow the documented Realtime session configuration.
- A target language parameter A dedicated Azure-specific translation session contract or target-language parameter for gpt-realtime-translate is not currently documented. Because translation inference is not successfully completing, the expected translation output configuration cannot be validated at this stage.
Please check if the following workarounds help-
- Whisper + Translation Workflow Streaming Audio > gpt-realtime-whisper > translation-capable service or model >anslated text or speech output
- Azure AI Speech Translation For production real-time speech translation workloads, Azure AI Speech Translation provides a supported speech translation capability and may serve as an alternative
The following references might be helpful , please check them out
- Use the GPT Realtime API for speech and audio with Azure OpenAI - Microsoft Foundry | Microsoft Learn
- Speech translation overview - Speech service - Foundry Tools | Microsoft Learn
Thank you
Please "Accept" the answer with an "Upvote" if the response was helpful. This will be benefitting other community members who face the same issue.