---
title: "Purview Role Migration After the Retirement | Dawiso"
description: "Purview role migration explained: what the Role Assignment Migrator does, and how Unified Catalog and Data Map roles map to Fabric or a data catalog."
url: "https://www.dawiso.com/glossary/purview-role-migration"
language: "en"
---

November 18, 2026

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](https://learn.microsoft.com/en-us/purview/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 role | Purview roles synced to it, per Microsoft |
| --- | --- |
| Purview Workload Content Reader | Insider Risk Management Analysis and Investigation, Compliance Search, Export, the Privacy Management roles, Data Security Investigation Reviewer |
| Purview Workload Content Writer | Hold, Privacy Management Investigation, Data Security Investigation Investigator |
| Purview Workload Content Administrator | Search 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](https://learn.microsoft.com/en-us/purview/data-governance-roles-permissions) 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](https://learn.microsoft.com/en-us/purview/data-gov-classic-permissions) 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.

## 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](https://techcommunity.microsoft.com/blog/analyticsonazure/from-purview-data-governance-to-the-fabric-onelake-catalog/4573422) 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 role | Closest Fabric equivalent | What to watch |
| --- | --- | --- |
| Data Governance Administrator, Purview Administrators | [Fabric admin](https://learn.microsoft.com/en-us/fabric/governance/domains), who creates domains and names domain admins | A tenant-wide administrative role, broader than governance alone |
| Governance Domain Creator | Fabric admin | Only Fabric admins create domains |
| Governance Domain Owner, Collection admin | Domain admin | A domain admin cannot delete or rename the domain or add other domain admins |
| Data Steward, Data curator, Global Asset Curator | No dedicated role; workspace Member or Contributor for editing items | Microsoft advises a responsibility matrix for stewardship duties with no role |
| Data Product Owner | Item owner and workspace Contributor | The product contract, lifecycle and access process sit outside the catalog where Fabric does not cover them |
| Global or Local Catalog Reader, Data reader | [Workspace Viewer](https://learn.microsoft.com/en-us/fabric/fundamentals/roles-workspaces), item permissions, a OneLake security Read role | Sharing an item does not necessarily grant permission to query its OneLake data |
| Data Source Administrator, Data source admin | Workspace Admin; shortcuts, mirroring and connectors take the place of scans | External sources are connected, not scanned as metadata |
| Data Quality Steward and data quality readers | No equivalent in the OneLake catalog | Data quality rules move to a separate tool |
| Policy author | Fabric Policies (preview), managed in the Govern tab of the OneLake catalog | Fabric Policies allow only three policy types today |
| Workflow admin | No equivalent | Approval 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](https://learn.microsoft.com/en-us/fabric/onelake/security/data-access-control-model) 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](https://www.dawiso.com/glossary/purview-to-fabric).

[See it in action](https://www.dawiso.com/microsoft-purview-alternative)

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?](https://www.dawiso.com/glossary/microsoft-purview-migration-tool), [Purview glossary migration](https://www.dawiso.com/glossary/purview-glossary-migration) and [Microsoft Purview Data Governance is retiring](https://www.dawiso.com/blog-post/microsoft-purview-data-governance-retirement).

## Sources

- Microsoft Learn - [Purview Role Assignment Migrator](https://learn.microsoft.com/en-us/purview/purview-role-assignment-migrator)
- Microsoft Learn - [Roles and permissions in Unified Catalog](https://learn.microsoft.com/en-us/purview/data-governance-roles-permissions)
- Microsoft Learn - [Permissions in the classic data governance experience](https://learn.microsoft.com/en-us/purview/data-gov-classic-permissions)
- Microsoft Analytics on Azure Blog - [From Purview Data Governance to the Fabric OneLake Catalog](https://techcommunity.microsoft.com/blog/analyticsonazure/from-purview-data-governance-to-the-fabric-onelake-catalog/4573422) (November 13, 2026)
- Microsoft Learn - [Roles in workspaces in Microsoft Fabric](https://learn.microsoft.com/en-us/fabric/fundamentals/roles-workspaces)
- Microsoft Learn - [Fabric domains](https://learn.microsoft.com/en-us/fabric/governance/domains)
- Microsoft Learn - [OneLake security access control model](https://learn.microsoft.com/en-us/fabric/onelake/security/data-access-control-model)
- Dawiso Help - [User and user role management](https://help.dawiso.com/actual/user-and-user-role-management/), [User roles and permissions](https://help.dawiso.com/actual/user-roles-permissions-overview/), [Workflows](https://help.dawiso.com/actual/workflows-overview/), [Data product lifecycle](https://help.dawiso.com/actual/data-product-lifecycle/) and [Microsoft Entra ID synchronization](https://help.dawiso.com/actual/microsoft-entra-id-synchronization/)

[See it in action](https://www.dawiso.com/microsoft-purview-alternative)

Moving off Purview Data Governance?

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

### Table of contents

What is Purview role migration?What is the Purview Role Assignment Migrator?Purview data governance rolesMapping Purview roles to FabricMapping Purview roles to a data catalogHow to migrate Purview role assignmentsSources

## Related Terms

### [Purview to Fabric: Mapping Data Governance to OneLake](https://www.dawiso.com/glossary/purview-to-fabric)

Purview to Fabric mapped object by object: what moves to the OneLake catalog, what is partial or missing, what stays in Purview and how to move in waves.

Read more →

### [Microsoft Fabric vs Purview: What Each One Does](https://www.dawiso.com/glossary/microsoft-fabric-vs-purview)

Microsoft Fabric vs Purview explained: an analytics platform and a security and compliance suite, and what changes as Purview Data Governance retires.

Read more →

### [What Is Data Stewardship?](https://www.dawiso.com/glossary/data-stewardship)

Data stewardship is the practice of keeping data accurate, documented and governed. How to build a stewardship program, find stewards and make it stick.

Read more →

### [Is There a Microsoft Purview Migration Tool?](https://www.dawiso.com/glossary/microsoft-purview-migration-tool)

There is no Microsoft Purview migration tool for leaving Purview Data Governance. See what the three Purview migration tools do and how to export your content.

Read more →

### [Purview Glossary Migration: How to Move Your Terms](https://www.dawiso.com/glossary/purview-glossary-migration)

Purview glossary migration step by step: classic vs Unified Catalog terms, how to export them, what gets lost and how fields map to Fabric or a data catalog.

Read more →

### [What Is the Microsoft Purview Unified Catalog?](https://www.dawiso.com/glossary/microsoft-purview-unified-catalog)

The Microsoft Purview Unified Catalog explained: domains, data products, CDEs, how it differs from the Data Map, and what its retirement means for you.

Read more →
