cognitive service 404 error

Thybris Vandenbroucke 0 Reputation points
2023-10-17T16:30:08.51+00:00

I have a student membership and experience a 404 error when I try to connect to my cognitive service API. Is there a reason why I can not do a simple get request while my endpoint and keys are given correctly to my application?

Azure AI services
Azure AI services
A group of Azure services, SDKs, and APIs designed to make apps more intelligent, engaging, and discoverable.
2,583 questions
{count} votes

2 answers

Sort by: Most helpful
  1. VasaviLankipalle-MSFT 15,836 Reputation points
    2023-10-27T00:35:53.94+00:00

    Hello @Thybris Vandenbroucke , thanks for confirming. I would suggest you check all the necessary permissions to access the Face API. Try checking the roles for your resource (Azure portal->Resource->Access control) like contributor, role-based access control (RBAC), Cognitive Services Contributor/Face Recognizer for the resource. Please go through this documentation: https://video2.skills-academy.com/en-us/azure/ai-services/translator/document-translation/how-to-guides/create-use-managed-identities

    Also make sure you have active subscription, resource and its region. Try to regenerate the keys in the Azure portal under your resource and add latest key to see if that helps.

    As we know we have Limited Access features of Face API based on eligibility and usage criteria in order to support our Responsible AI principles. You do not need to submit this form if you are using Facial Detection capabilities of these services. 

    However, please note that detection of emotion, gender, age, smile, facial hair, hair, and makeup attributes is no longer available to new customers. Existing customers have until June 30, 2023, to discontinue use of these attributes before they are retired.   https://video2.skills-academy.com/en-us/azure/ai-services/computer-vision/how-to/identity-detect-faces

    I hope this helps.

    Regards,
    Vasavi

    0 comments No comments

  2. Yakov Keselman 25 Reputation points
    2024-06-18T19:30:33.7066667+00:00

    When I moved my endpoint to US-East, the problem fixed itself.

    0 comments No comments