Custom translator fails

Søren Printz Christensen 20 Reputation points
2026-08-18T16:07:09.1566667+00:00

When running training I get this:

"Unable to create model

Your current Translator Text API or Cognitive Services subscription is not valid. Please verify in the Azure portal that your subscription still exists and your billing information is up to date, then retry.

"

Søren

Azure Translator in Foundry Tools

Answer accepted by question author
Thanmayi Godithi 11,825 Reputation points Microsoft External Staff Moderator
2026-08-18T16:58:59.9866667+00:00

Hi Søren Printz Christensen,

Before recreating the FSBDevTranslations workspace, I'd recommend a few checks first. This error typically indicates that Custom Translator cannot validate the Translator resource associated with the workspace, which can occur even when the Azure resource itself appears healthy.

1.Verify the Translator resource outside the portal

Test the Translator resource directly using a simple translation request:

curl -X POST "https://api.cognitive.microsofttranslator.com/translate?api-version=3.0&amp;to=de" </span>
-H "Ocp-Apim-Subscription-Key: <your-key>" </span>
-H "Ocp-Apim-Subscription-Region: <your-region>" </span>
-H "Content-Type: application/json" </span>
-d '[{"Text":"Hello"}]'

A successful response confirms that the Translator key and region are valid for API requests.

2.Review the Translator resource configuration

In Azure Portal, verify:

  • The Translator resource is active and provisioned successfully.
  • The Azure subscription is active and has no billing restrictions.
  • Any networking restrictions, firewalls, or private endpoint configurations are compatible with your Custom Translator scenario.

3.Check the pricing tier

Confirm the Translator resource is running on a supported tier. Per Microsoft documentation, the free tier has limitations, including a maximum training limit of 2,000,000 characters.

4.Validate the workspace association

Within the Custom Translator workspace, open Workspace Settings and verify that the linked Translator resource, region, and access key match the values shown under Keys and Endpoint in Azure Portal.

Reference documentation:

As discussed over the call, recreating the workspace and validating the workspace association helped resolve the issue.

Kindly let us know if the above helps or you need further assistance on this issue.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

1 additional answer

Sort by: Newest
  1. Søren Printz Christensen 20 Reputation points
    2026-08-18T16:22:09.5333333+00:00

    Thanks for the quick answer Jerald.

    I don'r see the gear icon:User's image

    The resource should be okay.

    Was this answer helpful?

    0 comments No 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.