Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Azure Translator is updated continuously, and service changes can affect feature behavior and capability limits. This article tracks known issues in Azure Translator, describes their impact, and provides mitigation or resolution guidance. Before you submit a support request, review the list to determine whether your issue is a known condition and to identify the recommended remediation.
Service-level outages and notifications
Azure status and Azure Service Health publish service-level outages and regional disruptions. Use these services to validate current impact, track incident lifecycle updates, and configure proactive notifications for your subscriptions and resources.
- Service-level outages: Azure status page.
- Outage notifications and alerts: Azure Service Health Portal.
Text translation current known issues
The following table lists active, service-confirmed issues in the Azure Translator text translation feature. Each entry includes the issue category, observed behavior, documented workaround, and initial publish date.
| Issue ID | Category / Feature Area | Title | Description | Workaround | Issues publish date |
|---|---|---|---|---|---|
1006 |
Content | Translating sentences with mixed language text | The Text translation API doesn't support translating sentences that contain mixed language input. As a result, translations can be incorrect or incomplete when a single sentence includes multiple languages. | Specify the intended source language, remove the mixed-language sentence, or split the text into single-language segments. | February 5, 2025 |
1004 |
Model | Preserving context and pronouns | Some translation models don't handle pronouns well; especially third-person pronouns. This issue is due to an inherent problem with sentence-level training and inference where context isn't preserved. We're actively working to shift all our models to document-level training and inference to preserve the context. | Currently, there's no direct workaround. Users should manually review and adjust pronoun usage as needed. | February 5, 2025 |
Document translation current known issues
The following table lists active, service-confirmed issues in the Azure Translator document translation feature, including issue category, observed behavior, documented workaround, initial publish date, and scenarios involving complex or mixed-content inputs.
| Issue ID | Category | Title | Description | Workaround | Publication date |
|---|---|---|---|---|---|
| 3010 | Content | Translating documents containing visible watermarks or seals | Documents with visible watermarks or seals can significantly hinder the translation process, as the watermarks may overlap with the text, making it difficult for the models to accurately recognize and process the content. This issue can result in the document remaining untranslated or only partially translated. | For optimal translation results, use clean, watermark-free documents. Files without visible watermarks or seals translate accurately and as expected. | May 21, 2025 |
| 3009 | Formatting | Translating documents containing borderless charts and tables | Complex tables and charts can present significant challenges during translation, especially when they're large and intricate. Charts and tables with mixed horizontal and vertical text, varying cell sizes, or grid structures that are borderless, are difficult to format accurately. These types of tables may require added processing to ensure precision without compromising overall performance. | To improve the quality of translation output, consider recreating documents using bordered tables and charts rather than borderless ones. | April 1, 2025 |
| 3008 | File types | Translating complex documents | Translating documents with thousands of intricate pages can be challenging. These documents often include images, embedded text within images, and manually typed text. As a result, the batch translation request can encounter failures during the extraction, translation, and reassembly processes. | Split the large document into smaller sections (for example, divide a 1000-page file into approximately 10 files of 100 pages each) and submit them individually for the best results. | February 5, 2025 |
| 3007 | Content | Translating documents with mixed source languages | In some cases, document translation doesn't translate source documents with multiple languages leading to incorrect or incomplete results. For example, a sentence that contains more than one language. | To ensure that the desired language is translated to the target language, specify the intended source language. Alternatively, remove the mixed-language sentence, or split the text into segments containing only one language. | February 5, 2025 |
| 3001 | Formatting | Formatting of mathematical expressions | In some cases, translated documents don't fully retain the formatting of mathematical expressions. Superscript and subscript numbers can be reformatted incorrectly, leading to discrepancies between expected and actual output. | Currently, there's no direct workaround. Users should manually adjust the formatting of mathematical expressions as needed. | February 5, 2025 |