Migrating a Microsoft Purview account to another Azure tenant or subscription isn’t currently supported as a direct, automated process. This is because Microsoft Purview has deep dependencies on Azure Active Directory (AAD) and is tightly integrated with the subscription and tenant where it was originally created.
That said, you can manually recreate your Purview environment in the new tenant or subscription by following these steps:
Recommended approach
Create a new Purview account - In the target tenant or subscription, create a new Microsoft Purview account.
Back up your configuration and metadata - Use Purview REST APIs or scripts to export:
- Glossary terms
- Classifications
- Custom attributes
- Collection hierarchy
- Scan rulesets
Re-register data sources - Set up your data sources again in the new account and reconfigure the integration runtimes and scan credentials.
Reconfigure access policies - Access control settings (e.g., RBAC and collections permissions) are tenant-specific and must be manually recreated.
Run tests - Before making the new Purview account your production environment, perform scans and validate metadata to ensure everything is functioning correctly.
Things to consider
Data Loss Risk – Metadata and configuration won’t automatically carry over, so exporting is crucial.
Identity Differences – Users and groups in the old tenant won't exist in the new tenant unless you map or recreate them.
Downtime – You may experience downtime during the transition, depending on your usage.
No Migration Tool – There's no native Microsoft tool for end-to-end Purview migration at this time.
For additional information, please refer: Microsoft Purview disaster recovery and migration best practices
I hope this information helps. Please do let us know if you have any further queries.
If this answers your query, do click Accept Answer
and Yes
for was this answer helpful. And, if you have any further query do let us know.
Thank you.