Hi, I'm struggling with this integration. I've created the Azure speech resource, and have my keys. In the VAPI integrations page I try selecting region UK and add my key, but it keeps getting rejected with error because VAPI is trying https://uk.tts.speech.microsoft.com whereas apparently it should be https://uksouth.tts.speech.microsoft.com Can anyone advise?

It looks like VAPI is trying to use a generic UK endpoint, but Azure TTS actually needs the full regional URL like https://uksouth.tts.speech.microsoft.com. The best approach is to set the full endpoint in your VAPI settings or SDK instead of just picking the region. Have you tried entering the full uksouth endpoint directly to see if that fixes the key rejection? @James

Have you tried immigrating away from the UK? Try moving to Canada or US (:

Hi, thanks for the reply. The endpoints are already in the VAPI settings, I can only pick UK and there is nowhere to actually type in the full regional URL

Since VAPI only allows selecting “UK” and doesn’t expose the full endpoint, this points to a region-mapping issue on the VAPI side rather than a problem with your Azure keys. The way to approach this is to first confirm the Azure Speech resource region, then validate which endpoint VAPI’s “UK” option actually resolves to, and, if needed, test with a supported region as a temporary workaround. From there, this typically requires escalation to VAPI so they can correct the Azure endpoint mapping. I can help you walk through this step by step and narrow it down quickly, let’s discuss the details privately. @James

Hi James, In VAPI, it seems like a region-mapping issue is causing your Azure TTS integration to use the incorrect endpoint. While "UK" is available as a region option, Azure requires more specific endpoints like

https://uksouth.tts.speech.microsoft.com

. To resolve this, you should directly set the full regional endpoint in your integration configuration if the VAPI interface doesn't allow typing it directly. Here’s the general approach: 1. **Verify Azure Resource Details**: Ensure your Azure Speech resource is indeed set up for a specific region, such as

UK South

. 2. **API Workaround**: If the settings page restricts direct URL input, use the VAPI API to create or modify integrations. You can specify the exact endpoint through the API call. Here’s a cURL template you can adjust to update your integration:

bash
   curl -X POST "https://api.vapi.ai/credential" \
   -H "Authorization: Bearer YOUR_VAPI_API_KEY" \
   -H "Content-Type: application/json" \
   -d '{
     "provider": "azure",
     "service": "speech",
     "region": "uk",   // Keep this or adjust textually considering VAPI mappings
     "apiKey": "YOUR_AZURE_SPEECH_API_KEY",
     "openAIEndpoint": "https://uksouth.tts.speech.microsoft.com"
   }'

3. **Testing and Escalation**: After implementing this, test the connection again. If there's no improvement, consider reaching out to support through discussions or direct channels for further assistance and to report or request adjustments on VAPI’s mapping for various Azure regions. These steps should help in addressing the endpoint mismatch. Let me know if you need further clarification or assistance.