Azure Document Translation Not Available – Only Text Translation Resource Created

Hi @SriLakshmi C
Thanks for the clarification! It is really helpful and now I get it. Got a quick question, on your prerequisites that you shared, it is the approach where we use language studio.

In my case, I am using the end api for doc translation in python. Will it be the same condition and approach in this case?

Hi @schoo,

Yes, the same prerequisites and setup conditions apply when using the Azure Document Translation API via Python as they do when using Azure Language Studio. Whether you interact with the service through the portal, REST API, or the Python SDK (azure-ai-translation-document), the underlying requirements remain the same.

Ensure that you are using a single-service Translator resource, as Document Translation is not supported on multi-service Azure AI resources.

The Translator resource must be created in a region that supports Document Translation, such as East US, East US 2, West US 2, North Europe, or West Europe East Asia is not supported even when accessing the API directly.

The pricing tier must be S1 (Standard) or D3 (Volume Discount), as the Free (F0) tier does not support Document Translation. The Translator resource also needs to have a system-assigned managed identity enabled, and that identity must be granted the "Storage Blob Data Contributor" role on the Azure Blob Storage account that stores the source and translated documents.

Document Translation works by reading documents from a source blob container and writing translated output to a target container, which means you must supply valid SAS URLs for these containers in your API request.

Using the Python SDK does not change any of these requirements it is simply a wrapper around the REST API. Therefore, if your current Translator resource is in East Asia, you’ll need to recreate it in a supported region with the appropriate tier and configurations to ensure that your Python-based translation requests succeed.

please refer this Get started: Document translation client libraries (programming-language-python)

Use REST APIs programmatically.If this answers your query, please do click Accept Answer and Yes for was this answer helpful.

Thank you!

Hi @schoo,

Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Thank you!

Thank you so much for your continued support @SriLakshmi C ! Thanks to your help, I was able to successfully create the Translator resource, configure the storage account with two containers, assign the Storage Blob Data Contributor role, and connect to the API — receiving both 202 and 200 status codes.

However, I'm still getting a ValidationFailed status when checking the batch translation status. This is confusing because I believe all the required steps have been completed and the conditions are met.

Just in case, I also tested the same setup using Language Studio, but strangely, it gives me an error saying the user must have the Storage Blob Data Contributor role — which I have already assigned to the Translator resource.

I've attached screenshots of the error and my current setup. I would really appreciate your help with this final step.Thank you again!

Hi schoo,

Thank you for the detailed update and screenshots it’s great to hear that you’ve successfully configured the Translator resource and are receiving valid responses (202/200) from the API. However, the ValidationFailed status and the Language Studio error indicating missing Storage Blob Data Contributor access suggest a likely issue with the identity and permissions propagation or the SAS URL formatting.

Here are a few key points to check and next steps:

After assigning the Storage Blob Data Contributor role to the system-assigned managed identity of the Translator resource, it can take up to 10–15 minutes for the permission to fully propagate across Azure services. During this time, role-based access checks may fail. If you haven't already, please wait a few minutes and retry the operation.

Make sure the role is assigned specifically to the Translator resource’s managed identity, not to your user account or the storage account itself.

You can verify this by:

Going to the Storage Account → Access Control (IAM) → Role Assignments

Ensuring the Translator resource's identity name appears with the Storage Blob Data Contributor role

Ensure the SAS tokens provided for both the source and target containers meet the following:

Point to the container, not just the storage account or individual file

Include correct permissions: rwl (read, write, list) are typically required

Have valid expiry dates

Also, make sure that the SAS URL does not contain spaces or line breaks, as that can lead to validation errors.

While not strictly required, placing the Blob Storage account in the same region as your Translator resource helps minimize latency and potential access inconsistencies.

You can try a basic request with a single document and simple input/output structure to isolate the issue further. This helps rule out problems due to document formats, file sizes, or deeply nested folders.

I hope you understand, do let me know if you have further queries.

If this answers your query, please do click Accept Answer and Yes for was this answer helpful.

Thank you!