Skip to main content
purview role migrationpurview role assignment migrationpurview unified catalog rolespurview data governance retirementmicrosoft fabricdata stewardship

Purview Role Migration After the Data Governance Retirement

Purview role migration means two different things in November 2026: the Purview Role Assignment Migrator, which syncs security and compliance roles to Microsoft Entra ID, and the move of data governance roles out of Purview before Purview Data Governance retires on November 12, 2027. The first one runs in the background and has nothing to do with the retirement. The second one has no tool, and it decides who owns, curates and reads your governed data after the move.

This page explains the Role Assignment Migrator first, so you can set it aside, then lists the Unified Catalog and classic Data Map roles and maps each one to Microsoft Fabric and to a data catalog.

TL;DR

The Role Assignment Migrator syncs Purview security and compliance roles, such as Compliance Search, Export and Hold, to Entra roles. It covers no data governance roles. Data governance roles, such as Governance Domain Owner, Data Steward, Data Product Owner and Data Curator, have no migration path. In Fabric they become workspace roles, domain admins and OneLake security roles, and stewardship has no dedicated role, so Microsoft advises a responsibility matrix. A data catalog such as Dawiso keeps owners and stewards as roles on the objects, with access granted through Entra ID groups.

What is Purview role migration?

People searching for Purview role migration usually land in one of two situations. A Microsoft 365 or security administrator sees the Role Assignment Migrator in Entra ID or in audit logs and wants to know what it does. A data governance lead needs to know where the people with roles in the Unified Catalog will get their rights after the retirement. The two have the same words in their names and nothing else in common.

What is the Purview Role Assignment Migrator?

The Purview Role Assignment Migrator is a Microsoft first-party enterprise application in Microsoft Entra ID. It syncs assignments of Purview roles to three Entra roles, which Microsoft 365 services check before long-running Purview operations such as content search and export continue:

Entra rolePurview roles synced to it, per Microsoft
Purview Workload Content ReaderInsider Risk Management Analysis and Investigation, Compliance Search, Export, the Privacy Management roles, Data Security Investigation Reviewer
Purview Workload Content WriterHold, Privacy Management Investigation, Data Security Investigation Investigator
Purview Workload Content AdministratorSearch and Purge, Data Security Investigation Admin and Analyst

Three facts from Microsoft's page are worth knowing. The application should stay enabled, because new Purview role assignments otherwise stop reaching Entra and long-running operations can fail authorization checks. It can overwrite manual changes to these Entra roles, so they should not be assigned by hand. And the list contains no Unified Catalog or Data Map role. For a data governance migration, there is nothing to do with it.

Purview data governance roles that need a new home

These are the roles that retire with Purview Data Governance. The Unified Catalog roles work at three levels:

  • Tenant role groups: Data Governance, Data Source Administrators and Purview Administrators.
  • Catalog level: Data Governance Administrator, Governance Domain Creator, Global Catalog Reader, Global Asset Curator, Data Health Owner and Data Health Reader.
  • Governance domain level: Governance Domain Owner and Reader, Data Steward, Data Product Owner, Local Catalog Reader, and the data quality sub-roles: Data Quality Steward, Data Profile Steward, Data Profile Reader, Data Quality Reader and Data Quality Metadata Reader.

The classic Data Map roles are scoped to collections and inherited by subcollections: Collection admin, Data source admin, Data curator, Data reader, Policy author, Workflow admin and Insights reader, plus a Domain admin at domain level. Tenants that use the Unified Catalog often hold both sets, because the Data Map scans the sources behind it.

Purview Role Migration - Where Each Role Goes PURVIEW ROLE MIGRATION - WHERE EACH ROLE GOES PURVIEW DATA GOVERNANCE MICROSOFT FABRIC OR A DATA CATALOG (DAWISO) Data Governance Administrator Purview Administrators Fabric admin Admin Governance Domain Owner Collection admin Domain admin Owner of the business domain Data Steward Data curator No dedicated role Responsibility matrix Steward role on objects Data Product Owner Item owner Workspace Contributor Owner of the data product Global or Local Catalog Reader Data reader Workspace Viewer OneLake security Read role Viewer with read access Assign every role to Microsoft Entra ID groups, not to individual people
Click to enlarge

Mapping Purview roles to Microsoft Fabric

Fabric has no governance role model of its own in the Purview sense. Access is built from four layers, which Microsoft's transition guidance lays out: workspace roles for broad capability, item permissions for one data product, OneLake security for different tables or rows of the same product, and separate workspaces only where administration or network needs really differ.

