How to resolve "Access denied due to invalid subscription key or wrong API endpoint" error in Azure OpenAI Playground

Matthias 20 Reputation points Microsoft Employee
2024-06-26T06:57:05.1966667+00:00

Hi,

I have set up an Azure OpenAI resource in my Azure account and created a deployment in the Azure OpenAI Playground. However, I am getting the error message "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" whenever I try to test the deployment in the Playground. I have checked that the subscription is active and the endpoint is correct. I have also tried removing and re-adding the resources and deployment several times, but the issue persists. Can you please suggest a solution or someone who can help me troubleshoot the issue? Thank you in advance,

Matthias

Azure OpenAI Service
Azure OpenAI Service
An Azure service that provides access to OpenAI’s GPT-3 models with enterprise capabilities.
2,521 questions
{count} votes

Accepted answer
  1. santoshkc 6,140 Reputation points Microsoft Vendor
    2024-06-26T08:54:12.5066667+00:00

    Hi @Matthias,

    Thank you for reaching out to Microsoft Q&A forum!

    The error message you’re seeing typically indicates that the subscription key you’re using for the Azure OpenAI is either incorrect or expired. It could also mean that the endpoint you’re using doesn’t match the one associated with your key. Here are a few things you can recheck to resolve the issue:

    • Recheck if the subscription key is still valid and has not expired.
    • Verify if the API endpoint URL is correct.
    • Check if you have the necessary permissions to access the resource.
    • Might this issue would be intermittent, it could be due to a temporary network or server issue. In this case, you can try again later to see if the issue has been resolved.
    • Try Clear browser cache and cookies and also try using a different browser.

    Hope this helps. And, if you have any further query do let us know.


    If this answers your query, do click Accept Answer and Yes for was this answer helpful.

    1 person found this answer helpful.
    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Matthias 20 Reputation points Microsoft Employee
    2024-06-28T06:52:59.5033333+00:00

    I guess it was due to a temporary network or server issue. I tried it some days later and since that it works with the original settings.

    Thanks for your assistance!

    0 comments No comments