Migrate from Azure Data Catalog to Microsoft Purview
Microsoft launched a unified data governance service to help manage and govern your on-premises, multicloud, and software-as-a-service (SaaS) data. Microsoft Purview creates a map of your data landscape with automated data discovery, sensitive data classification, and end-to-end data lineage. Microsoft Purview enables data curators to manage and secure their data estate and empowers data consumers to find valuable, trustworthy data.
The document shows you how to do the migration from Azure Data Catalog to Microsoft Purview.
Recommended approach
To migrate from Azure Data Catalog to Microsoft Purview, we recommend the following approach:
✔️ Step 1: Assess readiness
✔️ Step 2: Prepare to migrate
✔️ Step 3: Migrate to Microsoft Purview
✔️ Step 4: Cutover from Azure Data Catalog to Microsoft Purview
Note
Azure Data Catalog and Microsoft Purview are different services, so there is no in-place upgrade experience. Intentional migration effort required.
Assess readiness
Look at Microsoft Purview and understand key differences of Azure Data Catalog and Microsoft Purview.
Azure Data Catalog | Microsoft Purview | |
---|---|---|
Pricing | User based model | Pay-As-You-Go model |
Platform | Data catalog | Unified governance platform for data discoverability, classification, lineage, and governance. |
Data sources supported | Data Catalog supported sources | Microsoft Purview supported sources) |
Extensibility | N/A | Extensible on Apache Atlas |
SDK/PowerShell support | N/A | Supports REST APIs |
Prepare to migrate
- Identify data sources that you'll migrate. Take this opportunity to identify logical and business connections between your data sources and assets. Microsoft Purview will allow you to create a map of your data landscape that reflects how your data is used and discovered in your organization.
- Review Microsoft Purview best practices for deployment and architecture to develop a deployment strategy for Microsoft Purview.
- Determine the impact that a migration will have on your business. For example: how will Azure Data catalog be used until the transition is complete?
- Create a migration plan using the Microsoft Purview deployment checklist.
Migrate to Microsoft Purview
Create a Microsoft Purview account, create collections in your data map, set up permissions for your users, and onboard your data sources.
We suggest you review the Microsoft Purview best practices documentation before deploying your Microsoft Purview account, so you can deploy the best environment for your data landscape. Here's a selection of articles that may help you get started:
- Microsoft Purview deployment checklist
- Microsoft Purview security best practices
- Accounts architecture best practices
- Collections architectures best practices
- Create a collection
- Import Azure sources to Microsoft Purview at scale
- Tutorial: Onboard an on-premises SQL Server instance
Cutover from Azure Data Catalog to Microsoft Purview
After the business has begun to use Microsoft Purview, cutover from Azure Data Catalog by deleting the Azure Data Catalog.
Next steps
- Learn how Microsoft Purview's data insights can provide you up-to-date information on your data landscape.
- Learn how Microsoft Purview integrations with Azure security products to bring even more security to your data landscape.
- Discover how sensitivity labels in Microsoft Purview help detect and protect your sensitive information.
Feedback
Submit and view feedback for