Hello Liel Serfaty
Good day.
Yes, you can use your Custom Translator model (category ID) with the Azure Document Translation Python SDK.
Common pitfalls & checks
- Region mismatch\ Your Custom Translator model and your Translator resource must be in the same Azure region. A mismatch typically returns a 400/BadRequest with messaging like “unknown category.”
- Resource type\ Use a Translator resource (single-service). A generic “Cognitive Services (multi-service)” key won’t work with Document Translation.
- Model status\ Ensure the Custom Translator system is Deployed and the Category ID is from that deployment (not the project ID).
- Language pair alignment\ The custom system must support the source→target pair you are requesting (e.g.,
es->en). - Permissions to blobs\ The SAS on
source_urlmust grant Read; on eachtarget_url, grant Write (and typically Create, Add, List) for the SDK to write outputs. - SDK property name\ In Python it’s
category_idonTranslationTarget. In some REST samples it’scategory. If you setcategoryin Python, it will be ignored—usecategory_id.
Thank you.