Hello Rich !
Thank you for posting on Microsoft Learn.
I think this is a Genesys filtering/UX thing.
Multilingual Azure voices (like Cora) have a primary locale in the name (for example en-US-CoraMultilingualNeural). Even though they can speak more than 50 languages, they’re cataloged under their primary locale.
If a tool (like the Genesys Azure TTS integration) lists voices by the selected locale only, it won’t show Cora when you pick fr-CA or es-ES. That’s expected behavior. https://developer.signalwire.com/voice/tts/azure
https://learn.microsoft.com/en-us/azure/ai-services/speech-service/rest-text-to-speech
https://speech.azure.cn/portal/voicegallery
You can set the TTS engine to Azure and choose English (US), then select en-US-CoraMultilingualNeural as the voice even for your French-Canada or Spanish flows. Genesys allows using a TTS voice that doesn’t match the flow language, and Azure multilingual voices will speak the input text in those languages.
https://help.dev-genesys.cloud/190641
https://learn.microsoft.com/en-us/azure/ai-services/speech-service/get-started-text-to-speech