Purview Data Quality

Question

Purview Data Quality

Abhradeep Das 0

Hi Team,

We are using Microsoft Purview and noticed that AWS Redshift is available as a supported data source for metadata scanning and cataloging in Data Map.

However, when configuring Data Quality, we do not see an option to add AWS Redshift as a data source.

Could you please clarify the following:

Is Amazon Redshift currently supported as a data source for Microsoft Purview Data Quality?
1
If it is not currently supported, are there any recommended workarounds or alternative approaches to perform data quality assessments on data stored in Amazon Redshift?
Are there any roadmap plans to add native Amazon Redshift support to the Data Quality capability in Purview?

Our understanding is that Redshift can be scanned and cataloged successfully in the Data Map, but we are unable to find a corresponding option while configuring Data Quality.

Any guidance or official documentation would be greatly appreciated.

Thank you.

Peram Venkateswara Reddy 5 Microsoft External Staff Moderator

Hi @Abhradeep Das , Hope you are doing well.

Hi Abhradeep,

Good catch — your observation is correct, and it's expected behaviour rather than a configuration issue on your side. Here's the breakdown against all three of your questions.

Is Amazon Redshift supported for Purview Data Quality?

No — not currently. The supported sources for Data Quality in Unified Catalog are:

Data source	Profiling	DQ scan
Azure Data Lake Storage Gen2	Yes	Yes
--------	--------	--------
Azure Data Lake Storage Gen2	Yes	Yes
Azure Databricks Unity Catalog	Yes	Yes
Azure Synapse serverless	Yes	Yes
Azure Synapse Data Warehouse	Yes	Yes
Azure SQL Database	Yes	Yes
Azure SQL Managed Instance	Yes	Yes
Azure Dedicated SQL Pool	Yes	Yes
Google BigQuery	Yes	Yes
Snowflake	Yes	Yes
Fabric	Yes	Yes
Amazon S3	Yes	Yes (via Fabric shortcut)
Dataverse	Yes	Yes (via Fabric shortcut)
Google Cloud Storage	Yes	Yes (via Fabric shortcut)
Oracle	No	Yes (on-premises)
SQL Server	No	Yes (on-premises)

Amazon Redshift isn't on this list, which is why no option appears when you configure a Data Quality connection.

Your understanding of the Data Map side is also correct: Redshift is supported there (currently in preview) for metadata extraction — server, databases, schemas, tables with columns/foreign keys/unique constraints, views, stored procedures, and functions. Full and scoped scans are supported; incremental scans are not. So cataloguing works; quality assessment doesn't. The two capabilities have separate source lists.

Workarounds

The practical pattern is to land the Redshift data in a source that Data Quality does support, then run profiling and rules there:

Option A — Fabric Lakehouse (recommended). Fabric's Data Factory has a native Amazon Redshift connector (Dataflow Gen2, with Import and DirectQuery). Land the tables in a Fabric Lakehouse, then run Data Quality against the Lakehouse — Fabric is fully supported for both profiling and DQ scans, including virtual network scenarios.
Option B — S3 via Fabric shortcut. If you already UNLOAD Redshift data to S3, Amazon S3 is supported for Data Quality via a Fabric shortcut. Use Parquet or Delta (both are supported file formats, along with Iceberg Avro and Iceberg Orc).
Option C — ADLS Gen2 or Azure SQL. Copy the relevant tables into either via a pipeline; both are fully supported.

Two things to plan for with any of these:

Data Quality scans run on Apache Spark 3.5 / Delta Lake 3.2.1, and Managed Identity is the authentication method for Microsoft-native sources (note that Managed Identity can't be used for Azure Databricks, Snowflake, or Google BigQuery).
If a schema changes at the source, re-run Import schema from the Data Quality overview page before scanning, or the job may fail.

One caveat worth stating plainly: these approaches assess quality on a copy of the data, so results reflect the copy's freshness rather than live Redshift state. Align the refresh cadence with your assessment needs.

Roadmap

There's no published commitment for native Redshift support in Data Quality, and roadmap timing isn't something that can be confirmed through Q&A. Two places to track and influence it:

The supported sources page — this is updated as sources are added, so it's the authoritative place to check.
Submit the request through the Microsoft Purview feedback/ideas channel, and raise it with your Microsoft account team if you have one — customer demand signals are what drive connector prioritisation.

References

Kind Regards,
Microsoft Support Team.

Peram Venkateswara Reddy 5 Reputation points Microsoft External Staff Moderator

2026-08-05T08:14:49.4433333+00:00

Hi @Abhradeep Das , Hope you are doing well. Following up on my previous comment regarding you query. Please let us know if it is resolved your query.

Regards,
Microsoft Support Team.

1 answer

Your answer

Peram Venkateswara Reddy 5 Reputation points Microsoft External Staff Moderator

2026-08-05T08:14:49.4433333+00:00

Hi @Abhradeep Das , Hope you are doing well. Following up on my previous comment regarding you query. Please let us know if it is resolved your query.

Regards,
Microsoft Support Team.

Answer 1

Amazon Redshift is currently supported in Microsoft Purview for Data Map metadata scanning and cataloging, but it is not listed as a supported data source for Data Quality.

Supported Data Quality sources currently include Azure Data Lake Storage Gen2, Azure Databricks Unity Catalog, Azure Synapse serverless, Azure Synapse Data Warehouse, Azure SQL Database, Azure SQL Managed Instance, Azure Dedicated SQL Pool, Google BigQuery, Snowflake, Fabric, Amazon S3, Dataverse, Google Cloud Storage, Oracle, and SQL Server. Amazon Redshift does not appear in that supported Data Quality source list.

For the current gap:

Catalog Redshift in Data Map
- Redshift can be registered and scanned in Data Map.
- Purview supports extracting metadata such as databases, schemas, tables, views, stored procedures, and functions.
Use an alternative supported Data Quality source
- If Redshift data can be made available through a supported source for Data Quality, that supported source can be assessed there instead.
- Examples of supported Data Quality sources include Snowflake, Google BigQuery, Azure SQL, Synapse, Fabric, and Amazon S3.
No documented native Redshift Data Quality support or roadmap in the available documentation
- There is no published support statement in the available documentation showing Amazon Redshift as a native Data Quality source.
- There is also no roadmap statement in the available documentation confirming when or whether native Redshift support will be added.

So the current behavior is consistent with the product documentation: Redshift is supported for scanning in Data Map, but not currently supported as a Data Quality data source in Purview Unified Catalog.