Azure
Plateforme et infrastructure de cloud computing pour la génération, le déploiement et la gestion d’applications et de services à travers un réseau mondial de centres de données gérés par Microsoft.
Fetching Azure Translation supported languages with private endpoint
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 43%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAO%3C/text%3E%3C/svg%3E)
Arthur-Olivier Fortin
140
Points de réputation
I’ve been trying to fetch the list of supported translation languages using our Translator resource configured with Virtual Network integration. However, I consistently receive a 404 error when calling the endpoint.
I followed the official documentation and successfully tested the public endpoint:
https://api.cognitive.microsofttranslator.com/languages?api-version=3.0
This works as expected.
However, when using our private endpoint in the format:
https://<your-custom-domain>.cognitiveservices.azure.com/languages?api-version=3.0
the request fails with a 404, even though other translation operations work correctly through the same private endpoint.
We’ve been using this Translator resource for a while, and the endpoint is generally reachable. I also temporarily disabled the VNet integration to rule out a network issue, but the same 404 persists when using the /languages path.
Documentation reference: https://learn.microsoft.com/en-us/azure/ai-services/translator/text-translation/reference/v3/languages#request-url
Could you clarify if the /languages endpoint is supported through custom domains or private endpoints?
Azure
{count} votes
-
Arthur-Olivier Fortin 140 Points de réputation
2025-06-27T19:11:56.78+00:00 After extensive trial and error, here’s what finally worked for me:
curl -X GET "https://<your-custom-domain>.cognitiveservices.azure.com/translator/text/v3.0/languages?api-version=2024-05-01" \ -H "Authorization: Bearer <Base64-access_token>"The documentation is somewhat misleading, because the only place where the
/languagespath is shown uses a different endpoint format that does not work as documented:https://<your-custom-domain>.cognitiveservices.azure.com/languages?api-version=3.0I consistently received errors when trying to call the API exactly as described here: https://learn.microsoft.com/en-us/azure/ai-services/translator/text-translation/reference/v3/languages
In the end, I had to adapt the request format to use the custom domain with the
/translator/text/v3.0/languagespath.
Se connecter pour commenter
Se connecter pour répondre