Custom translator fails

Hello Søren Printz Christensen,

Greetings! Thanks for raising this question in the Q&A forum.

This error is a generic validation message that Custom Translator returns whenever it cannot confirm that the Translator (Cognitive Services) resource linked to your workspace is active and properly billed. It is not necessarily about your Azure subscription being cancelled. In most cases it comes down to one of three things: the linked Translator resource is on the F0 free tier (free tier does not support full model training once your data exceeds 2 million characters), the key stored in the Custom Translator workspace no longer matches the resource's current key (for example after a key regeneration), or the underlying Azure subscription has a billing problem such as an expired payment method or a subscription that has moved into a disabled or warned state.

Confirm the resource is active in the Azure portal. Go to portal.azure.com, open your Translator resource, and check that its status shows as Succeeded and not Disabled or Moved. Also check Subscriptions in the portal to make sure the parent subscription itself is Active, not Disabled, Expired, or Past Due.

Check the pricing tier. Open the Translator resource, select Pricing tier, and confirm it is set to S1 or higher (or a paid multi-service C2+ tier). If it shows F0 Free, this is very likely the cause, since free tier resources cannot be used to train a full custom model once your training data goes beyond the free character allowance.

Azure Portal > Translator resource > Pricing tier

Verify billing information on the subscription. Go to Cost Management + Billing in the portal and check that a valid payment method is on file and there are no outstanding invoices. A card expiry or failed payment is a common silent cause of this exact error message.

Re-sync the key in the Custom Translator portal. Sign in to Custom Translator, go to the gear icon in the top right, select Subscriptions, and check the key listed against your workspace's Translator resource.

Regenerate and re-add the key if needed. If the key shown does not match, go back to the Azure portal, open Keys and Endpoint on the Translator resource, regenerate Key1, wait about a minute, then copy the new key back into the Custom Translator Subscriptions page to refresh the association.

Azure Portal > Translator resource > Keys and Endpoint > Regenerate Key1

Recreate the workspace connection if the resource was deleted or recreated. If you deleted and recreated the Translator resource at any point (even with the same name), the workspace is still pointing at the old resource ID internally. In that case add the resource again as a new subscription entry in Custom Translator rather than reusing the old entry, then link your project to it.

Retry training once the tier and key are confirmed correct. If the same error persists after all of the above checks come back clean, open a support request from within the Azure portal on the Translator resource itself (Support + troubleshooting), since at that point it is worth having the backend team check the resource's provisioning state directly. Include the resource ID, region, and the exact timestamp of a failed training attempt.

If this answer helps you kindly accept the answer which will help others who have similar questions.

Best Regards,

Jerald Felix.

Hello Søren, thanks for the update.

The gear icon UI I described has been replaced in the current Custom Translator portal. The resource and key are now managed from within the workspace itself rather than a separate top level Subscriptions page, so here is the updated path.

Open your FSBDevTranslations workspace, then look for Workspace settings rather than a gear icon. This is usually reached from a menu option next to the workspace name or from the left navigation panel once you are inside the workspace, not from the top blue bar shown in your screenshot.

On the Workspace settings page, scroll to the section showing the linked Translator resource. This is where the current key and region tied to the workspace are displayed.

If the key shown there does not match the current key on the resource in the Azure portal, that mismatch is the likely cause of the training error, and you can update it from that same settings page rather than needing a separate Subscriptions screen.

If you still cannot find a settings option anywhere inside the workspace, it may be a permissions issue rather than a missing menu. Workspace settings are typically only visible to the account listed as Owner or Admin on the workspace. Check under the Manage users or Workspace access option to confirm which role your account has.

If this gets you to the right screen, let me know what key and region it shows so we can confirm it matches your resource.

Seeing this:

Maybe I should re-make the the workspace ?