VAPI•7mo ago

azure Speech endpoint incorrect

Hi,
I signed up to azure speech to connect as an external provider. I chose Australia east (the only australia region) and the endpoint in auzre is : https://australiaeast.api.cognitive.microsoft.com/

can't change this

t when I paste my API key into vapi i get - ENOTFOUND australia.tts.speech.microsoft.com - error saving credentials

how do I connect azure speech service using the australia region?

KyleAPP•5/26/25, 11:01 AM

Hi jicka,

To connect Azure Speech Service using the Australia East region in Vapi, make sure you're specifying the correct region identifier. Based on the latest changelog from December 19, 2024, ensure the region is correctly updated in your settings.

In your case, if you're still facing issues, verify:

Use australiaeastaustraliaeast as the region (not just australiaaustralia).
In the Vapi Dashboard, navigate to “Provider Keys” and update the region correctly.
Double-check your API key and the region code for spelling or syntax errors.

If the problem persists, it might be worth checking the regional configuration on Azure to ensure no mismatch.

ordinary-sapphireOP•5/26/25, 11:55 AM

hi thanks for your response - in vapi - external key providers - the only option i can select is 'australia' - is there some other locaiton where I can change the endpoint? in azure speech service i can't change the location or endpoint - when setting it up can just choose aus east and it has the endpoint set

but I also don't have the option to change hte endpoint in vapi either

Vapi Support BotAPP•5/26/25, 11:57 AM

To connect Azure Speech Service for Australia East in Vapi, you must use australiaeastaustraliaeast as the region code in the Provider Keys section. If the Vapi dashboard only allows "australia" and not "australiaeast", this may be a UI limitation or bug. I recommend reaching out to Vapi support directly and providing a screenshot of the issue, as the documentation expects the exact Azure region code to be used and does not mention a manual endpoint override (changelog reference).

Source:

Vapi Changelog: December 19, 2024

⤵️ Mention @Vapi Support Bot for follow-ups 🐥

ordinary-sapphireOP•5/26/25, 12:00 PM

Vapi Support BotAPP•5/26/25, 12:02 PM

Since the Vapi dashboard only allows "Australia" and not the required "australiaeast" region code, this appears to be a UI limitation or bug.
The documentation expects you to use the exact Azure region code (australiaeastaustraliaeast), but there is no option to manually override the endpoint.
Action: Please contact Vapi support and provide your screenshot, as this will help them resolve the mismatch between the documentation and the dashboard UI.
Reference: Vapi Changelog, December 19, 2024

Source:

Vapi Changelog: December 19, 2024

KyleAPP•5/28/25, 6:19 AM

Vapi’s dashboard currently only supports Azure Speech keys from the Australia region; to use other regions, you’ll need to create a Speech resource in that region and configure it via the API.

ordinary-sapphireOP•5/29/25, 12:33 AM

Hi thanks - I did create a speech resrouce in that region but it does not match. Azure only has 1 speec resource location for australia and hte API endpoints do not match

KyleAPP•5/29/25, 8:40 PM

Hey @Jicka, just to keep you in the loop, I am taking a look into it but it is taking some time as we need to dig deeper into it.

ordinary-sapphireOP•5/29/25, 10:17 PM

@Shubham Bajaj ok thanks for the update - I posted earlier but just to recap for you

azure endpoint https://australiaeast.api.cognitive.microsoft.com/
- I double checked in Azure and this is the only australia region and you cannot change the endpoint
Vapi endpoint error - australia.tts.speech.microsoft.com - vapi only has 1 australia location as well but the endpoints don't match.

I looked in API documentation to see if I could change by API but its not an assistant or tool etc so doesnt look like it can be changed by the user

ordinary-sapphireOP•5/29/25, 10:20 PM

i double checked and azure does not support endpoint override - so I don't know if possible to update the endpoint to match azure's on teh vapi side. Anyway thanks again

KyleAPP•5/30/25, 2:03 PM

Sure, I will start looking into it after some time and then get back to you.

ill-bronze•8/30/25, 6:28 PM

hey there, this is quite a breaking bug. all your integrations are going to the dns endpoint region.tts.speech.microsoft.com whilst the actual endpoints are now under cognative services region.api.cognitive.microsoft.com/

this is also not the only API bug there is. IMO you should allow us to add the connecting endpoint manually so you dont have to hotfix when upstream providers change their endpoints.

KyleAPP•11/18/25, 4:04 AM

I sincerely apologize for the delayed response to your support request.
We implemented better tracking for support tickets to ensure timely responses going forward, but due to a technical limitation, this only applies to tickets created after this past week.
I'm closing this older ticket, but if your issue still needs attention, please:
Reply with 'REOPEN' or
Email support@vapi.ai with any updates
I'll personally ensure your new request gets prompt attention.
Thank you for your patience.
Best regards,
Vapi Support Team

azure Speech endpoint incorrect

Similar Threads

Similar Threads

Similar Threads