Azure AI Translator not working after resource creation – Portal “Try it” fails and API returns 401001 across subscriptions

Hello @JiKoudela-2226 ,

Welcome to Microsoft Q&A .Thank you for reaching out to us.

Adding to the inputs provided by Jerald Felix, please check if the following helps-

The 401001 error (“credentials are missing or invalid”) generally indicates an authentication mismatch. In most scenarios, this is caused by incorrect endpoint usage or missing/incorrect headers. As a first level validation, the following checks are recommended:

1. Kindly ensure the correct endpoint is being used:
   • Global endpoint (commonly used): https://api.cognitive.microsofttranslator.com/...
2. Validate required authentication headers:
   • Ocp-Apim-Subscription-Key - required for all requests
   • Ocp-Apim-Subscription-Region - required for regional or multi-service resources and must exactly match the deployed region
3. Please confirm that:
   • The key belongs to the same resource being called
   • The region value is correct (for example: westeurope, francecentral)
   • No formatting issues or extra spaces exist in headers

There can also be a possibility that the resource provisioning or backend activation has not completed correctly, even though the resource shows as active. In such cases a backend validation might be needed, which can be done by reaching out to support for further assistance.

The following references might be helpful , please check them out

• Quickstart: translate text programmatically - Foundry Tools | Microsoft Learn
• Authentication and authorization in Azure Translator in Foundry Tools service - Foundry Tools | Microsoft Learn
• Translator V3.0 Reference - Foundry Tools | Microsoft Learn
• How to create an Azure support request - Azure portal | Microsoft Learn

Thank you

Hello JiKoudela-2226,

Greetings!

Thanks for raising this question in Q&A forum.

I completely understand how frustrating this must be two days on a blocking issue is no fun at all! You've done an excellent job documenting the problem. The 401001 error ("credentials are missing or invalid") combined with failure even inside the Azure Portal's own "Try it" tool strongly points to a backend provisioning or entitlement issue, not a mistake on your end. This sometimes happens when a new Translator resource is created but the backend activation doesn't fully propagate meaning the keys are issued but the service entitlement behind them isn't yet fully live.

Let's go through everything you can check and do right now:

Step 1: Confirm You Are Using the Right Endpoint for Your Resource Type

There are two types of Translator resources and they use different endpoints. This is one of the most common causes of 401001:

If you created a single-service Translator resource, use the resource-specific endpoint (not the global one):

https://<your-resource-name>.cognitiveservices.azure.com/translator/text/v3.0/translate

If you are using the global endpoint https://api.cognitive.microsofttranslator.com, you must also pass the Ocp-Apim-Subscription-Region header. Make sure the region value matches exactly what is shown in your resource — for example westeurope or francecentral (all lowercase, no spaces).

Step 2: Double-Check Your Request Headers in Postman

Make sure all three required headers are present and correct:

Ocp-Apim-Subscription-Key: <your-key1-or-key2>
Ocp-Apim-Subscription-Region: westeurope   ← must match your resource region exactly
Content-Type: application/json

Even a small typo or extra space in the region value will cause a 401001 error.

Step 3: Try the Resource-Specific Endpoint Instead of the Global One

Since the global endpoint is failing, switch to your resource's own endpoint in Postman:

POST https://<your-resource-name>.cognitiveservices.azure.com/translator/text/v3.0/translate?api-version=3.0&to=cs

With the same headers and body. This bypasses the global routing layer and goes directly to your resource.

Step 4: Regenerate Your Keys

Go to your Translator resource in the Azure Portal, navigate to Keys and Endpoint, and click Regenerate Key1. Wait about 60 seconds, then copy the fresh key and try again. Occasionally newly provisioned keys don't activate cleanly on the first generation.

Step 5: Check If a "Azure AI Services" Multi-Service Resource Works Instead

Try creating a new resource of type "Azure AI Services" (the multi-service kind) instead of the standalone Translator resource. This uses a different provisioning path and has been known to work when single-service Translator resources have activation issues.

Step 6: Check Your Subscription for Any Policy Restrictions

Go to Azure Portal → Subscriptions → Your Subscription → Resource Providers and confirm that Microsoft.CognitiveServices is listed as Registered. If it shows as "NotRegistered", click Register and wait a few minutes before trying again.

Step 7: Raise an Azure Support Ticket This Likely Needs Backend Investigation

Since this is failing across multiple subscriptions, regions, tiers, and even inside the Portal's own test tool, you've clearly ruled out all client-side issues. This needs Microsoft's backend team to look at the provisioning state of your resources. Please open an Azure Support Request with Severity B and include:

• Your resource names and resource IDs (from the Properties blade)
• The exact subscription IDs you tested with
• The timestamps of when resources were created
• Screenshots of the 401001 error from Postman and the Portal

The support team can inspect the internal entitlement state of your resources directly and resolve any backend activation issue quickly.

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

Best Regards,

Jerald Felix.