Purview roleClosest Fabric equivalentWhat to watch
Data Governance Administrator, Purview AdministratorsFabric admin, who creates domains and names domain adminsA tenant-wide administrative role, broader than governance alone
Governance Domain CreatorFabric adminOnly Fabric admins create domains
Governance Domain Owner, Collection adminDomain adminA domain admin cannot delete or rename the domain or add other domain admins
Data Steward, Data curator, Global Asset CuratorNo dedicated role; workspace Member or Contributor for editing itemsMicrosoft advises a responsibility matrix for stewardship duties with no role
Data Product OwnerItem owner and workspace ContributorThe product contract, lifecycle and access process sit outside the catalog where Fabric does not cover them
Global or Local Catalog Reader, Data readerWorkspace Viewer, item permissions, a OneLake security Read roleSharing an item does not necessarily grant permission to query its OneLake data
Data Source Administrator, Data source adminWorkspace Admin; shortcuts, mirroring and connectors take the place of scansExternal sources are connected, not scanned as metadata
Data Quality Steward and data quality readersNo equivalent in the OneLake catalogData quality rules move to a separate tool
Policy authorFabric Policies (preview), managed in the Govern tab of the OneLake catalogFabric Policies allow only three policy types today
Workflow adminNo equivalentApproval flows move to another tool or an operating process

Two details change how roles behave in Fabric. Domain assignment does not affect item visibility or access, so a domain admin gets no data access from the domain alone. And OneLake security roles only grant, never deny, with limits of 250 roles per item and 500 members per role. Plan the groups before you plan the people. The wider object mapping is in Purview to Fabric.

See it in action

Dawiso as a Microsoft Purview alternative

Owners and stewards as roles on every term and data product, across Fabric and the platforms next to it.

Mapping Purview roles to a data catalog

A data catalog keeps the split Purview had: who may use the tool, and who is responsible for each object. In Dawiso, as documented on help.dawiso.com, that works like this:

  • Three main user roles. Admin manages users, groups and permissions, and the permissions matrix adds a space admin level. Contributor creates objects and edits attributes in the spaces they may write to. Viewer reads. Purview administrators map to Admin, stewards, curators and product owners to Contributor, and readers to Viewer.
  • Access per space. Read or write access is set per space for each user or user group, and group members inherit it. A Purview governance domain usually becomes a space with its own group.
  • Responsibility on the object. Owner and steward are roles on each term, domain or data product. Workflow transitions name who may move an object into review or approval, and a data product needs an owner before it reaches production.
  • Entra ID groups. Each Dawiso role maps to one Entra group, extra groups such as a data stewards group can be mirrored, and users are synced before their first sign-in, so they can be assigned as owners during the migration.

The practical difference from Fabric is that the steward role exists. A team that ran a stewardship model in Purview keeps it, instead of replacing it with a spreadsheet.

How to migrate Purview role assignments

  1. Export the current assignments. List role assignments per governance domain in the Unified Catalog and per collection in the Data Map. There is no export tool, so record them while the portal works.
  2. Map people to responsibilities. Group the assignments by what people do: administer, own a domain, steward terms, own products, read. Remove people who have left.
  3. Create Entra ID groups. Microsoft recommends assigning Fabric workspace roles to security groups rather than individuals. The same works for a data catalog.
  4. Assign roles in the target. Grant access to groups, then set owners and stewards on the migrated objects.
  5. Test a denied identity. Microsoft's pilot advice is to prove that access is blocked for someone who should not have it, not only that it works for those who should.

For the rest of the move, see Is there a Microsoft Purview migration tool?, Purview glossary migration and Microsoft Purview Data Governance is retiring.

Sources

See it in action

Moving off Purview Data Governance?

See how Dawiso maps owners, stewards and readers from Purview, with Entra ID groups.

A cookie a day keeps bad UX away.

We use cookies to personalize content, ads and to analyze our traffic. We also share information about your use of our site with our advertising and analytics partners who may combine it with other information that you've provided to them or that they've collected from your use of their services. By clicking "Accept All", you allow us to use cookies for analytics and ads via Google Tag Manager. You can also customize cookies.

Customize Consent Preferences

We use cookies to personalize content, ads and to analyze our traffic. We also share information about your use of our site with our advertising and analytics partners. Privacy Policy

Necessary cookies allow core website functionality such as user login and account management. The website cannot be used properly without strictly necessary cookies.

Functionality cookies are used to remember visitor information on the website, eg. language, timezone, enhanced content.

Analytics cookies are used to see how visitors use the website, eg. analytics cookies. Those cookies cannot be used to directly identify a certain visitor.

We use Microsoft Clarity to see how you use our website (including heatmaps and session replays) so we can improve it. By using our site, you agree that we and Microsoft can collect and use this data. See our Privacy Policy for details.

Advertisement cookies are used to identify visitors between different websites, eg. content partners, banner networks. Those cookies may be used by companies to build a profile of visitor interests or show relevant ads on other websites.