Azure Purview Api returning 404

Question

Hi,

I am using below microsoft learn page to query some data using rest api calls, I tried to fetch glossary list by clicking try it button. I have an azure purview resource created in my subscription with data sources and the glossary exist.

MS learn page - https://learn.microsoft.com/en-us/rest/api/purview/datamapdataplane/glossary/list?view=rest-purview-datamapdataplane-2023-09-01&tabs=HTTP&tryIt=true&source=docs

API I am trying - GET {endpoint}/datamap/api/atlas/v2/glossary

whenever I login using my Azure account to which I have below access but I am still getting response code 404

I do not want to use service prinicipal want to use an AD user.

I have bleow permission on Purview collection

Role-NHA-Dev-Purview-Collection-Admin , Role-NHA-Dev-Purview-Data-Source-Admin, Role-NHA-Dev-Purview-Data-Reader, Role-NHA-Dev-Purview-Data-Curator

can you please guide me what wrong I am doing here ? I have added screenshots here for reference

Answer 1

@Vinod G I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer.

Issue: I am using below microsoft learn page to query some data using rest api calls, I tried to fetch glossary list by clicking try it button. I have an azure purview resource created in my subscription with data sources and the glossary exist.

MS learn page - https://learn.microsoft.com/en-us/rest/api/purview/datamapdataplane/glossary/list?view=rest-purview-datamapdataplane-2023-09-01&tabs=HTTP&tryIt=true&source=docs

API I am trying - GET {endpoint}/datamap/api/atlas/v2/glossary

whenever I login using my Azure account to which I have below access but I am still getting response code 404

I do not want to use service prinicipal want to use an AD user.

I have bleow permission on Purview collection

Role-NHA-Dev-Purview-Collection-Admin , Role-NHA-Dev-Purview-Data-Source-Admin, Role-NHA-Dev-Purview-Data-Reader, Role-NHA-Dev-Purview-Data-Curator

Resolution: Resolved by @Vinod G

I found that somehow in MS learn site the request sent were not getting response so instead I wrote Azure powershell task in yaml pipeline and generated the token for my managed identity. The same token I have used in bruno for testing Purview API and what I found is that it worked..!!!!

The managed identity should have necessary permission to work.

• Purview-Collection-Admin
• Purview-Data-Source-Admin
• Purview-Data-Reader
• Purview-Data-Curator

If you have any other questions or are still running into more issues, please let me know. Thank you again for your time and patience throughout this issue.

Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.

Answer 2

I found that somehow in MS learn site the request sent were not getting response so instead I wrote Azure powershell task in yaml pipeline and generated the token for my managed identity. The same token I have used in bruno for testing Purview API and what I found is that it worked..!!!!

The managed identity should have necessary permission to work.

• Purview-Collection-Admin
• Purview-Data-Source-Admin
• Purview-Data-Reader
• Purview-Data-Curator

Answer 3

I understand your preference for using an AD user instead of a service principal.

Upon reviewing the permissions you've shared, it seems that you have the necessary roles assigned for accessing the glossary within your Purview collection. However, the 404 error suggests there might be a configuration issue or a misalignment with the endpoint URL.

Permissions and Roles:

Ensure that your AD user has the necessary permissions to access the glossary.

• Role-NHA-Dev-Purview-Collection-Admin
• Role-NHA-Dev-Purview-Data-Source-Admin
• Role-NHA-Dev-Purview-Data-Reader
• Role-NHA-Dev-Purview-Data-Curator

Double-check that these roles cover the required actions for accessing the glossary.

Endpoint URL: Please ensure that the endpoint URL in your API call is correctly formed and points to your Azure Purview resource. You can refer to the Microsoft Learn page you mentioned for the correct format.

Network Configuration: Confirm that your Azure Purview account's network settings allow public access. If it's set to private, you may need to adjust the network configuration.

Authentication Method: Since you prefer using an AD user, ensure that you're authenticating with your Azure AD user credentials when making the REST API calls.

Direct API Call: Try making the API call directly using a tool like Postman or cURL, ensuring that the parameters and headers match your actual use case. This can help isolate any issues with the "Try it" button on the Microsoft Learn page.

Troubleshooting the 404 Error: Check the response headers and body when you receive the 404 error. This might provide additional clues about what's missing or incorrect.

For further reference and detailed documentation, you can also explore the Microsoft Azure Purview Documentation.

Answer 4

I found that somehow in MS learn site the request sent were not getting response so instead I wrote Azure powershell task in yaml pipeline and generated the token for my managed identity. The same token I have used in bruno for testing Purview API and what I found is that it worked..!!!!

The managed identity should have necessary permission to work.

• Purview-Collection-Admin
• Purview-Data-Source-Admin
• Purview-Data-Reader
• Purview-Data-Curator