For Microsoft Purview users
A Microsoft Fabric data catalog that goes beyond Purview
Purview tracks most Fabric lineage item by item and bills per governed asset, plus Data Map capacity and data quality compute. Dawiso maps lineage across Fabric, Power BI and the platforms next to them, and is priced per user. You buy it on Azure Marketplace and pay through your Azure bill.
Dawiso customer on Fabric and Databricks
The close dialogue with the Dawiso team is what made the pilot work: when our model didn't fit the tool, they adapted the tool to us.
- ~60 daysfrom kick-off to fully operational
- 18,000+objects cataloged in Microsoft Fabric
01At a glance
Dawiso vs Microsoft Purview, side by side
Purview facts come from Microsoft’s own documentation and price list.
| Area | Dawiso | Microsoft Purview |
|---|---|---|
| Fabric lineage | Lineage across Fabric, Power BI and the platforms next to them | Outside Power BI: item-level lineage, none across workspaces |
| Beyond Microsoft | Databricks, Snowflake, dbt, SAP HANA, Oracle, Tableau | Lineage beyond Microsoft takes extra work |
| Pricing | Per user, unlimited connectors | Per governed asset per day, plus processing units for data quality |
| Deployment | SaaS on Azure or on premises | SaaS on Azure |
| Security and compliance | Classifies personal data in the catalog, enforcement stays in the source | Purview leads: DLP, sensitivity labels and policies |
02How it works
Govern Microsoft Fabric end to end, in a catalog built for the whole business
03Where Dawiso wins
Six things Purview users ask about, one verdict each
Open a row for the detail.
Fabric lineage Lineage that follows your data across platforms
Dawiso catalogs Fabric from the tenant and workspace down to semantic models, tables and columns, including DAX and Power Query expressions. It draws lineage across Fabric, Power BI and the other connected platforms, so before you change a lakehouse or a model, you see which reports depend on it.
For Fabric items other than Power BI, Purview captures metadata and lineage at item level, and cross-workspace lineage is not supported, according to Microsoft’s own documentation.
Dawiso reads metadata only, through one Entra ID service principal. Your data stays in OneLake.
Beyond Microsoft One catalog for Fabric and everything next to it
Connectors for Databricks, Snowflake, dbt, Oracle, SAP HANA, Tableau and more sit next to Fabric, Power BI, Azure Synapse and Azure Data Factory, with no limit on connectors in any plan.
Lineage goes down to the column through dbt, and through SQL parsing on Enterprise. Bertel O. Steen runs Microsoft Fabric and Databricks side by side in Dawiso, with impact analysis across both in one view.
Run it as SaaS on Azure or on premises on the Enterprise plan.
See all connectorsBusiness adoption A catalog the business opens
People search in their own words: business terms, technical assets and data products in one place. Every asset shows what it means, who owns it and whether it is certified.
Analysts and domain experts add content themselves, and built-in AI drafts descriptions for them to review. At Kooperativa, 150+ people contribute and the catalog gets 23,000+ visits a month.
Lifecycle management Approvals and lifecycle built in
Glossary terms, data products and assets move through states such as draft, review and approved, with the approval steps you define. Mark items as certified, deprecated or under review, so people know what is current.
Raiffeisenbank governs around 4,000 internal documents this way, with approval paths set by document type, from draft to archive.
Read the Raiffeisenbank storyFlexibility Your metamodel, your workflows
Configure attributes, object types and workflows to match how your organization works, instead of fitting your governance into a fixed structure.
Build your own apps from low-code JSON packages, and keep metadata cleanly separated across companies, divisions or tenants.
AI Your own AI model and agents
Built-in AI features come with every plan. On the Corporate and Enterprise plans they can run on your own OpenAI or Azure OpenAI account.
A managed MCP server gives Claude, Cursor and other MCP-compatible agents the same governed definitions, owners and lineage, on the Corporate and Enterprise plans in Dawiso Cloud.
See lineage across your Fabric estate. We will show you Dawiso on a stack like yours.
04Price
Per user, not per asset.
-
Microsoft Purview
Per governed asset About $0.50 per asset per month, plus processing units for every data quality run. The bill grows with every asset you govern. -
Dawiso
Per user Unlimited connectors. Cataloging more does not change the bill up to 100,000 objects per contributor.
05FAQ
Frequently asked questions
Something else on your mind? Contact us and we will get back to you shortly.
What is the best alternative to Microsoft Purview for data governance?
For teams on Microsoft Fabric that need lineage across Fabric, Power BI and the rest of their stack, and a catalog business users work in, Dawiso is built for exactly that. It runs on Azure, is available on Azure Marketplace, catalogs Fabric and Power BI in depth and connects to Databricks, Snowflake, SAP HANA and more.
Does Dawiso work with Microsoft Fabric?
Yes. Dawiso catalogs Fabric from the tenant and workspace down to semantic models, tables and columns, including DAX and Power Query expressions and Lakehouse, Warehouse and SQL Database schemas. It draws lineage across Fabric, Power BI and the other connected platforms, and reads metadata only through an Entra ID service principal. See the Fabric connector.
Can we buy Dawiso through Azure Marketplace?
Yes. Dawiso is available on Azure Marketplace, so you can buy it through your Azure account and it is billed through Azure, without a new vendor agreement. Read the announcement.
How is Dawiso priced compared to Microsoft Purview?
Microsoft bills Purview data governance pay-as-you-go, by governed asset and by processing unit for data quality, so the bill grows with every asset you govern. Dawiso is priced per user, with unlimited connectors and 100,000 cataloged objects per contributor, and publishes its pricing. How Purview pricing works and Dawiso pricing.
Do we have to stop using Microsoft Purview to use Dawiso?
No. Purview’s security and compliance features, such as sensitivity labels and data loss prevention, are separate from its data catalog, and you can keep them. Dawiso covers the catalog side, including classification of personal data, while enforcement stays with Purview and the source.
What if our data is not only on Microsoft?
That is the usual case, and Dawiso is built for it. Alongside Fabric, Power BI, Azure Synapse, Azure Data Factory and SQL Server, it connects to Databricks, Snowflake, dbt, Oracle, SAP HANA, Tableau and more, with lineage across them, down to the column where the source allows it. See all connectors.
Can Dawiso run on our own Azure OpenAI model?
Yes. On the Corporate and Enterprise plans, Dawiso’s built-in AI features can run on your own OpenAI or Azure OpenAI account, and in Dawiso Cloud a managed MCP server gives Claude, Cursor and other MCP-compatible agents governed context from Dawiso.
Does Dawiso support Microsoft Entra ID?
Yes. Microsoft SSO and Azure AD user sync are included in every plan, and the Fabric connector authenticates with an Entra ID service principal.
How long does it take to implement Dawiso?
Connecting Fabric takes one Entra ID service principal and workspace access. A full rollout depends on scope: Bertel O. Steen, on Databricks and Microsoft Fabric, was fully operational in about 60 days, and P3 Parks in 78 days. Read the Bertel O. Steen story.
When does Microsoft Purview still make sense?
Purview is a sensible choice when your data lives almost entirely in Microsoft and governance is owned mainly by security and compliance. Its data security features, such as sensitivity labels and data loss prevention, stay useful next to Dawiso.
Ready for a catalog the whole business uses?
See Dawiso on Fabric, Power BI and the rest of your stack, in a demo built around your setup.