How do I fix a 403 "This request is not authorized to perform this operation using this permission." error when accessing a newly created Language Studio project?

Pavel Gutin 80 Reputation points
2024-08-17T21:31:13.9+00:00

I am trying to work my way through the Extract Custom Entities exercise. I am running into an issue when trying to access a newly created project. I can get though the creation steps, but when I click on the project, I get a 403 error that states "This request is not authorized to perform this operation using this permission."

Here are the things that I already tried after some troubleshooting:

  1. I made sure that I am creating the project with the same storage account. (I only have a single one)
  2. I checked to make sure that my storage account has "Blob anonymous access" Enabled User's image
  3. I checked that CORS is properly set
    User's image
  4. I checked that container has the right access level
    User's image
  5. I am out of ideas of what to try next.
Azure AI Language
Azure AI Language
An Azure service that provides natural language capabilities including sentiment analysis, entity extraction, and automated question answering.
479 questions
Azure AI services
Azure AI services
A group of Azure services, SDKs, and APIs designed to make apps more intelligent, engaging, and discoverable.
3,312 questions
{count} votes

Accepted answer
  1. YutongTie-MSFT 53,941 Reputation points
    2024-08-21T17:44:13.4566667+00:00

    Hello everyone,

    Thanks for reaching out to us, there is some change just announced today for this behavior.

    Please add the 'Storage Blob Data Contributor' role, it should resolve this issue.

    We will add a notification in the doc so that avoiding this error anymore as below -

    User's image

    Please go to Azure Portal, go to the storage account you connected to your Azure Language resource, on the left panel, select Access Control, click the Add button and add the role as the second screenshot.

    User's image

    Add 'storage blob data contributor' role for the user on the storage account even though you are the owner of the storage account.

    User's image

    Please have a try and see how it works, the document team is working on adding more details so that there is less misunderstanding.

    Regards,

    Yutong

    -Please kindly accept the answer if you feel helpful to support the community, thanks a lot.

    9 people found this answer helpful.

6 additional answers

Sort by: Most helpful
  1. Sina Atabaki 0 Reputation points
    2024-10-27T17:15:52.5266667+00:00

    For me it worked, after setting the CORS settings and giving the 'storage blob data contributor' Role to your own user as mentioned above

    0 comments No comments

  2. Tanishq Sakhare 0 Reputation points
    2025-04-03T10:24:09.2133333+00:00

    Hey folks,

    There are some specific changes, according to this particular steps you can follow now...

    -------> If you encounter a 403 Forbidden error when trying to access a newly created Language Studio project, it usually means that your account lacks the necessary permissions to perform the requested operation.

    Below are some potential fixes based on common causes:

    1. Check Azure Role-Based Access Control (RBAC) Permissions

    Ensure that your Azure account has the correct role assigned to access the Cognitive Services resource backing your Language Studio project.

    Go to the Azure portalYour Cognitive Services resourceAccess control (IAM)Check role assignments.

    Assign at least the Cognitive Services Contributor or Owner role if you lack sufficient permissions.

    2. Verify Subscription and Resource Access

    Confirm that your Azure subscription is active and that your Cognitive Services resource is properly created and assigned to the correct Resource Group.

    If you have multiple Azure Directories, ensure you are signed in to the correct directory that contains the resource.

    3. Ensure API Permissions in Microsoft Entra ID (formerly Azure AD)

    If your project involves authentication using Microsoft Entra ID, make sure your user or service principal has been granted the necessary API permissions.

    Navigate to Azure portalMicrosoft Entra IDEnterprise applicationsFind the app associated with your projectCheck API permissions.

    If missing, add Cognitive Services User or relevant permissions and click "Grant admin consent."

    4. Regenerate API Keys and Endpoint URL

    Sometimes, authentication errors occur due to incorrect or expired API keys.

    Go to Azure portalCognitive Services resourceKeys and EndpointCopy a new key and update your connection settings in Language Studio.

    5. Try Using a Different Role or Account

    If you are working in a corporate or enterprise environment, your access may be restricted by company policies.

    Try logging in with a different Azure account that has higher privileges or contact your Azure administrator to request access.

    6. Check If the Region Supports Your Service

    Some Cognitive Services Language features are not available in all Azure regions.

    Check the Azure region availability for your selected Language Studio service and migrate the resource to a supported region if necessary.

    7. Use the Correct Endpoint URL Format

    Ensure you are using the correct endpoint URL format when accessing the Language Studio API. The URL should match the region where the resource is deployed, such as:

    https://<your-resource-name>.cognitiveservices.azure.com/
    

    If using a REST API or SDK, confirm that your endpoint URL is correctly formatted and matches your resource settings in Azure.

    💡 Final Steps

    If none of the above solutions work:

    Check Azure Logs: Go to Azure portalMonitorActivity Log for any failed authentication attempts.

    Consult Microsoft Docs: Review Azure Cognitive Services documentation for any service-specific access requirements.

    Contact Microsoft Support: If the issue persists, open a support ticket in the Azure portal for further assistance.

    By following these steps, you should be able to resolve the 403 error and successfully access your Language Studio project!

    Try this and acknowledge me if you've satisfied with this answers!

    Regards,

    Tanishq S.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.