Hello vijo.jose,
Welcome to the Microsoft Q&A and thank you for posting your questions here.
I understand that you are having issues with Ryan Multilingual Voice – Accent Changing from American to Australian.
Most of all, you will need to understand that multilingual voices dynamically adjust accents based on input/text unless explicitly locked to a locale. The issue likely stems from missing SSML restrictions or regional misconfigurations, not updates/network issues. Follow the below steps to address this and ensure consistent accent output.
- Ensure live calls use SSML with strict locale enforcement:
<voice name='en-US-RyanMultilingualNeural'>
<lang xml:lang='en-US'>[Your text here]</lang>
</voice>
This prevents automatic accent detection based on input text.
- Confirm the exact voice name in live calls matches the Speech Studio version. Multilingual voices have region-specific identifiers (e.g.,
en-US-RyanMultilingualNeural
vs. a generic "Ryan" alias). - Check if the Yellow server uses the same Azure region as Speech Studio (e.g.,
eastus
vs.australiaeast
). Accent shifts may occur if the server defaults to an Australian endpoint. - Audit live call inputs for phrases/spellings that might trigger Australian English (e.g., "colour" vs. "color"). Multilingual models auto-adapt to dialects unless explicitly restricted.
- Capture raw SSML/logs from live calls where the accent shifted. Compare against Speech Studio requests to identify discrepancies in voice parameters or locales.
- If the above doesn't work as expected contact Microsoft Support via your Azure Portal to escalate with the following details:
- SSML snippets from failed/successful calls.
- Azure region and voice model name used.
- Timestamps/logs of accent shifts.
I hope this is helpful! Do not hesitate to let me know if you have any other questions.
Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.