Forum Discussion

MWLjdb's avatar
MWLjdb
Brass Contributor
Nov 10, 2021
Solved

API to Azure Purview

I can successfully generate the bearer token via API to our purview instance, but any time I try any other API call, I get the following.  This includes using the "Try it" button from the API documen...
  • drewbios's avatar
    drewbios
    Aug 18, 2022
    Difference for me using Piethein's excellent instructions was the change of resource from 'https://management.core.windows.net/' (getting that "Invalid token audience" error) to 'https://purview.azure.net'.
drewbios's avatar
drewbios
Copper Contributor
Aug 18, 2022
Difference for me using Piethein's excellent instructions was the change of resource from 'https://management.core.windows.net/' (getting that "Invalid token audience" error) to 'https://purview.azure.net'.
drewbios's avatar
drewbios
Copper Contributor
Aug 18, 2022

After assigning the recommended roles (Data Curator, Data Source Administrator, Collection Admin - I also added Data Reader) to the service principal, I get different errors using the different configurations.

  • Using the token with resource = 'https://management.core.windows.net/', the error  is Unauthenticated, "Invalid token audience provided..."
  • Using the token with resource = 'https://purview.azure.net' (as suggested by Piethein), the error is Unauthorized, "Not authorized to access account". 

So similar behaviour to other posters...

  • ahazel's avatar
    ahazel
    Icon for Microsoft rankMicrosoft
    Nov 04, 2022

    drewbios Did you by chance put your grant_type, client_id, client_secret_and resource in the params instead of the body of your authentication call? It should be in the body. Screenshots from my Postman request below.