Microsoft Purview Data Quality API - Error 404

Question

Microsoft Purview Data Quality API - Error 404

Erwin van Ek 0

Hello,

We are trying to use the Microsoft Purview Data Quality API in our Purview account located in North Europe. However, every call to the versions endpoint returns 404 Not Found:

Code

GET https://<PURVIEW_ACCOUNT>.purview.azure.com/purviewdataquality/api/versions?api-version=2023-09-01-preview

We have verified that:

Authentication works (valid bearer token for https://purview.azure.net/.default)

Authorization works (our service principal has Data Map Reader and Data Map Writer roles)

Catalog and Atlas APIs are functioning normally

This suggests that the Data Quality backend is not yet deployed in North Europe.

Could anyone please confirm whether the Data Quality service has been rolled out to the North Europe region?

Thank you.

0 comments

2 answers

Your answer

Answer 1

Hi,

Thanks for the suggestion — I tested the alternative base path (/unifiedcatalog/dataQuality/api/...) as mentioned, but I’m still getting a 404 Not Found response.

Here’s what I’ve validated so far:

The Purview account endpoint (https://<account>.purview.azure.com) is working correctly (e.g. Atlas/catalog APIs return valid responses).
Authentication is working (tested with a manually acquired bearer token, not using the “Try it” feature).
I tested both documented Data Quality API paths:
- /purviewdataquality/api/...
  - /unifiedcatalog/dataQuality/api/...
  - I also tested directly from Microsoft Learn using my own token — same result.
  - Both GET Rules and Create Rules endpoints consistently return 404.
  - The same data assets and rules are visible and accessible in the Purview UI.

Given this, it seems unlikely to be:

an authentication issue
an incorrect base endpoint
or a malformed request

My current assumption is that this may be related to one of the following:

The Data Quality API (especially for Unified Catalog) is not fully exposed in my tenant yet
There is a regional rollout limitation
The Purview UI is using internal backend APIs that are not (yet) publicly available

Could someone from Microsoft confirm:

whether the Data Quality REST APIs are fully supported for Unified Catalog assets in all regions?
and whether there are any prerequisites (feature flags, tenant configuration, SKU, etc.) required to use these endpoints?

Thanks in advance.Hi,

Thanks for the suggestion — I tested the alternative base path (/unifiedcatalog/dataQuality/api/...) as mentioned, but I’m still getting a 404 Not Found response.

Here’s what I’ve validated so far:

The Purview account endpoint (https://<account>.purview.azure.com) is working correctly (e.g. Atlas/catalog APIs return valid responses).
Authentication is working (tested with a manually acquired bearer token, not using the “Try it” feature).
I tested both documented Data Quality API paths:
- /purviewdataquality/api/...
  - /unifiedcatalog/dataQuality/api/...
  - I also tested directly from Microsoft Learn using my own token — same result.
  - Both GET Rules and Create Rules endpoints consistently return 404.
  - The same data assets and rules are visible and accessible in the Purview UI.

Given this, it seems unlikely to be:

an authentication issue
an incorrect base endpoint
or a malformed request

My current assumption is that this may be related to one of the following:

The Data Quality API (especially for Unified Catalog) is not fully exposed in my tenant yet
There is a regional rollout limitation
The Purview UI is using internal backend APIs that are not (yet) publicly available

Could someone from Microsoft confirm:

whether the Data Quality REST APIs are fully supported for Unified Catalog assets in all regions?
and whether there are any prerequisites (feature flags, tenant configuration, SKU, etc.) required to use these endpoints?

Thanks in advance.

Pilladi Padma Sai Manisha 10,110 Reputation points Microsoft External Staff Moderator

2026-04-21T18:19:43.1033333+00:00

Hi Erwin van Ek,
Thanks for the detailed follow-up, this really helps, and it’s clear you’ve already ruled out the common causes like authentication, endpoint format, and token issues.

Given everything you’ve validated, your assumption is most likely correct. The Data Quality APIs for Unified Catalog are still in preview and are not fully rolled out across all regions or tenants yet. In this scenario, a 404 typically means the backend route itself isn’t available rather than there being an issue with your request.

The behavior you’re seeing also aligns with how Purview preview features work. The UI can use internal or private APIs that aren’t yet exposed publicly, which explains why rules are visible and manageable in the UI but not accessible via REST. Additionally, regional rollout is still limited during preview, and North Europe is not always among the first regions to receive these capabilities. There are no clearly documented feature flags or SKU requirements, but access can still be controlled at the service or tenant level behind the scenes.

To validate this further, you could try the same API against a Purview account in a region like East US, where preview features are usually enabled earlier. If it works there, that would confirm a regional limitation. If it still doesn’t work, it may indicate that your tenant hasn’t been enabled yet.

If this is impacting your work, the best next step would be to raise a Microsoft support ticket so the product team can confirm regional availability and whether your tenant can be enabled for the preview.

Based on your testing so far, this doesn’t look like a misconfiguration, it’s most likely a service exposure limitation in preview.
Pilladi Padma Sai Manisha 10,110 Reputation points Microsoft External Staff Moderator

2026-04-22T14:38:14.79+00:00

Hi
Following up to see if the below answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Erwin van Ek 0 Reputation points

2026-04-22T14:47:33.6833333+00:00

Unfortunately, I can only create one Purview user in our tenant at the moment. I’ll wait for now. Thank you.

Answer 2

Hi Erwin van Ek ,

it looks like you’re running into a 404 because the Data Quality API endpoint you’re hitting isn’t quite right (and/or the service isn’t deployed in your region yet). A couple of things to try:

Make sure you’re using the unifiedcatalog path, not purviewdataquality. The Data Quality versions endpoint should be: GET https://<YOUR_PURVIEW_ACCOUNT>.purview.azure.com/unifiedcatalog/dataQuality/api/versions?api-version=2023-09-01-preview
If you still get 404 after correcting the URL, the Data Quality service (currently in Public Preview) might not be live in your region yet.

Can you share a bit more to help narrow this down?

• Exact URL you’re calling (minus any secrets)

• The full region name of your Purview account

• The api-version you’re using

• Whether you’ve tested a region where it’s known to work (e.g. East US)

Reference docs:

• Data Quality API for Unified Catalog (Public Preview)

https://learn.microsoft.com/rest/api/purview/unified-catalog-data-quality

• Common REST API errors (includes 404 troubleshooting)

https://learn.microsoft.com/azure/purview/troubleshoot-rest-api-errors#assets-issues-with-rest-api-call

• Purview REST API Data Plane samples

https://learn.microsoft.com/azure/purview/tutorial-using-rest-apis