Forum Discussion

DavidCM's avatar
DavidCM
Brass Contributor
Oct 17, 2024

Different uses of the classic portal and the new portal

Hi everyone,

 

I explain my problem, but without expecting a solution, as I understand that is no bug/issue there.

 

My problem is that I had all the glossary terms in the Classic glossary, with some workflows.

Then when they released the new version, more oriented to data products and data mesh, I started to migrate the glossary terms to each business domain, but 1) workflows cannot be applied to new portal items (glossary terms from a business domain) and 2) the terms cannot be linked to data assets in the data map, only to data products (a container for data assets)

 

FYI, the Enterprise Glossary is made up of all the "Approved" glossary terms in each Business Domain, and this confused me a bit at first.

 

In other hand, if you go for the classic portal you loose all data quality functionalities inside data products. The classic one don't have data quality tracking.

 

I think Microsoft should explain well what each portal is for and how to use it and simplify life for everyone.

For example, I think they should make it clear that we should reserve the new portal only if you use Fabric and a Datamesh approach and for the rest of the architectures/uses, it is better to use the classic one.

Or eventually unify the glossaries and data asset's data quality to have better experience.

 

Thanks!

David

 

 

1 Reply

  • Prathista Ilango's avatar
    Prathista Ilango
    Icon for Microsoft rankMicrosoft
    Apr 08, 2026

    Hello DavidCM, 

    Thank you for sharing this. We completely understand the confusion and the current limitations you're seeing when moving from the Classic Glossary to the Enterprise Glossary experience.

    Today, the Classic Glossary (Data Catalog/Data Map) and the Enterprise Glossary (Unified Catalog) are separate experiences, with the Enterprise Glossary being the forward‑looking model for managing business concepts aligned to governance domains and data products. The Classic experience remains supported but is in support mode with no new feature investments.

    That said, glossary migration from the Classic experience to the Unified Catalog glossary is on the roadmap, enabling glossary management from a single place going forward.

    MS-Purview-Data-Governance-Roadmap-H1-CY2026.pdf

    Hope that helps! 

    Please mark as solution, if you find the answer helpful. This will assist others in the community who encounter a similar issue, enabling them to quickly find the solution and benefit from the guidance provided.