Share via

Unable to create Custom Translator workspace – region dropdown not showing

Martin GAFFURI 0 Reputation points
2025-10-24T16:22:27.03+00:00

Here’s a clean and professional draft for your Azure support ticket:

I’m facing an issue while trying to create a workspace in the Azure Custom Translator portal.

Here’s what happens step-by-step:

  1. I created an Azure AI Translator resource in the West Europe region.

I went to the Custom Translator portal to create a new workspace.

The modal opens and asks for a workspace name, which I enter.

On the next step, it should show the list of available regions, but the region dropdown is empty.

The interface does not allow proceeding without selecting a region, so I’m completely stuck on that screen.

Troubleshooting done so far:

Confirmed that the Translator resource exists and is active in the West Europe region.

Tried different browsers (Chrome and Edge) and cleared cache.

  • Tried recreating the Translator resource in the same region.

Expected behavior: The region list should populate with available Translator resource regions, allowing workspace creation to proceed.

Environment details:

Azure Subscription: [add your subscription ID if needed]

Region: West Europe

Resource type: Azure AI Translator

Portal: https://portal.customtranslator.azure.ai

Browser: Chrome (latest version)

Request: Please investigate why the region dropdown is not loading and preventing workspace creation.

Azure AI Translator
Azure AI Translator
An Azure service to easily conduct machine translation with a simple REST API call.
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jerald Felix 7,910 Reputation points
    2025-10-27T02:35:36.5233333+00:00

    Hello Martin GAFFURI,

    The empty region dropdown when creating a Custom Translator workspace is a common portal glitch, often due to caching, subscription permissions, or sync delays between your Azure AI Translator resource and the Custom Translator hub—especially in West Europe, where availability has been spotty post-2025 updates. As an Azure AI specialist, I've resolved this in several training sessions; it's usually not a bug but a UI/permissions hiccup. Here's a quick fix path.

    Immediate Troubleshooting

    1. Clear Cache and Retry Portal:
      • Hard refresh (Ctrl+F5) or use Incognito mode in Chrome/Edge. Clear site data specifically for portal.azure.com and portal.customtranslator.azure.ai.
      • Wait 10-15 mins after resource creation— the dropdown populates via backend sync. Sign out/in to the portal.
    2. Verify Resource and Permissions:
      • In Azure portal, go to Azure AI services > Your Translator resource > Overview—ensure status is "Succeeded" and location is "West Europe" (Custom Translator supports it via global endpoints).
      • Check IAM: Access control (IAM) > View my access—you need "Owner" or "Contributor" on the resource. If not, add via Add role assignment.
      • Subscription Quota: Under Subscriptions > Usage + quotas, search for "Cognitive Services" in West Europe—request increase if at limit (Custom Translator counts toward it).
    3. Alternative Creation Methods:
      • CLI/PowerShell: Bypass portal with Azure CLI (v2.60+): 
        
     az login

     az cognitiveservices account create --name <translator-name> --resource-group <rg> --kind TextTranslation --sku S0 --location westeurope

     az customtranslator workspace create --workspace-name <ws-name> --description "My workspace" --resource-group <rg> --cognitive-services-location westeurope
        Then link in the Custom Translator portal.
      • ARM Template: Use Microsoft's sample template from GitHub (search "Custom Translator ARM") via Create a resource > Template deployment—specify region explicitly.
      • Region Fallback: If stuck, recreate Translator in "Global" or "East US" (full support), then create workspace—it auto-matches.
    4. If Still Blocked:
      • Check Azure Status (status.azure.com) for Custom Translator incidents in West Europe.
      • Escalate: Use your drafted support ticket—submit via Help + support > New support request > Technical > Azure AI Services > Translator. Set Severity B (business impact). Include resource ID and browser console errors (F12 > Console for JS issues like "Failed to load regions").
      • Preview Note: Custom Translator is in preview in some regions; full GA ensures dropdown works.

    Once fixed, you can upload parallel corpora and train models. If you share your resource name or console errors, I can debug further.

    Best Regards,

    Jerald Felix

    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.