Custom Translator – Unable to unpublish/update regions due to duplicate "Published" state on same Category ID

Spencer Lin 林彥穎 0 Reputation points
2026-08-11T03:06:18.5333333+00:00

Service: Azure AI Translator – Custom Translator

Severity: Medium (billing impact – duplicate model hosting charges)

Category ID affected: 299410be-c654-4d95-8a50-b0d29026f2f8-FINANCE

Region: North America

Summary: Within a single Custom Translator project, two models are simultaneously showing a "Published" status to the same region (North America) under the same Category ID. All self-service actions to remove the older model (Unpublish, Update regions) fail with the same error message, regardless of which model is targeted or which page in the portal the action is initiated from.

Affected models:

User's image **
Steps to reproduce:**

  1. Navigate to Model details for EAPIF_en_zhHant → select Unpublish.
    • Result: Dialog "Unable to unpublish – There is already a published model within this project. When swapping published models within a project, the new model must be published to the same regions as the existing model."
    1. Navigate to Publish model list page → select EAPIF_en_zhHant (older model) → click Unpublish.
      • Result: Same error dialog as above.
      1. Same page → select EAPIF_en_zhHant → click Update regions → attempt to remove North America.
        • Result: Dialog "Unable to update published regions" with the identical error text.
        1. Select EAPIF_en_zhHant_v2 (the newer, intended-to-remain model) → Publish button is greyed out/disabled (expected, since it's already published).

Expected behavior: Per official documentation, only one model per project should be published to a given region at a time, and the swap mechanism ("select the replacement model, then Publish") is the documented method for replacing a published model. In this case, however, both models already show as Published to the same region simultaneously — an inconsistent state that the portal did not prevent, and that none of the standard actions (Unpublish, Update regions) can resolve.

Actual behavior: Both models remain stuck in "Published" status to North America under the same Category ID. No self-service action in the portal is able to remove the older model's published status.

Business impact: Per Custom Translator pricing, model hosting is billed as a flat, non-prorated fee per hosted model per region per billing period. With two models currently showing as hosted/published to the same region, this results in duplicate hosting charges for a model (EAPIF_en_zhHant) that is no longer needed and should have been fully unpublished.

Requested action: Please manually clear the published/hosted state of EAPIF_en_zhHant in North America from the backend, so that only EAPIF_en_zhHant_v2 remains published under Category ID 299410be-c654-4d95-8a50-b0d29026f2f8-FINANCE, and confirm that hosting billing reflects only one hosted model going forward.

Azure Translator in Foundry Tools
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Thanmayi Godithi 11,825 Reputation points Microsoft External Staff Moderator
    2026-09-01T16:30:48.7+00:00

    Hi Spencer Lin 林彥穎 ,

    Thank you for bringing this issue to our attention.

    Based on the behaviour described, the project appears to be in an inconsistent publication state where two models are simultaneously marked as Published to the same region under a single Category ID. Since the portal is returning the same validation error for both Unpublish and Update regions operations, and the newer model already shows as published, this is not something that can be corrected through the available self-service actions.

    To investigate further, could you please provide the following details via a private message :

    • Azure Subscription ID
    • Custom Translator Workspace/Project name
    • Category ID: 299410be-c654-4d95-8a50-b0d29026f2f8-FINANCE
    • A screenshot of the published models page showing both models in the Published state
    • Approximate time when the duplicate published state was first observed

    Once we have these details, we can engage the engineering team to validate the backend publication records and determine whether manual remediation is required.

    Regarding billing concerns, we understand the impact of multiple models appearing as hosted in the same region. The support team can review this as part of the investigation and provide guidance based on the findings.

    We look forward to your update.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.