Unauthorized Error When Fetching Relationship from Purview API

Khushboo Shah 0

I encounter an "Unauthorized" error message when fetching a relationship from the Purview API. The specific error response is:

Endpoint: https://{purview account}/datamap/api/atlas/v2/relationship/guid/{assetGUID}?extendedInfo=false

{
  "error": {
    "code": "Unauthorized",
    "message": "Not authorized to access account"
  }
}

I have already checked my API credentials and they seem to be correct. Has anyone else encountered this issue, and if so, what steps did you take to resolve it? Any insights or suggestions would be greatly appreciated.

PRADEEPCHEEKATLA-MSFT 77,751 Reputation points Microsoft Employee

2024-04-12T08:30:42.04+00:00
@Khushboo Shah - Thanks for the question and using MS platform.

It seems like you are encountering an "Unauthorized" error message when fetching a relationship from the Purview API. This error message suggests that you are not authorized to access the account.

To resolve this issue, you can try the following steps:

Check if you have the correct permissions to access the account. You can check this by going to the Azure portal and navigating to the Purview account. From there, click on "Access control (IAM)" and check if your account has the necessary permissions.

Check if you have the correct API credentials. Make sure that you are using the correct credentials to access the Purview API. You can check this by going to the Azure portal and navigating to the Purview account. From there, click on "Access keys" and check if you are using the correct primary or secondary key.

Check if you are using the correct endpoint. Make sure that you are using the correct endpoint to access the Purview API. You can check this by going to the Azure portal and navigating to the Purview account. From there, click on "Properties" and check if you are using the correct endpoint.

For more details, refer to Access control inside the Microsoft Purview governance portal and checkout MS Q&A thread: Unauthorized: Not authorized to access Purview account using API requests addressing similar issue.

If none of these steps work, please provide more information about your issue, such as the steps you took before encountering the error message, and any additional error messages or logs that you may have.

I hope this helps! Let me know if you have any other questions.
Khushboo Shah 0 Reputation points

2024-04-12T10:38:58.7733333+00:00

Hi @PRADEEPCHEEKATLA-MSFT

Thanks for replying back

I checked my permissions, I have owner-level permissions, have entered the correct API credentials, and can generate token value. I am following the endpoint from the documentation itself.
I used the below solution for permissions and API-related issues but still received the same error message.
https://learn.microsoft.com/en-us/answers/questions/998548/unauthorized-error-using-purview-api-not-authorize
PRADEEPCHEEKATLA-MSFT 77,751 Reputation points Microsoft Employee

2024-04-15T05:29:15.82+00:00

@Khushboo Shah - If you have already checked your permissions, API credentials, and endpoint and are still encountering the "Unauthorized" error message when fetching a relationship from the Purview API, there could be a few other reasons why you are experiencing this issue.

One possible reason could be that there is an issue with the authentication token that you are using to access the Purview API. You can try generating a new authentication token and see if that resolves the issue.

Another possible reason could be that there is an issue with the asset GUID that you are using to fetch the relationship. Make sure that you are using the correct asset GUID and that it is valid.

If neither of these solutions work, you can open a support ticket for further assistance. They may be able to provide additional insights and help you resolve the issue.

I hope this helps! Let me know if you have any other questions.
PRADEEPCHEEKATLA-MSFT 77,751 Reputation points Microsoft Employee

2024-04-22T03:44:36.44+00:00

@Khushboo Shah - We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.