How to fix "Access denied due to invalid subscription key or wrong API endpoint. Make sure to provide a valid key for an active subscription and use a correct regional API endpoint for your resource." issue while getting response

Question

Access denied due to invalid subscription key or wrong API endpoint. Make sure to provide a valid key for an active subscription and use a correct regional API endpoint for your resource.

Answer 1

Neha Parate Thanks for the question, Can you please add more details about the API call that you are making.

Make sure to provide a valid key for an active subscription and use a correct regional API endpoint for your resource.” typically occurs when the subscription key or the API endpoint provided is incorrect.

Here are some steps you can take to resolve this issue:

Check your subscription key: Make sure that the subscription key you’re using is valid and active. You can usually find this in your Azure portal or the platform where you obtained the API.

Check your API endpoint: Ensure that you’re using the correct API endpoint for your resource. The endpoint usually depends on the region where your resource is located.

1. Check your code: If you’re using code to access the API, make sure that the subscription key and the API endpoint are correctly implemented in your code

Answer 2

My team was getting the same error in Azure AI. Turns out that some services are automatically created in another region if they are not available in your region. Our entire Azure workloads are in Australia, but when we created the document intelligence service, it silently got created in East US.

So when you see the Endpoints & Keys section of your dashboard, it will show where you created it (e.g. Australia), but the actual AI service is running elsewhere (e.g. East US). This causes a key/region mismatch. The only place where we could see this contrasting location was in Cost Management > Cost Analysis > Resources.

We created a new resource in East US, and used the keys and endpoint from there, and it started working without any problem.

It could possibly be because AI services are not rolled out worldwide, so there is a higher probability of them ending up in a different region than where the keys and endpoint are defined. Also make sure that the key for the API Key is named Ocp-Apim-Subscription-Key, and not apiKey or api-key.

Answer 3

Make sure to use the correct endpoint. I was using vision.cognitiveservices.azure.com/ instead of face.cognitiveservices.azure.com/