Share via

Atlas endpoint "Resource not found" via Purview API

Mollie Chapman 5 Reputation points
2023-07-12T12:58:50.11+00:00

Following this guide https://learn.microsoft.com/en-us/azure/purview/tutorial-atlas-2-2-apis I am trying to send any request to the atlas endpoint of my purview account (i.e. POST {{endpoint}}/api/atlas/v2/types/typedefs) or even just accessing the endpoint directly but the only response I get is: {"error":{"code":"ResourceNotFound","message":"Resource not found"}}.

I presume it is a problem with permissions but I have admin access to the subscription, resource group, purview account as well as all of the roles in the purview catalog (Collection admins_,_ Data source admins_,_ Data curators_,_ Data readers_,_ Insights readers_,_ Policy authors_,_ Workflow admins).

Can anyone suggest what could be configured incorrectly to not allow me to access the atlas endpoint?

Microsoft Security | Microsoft Purview

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Mollie Chapman 5 Reputation points
    2023-07-18T13:00:16.1933333+00:00

    I think the problem that I had was the way that I was using the access token in Postman - it worked when I did the below
    User's image

    1 person found this answer helpful.
    0 comments
  2. KranthiPakala-MSFT 46,642 Reputation points Microsoft Employee Moderator
    2023-07-12T21:29:01.18+00:00

    @Mollie Chapman Thanks for using Microsoft Q&A forum and posting your query.

    As per your statement looks like your user account has admin access to the subscription, RG, purview resource including other purview catalog permissions roles. But it doesn't state if your REST API client is using your credentials or a Service principal.

    Hence, I recommend going through this document to ensure you have covered all the prerequisite to trigger Purview Atlas 2.2 APIs using your REST API Client.

    As per the public document, it states that for a REST API client to access the catalog, the client must have a service principal (application), and an identity that the catalog recognizes and is configured to trust. When you make REST API calls to the catalog, they use the service principal's identity.

    Customers who have used existing service principals (application IDs) have had a high rate of failure. Therefore, we recommend creating a new service principal for calling APIs.

    Once after creating the service principal, please ensure to grant API permission to access Purview APIs as shown below:

    User's image

    Then the next step will be to assign the data plane roles of your purview account to the service principal created in the previous step at the root collection level. This is clearly documented here: Microsoft Purview - Set up authentication using service principal

    User's image

    If you are not sure what exact permissions is needed, the I highly recommend going through this document to understand the Purview permissions and their scope. Microsoft Purview - Who should be assigned to what role?

    Chart showing Microsoft Purview governance portal roles

    In addition , please double check if the endpoint used in the API URL is correct .

    Hope this info helps. Let us know how it goes.

    Thank you

    0 comments
  3. Cayir Aydar, Aysegul 0 Reputation points
    2023-07-18T09:27:32.3066667+00:00

    @Mollie Chapman , could you solve you problem? I have a same problem.

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.