Speech service supported regions

• 11/05/2019
• 4 minutes to read
• • 
  • 
  • 
  • 
  • 
  • +7

The Speech service allows your application to convert audio to text, perform speech translation, and covert text to speech. The service is available in multiple regions with unique endpoints for the Speech SDK and REST APIs.

The Speech portal to perform custom configurations to your speech experience for all the regions is available here: https://speech.microsoft.com

For invocations of your Speech service, make sure the call matches the region for your subscription.

Speech SDK

In the Speech SDK, regions are specified as a string (for example, as a parameter to SpeechConfig.FromSubscription in the Speech SDK for C#).

Speech-to-text, text-to-speech, and translation

The speech customization portal is available here: https://speech.microsoft.com

The Speech service is available in these regions for speech recognition, text-to-speech, and translation:

If you use the Speech SDK, regions are specified by the Region identifier (for example, as a parameter to SpeechConfig.FromSubscription). Make sure the region is matching the region of your subscription.

Intent recognition

Available regions for intent recognition via the Speech SDK are the following:

This is a subset of the publishing regions supported by the Language Understanding service (LUIS).

Voice assistants

The Speech SDK supports voice assistant capabilities in these regions:

Speaker Recognition

Speaker Recognition is currently only available in the westus region.

REST APIs

The Speech service also exposes REST endpoints for speech-to-text and text-to-speech requests.

Speech-to-text

For speech-to-text reference documentation, see Speech-to-text REST API.

The endpoint for the REST API has this format:

https://<REGION_IDENTIFIER>.stt.speech.microsoft.com/speech/recognition/conversation/cognitiveservices/v1

Replace <REGION_IDENTIFIER> with the identifier matching the region of your subscription from this table:

Text-to-speech

For text-to-speech reference documentation, see Text-to-speech REST API.

Standard and neural voices

Use this table to determine availability of standard and neural voices by region/endpoint:

Custom voices

If you've created a custom voice font, use the endpoint that you've created. You can also use the endpoints listed below, replacing the {deploymentId} with the deployment ID for your voice model.