Share via

How to migrate Microsoft Purview configuration and metadata from TEST to PROD?

Piotr Tybulewicz 125 Reputation points
2025-11-24T10:55:07.0466667+00:00

Hi Team,

I have deployed a Microsoft Purview account in an Azure TEST subscription so that our data stewards can evaluate its data governance capabilities. They are currently creating and managing data products, configuring domains/collections, setting up scans, credentials, custom attributes, and working with various scanned data assets.

Since an Azure tenant can host only one Microsoft Purview account, we will eventually need to remove the TEST instance and deploy the final production instance in the PROD subscription.

To avoid losing all the work done by the data stewards, I would like to ask:

Is there any supported way to preserve or migrate Purview configuration and metadata - such as data sources, scans, credentials, domains, collections, governance domains, data products, custom attributes, etc. - from one Purview account to another?

If deploying a second Purview account is not possible, is there any export/import mechanism or recommended approach to transfer all settings and configuration from TEST to PROD?

Regards,

Piotr

Microsoft Security | Microsoft Purview
Answer accepted by question author
  1. VRISHABHANATH PATIL 2,070 Reputation points Microsoft External Staff Moderator
    2025-12-03T06:53:27.6666667+00:00

    Hi @Piotr Tybulewicz

    Thanks for contacting to Microsoft QA, below are the few mitigation steps that may help you to resolve the issue.

    Migration Steps -

    • Set Up a New Purview Account Create a Microsoft Purview account in your production Azure subscription. You can follow the official Quickstart guide in the Azure portal.
    • Move Your Configurations There’s no direct migration button, so you’ll need to replicate settings manually or via APIs:
      • Collections: List existing collections and recreate them using the API.
        • Data Sources: Fetch all data sources with the API and add them to the new account.
          • Scan Rules: Use the scan rules API to copy and set them up again.
            • Credentials: These must be re-entered manually (no API available).
            • Run Fresh Scans Instead of exporting assets, run new scans to avoid hitting limits and ensure everything is up-to-date. Confirm your self-hosted integration runtimes are ready before scanning.
            • Recreate Other Items For custom types and glossary terms, use their respective APIs. Be mindful of dependencies and relationships.
            • Validate Everything After migration, test thoroughly to confirm all configurations work as expected in production.

    References:

    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2025-11-24T10:55:17.78+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    To migrate Microsoft Purview configuration and metadata from a TEST account to a PROD account, you can follow these steps:

    1. Create the New Account: If your organization needs to create a new Microsoft Purview account for production, you can do so by following the instructions in the Microsoft documentation. Ensure that you plan the configuration items that cannot be changed later, such as account name, region, and subscription.
    2. Migrate Configuration Items: You will need to manually migrate various configuration items, as there is no direct export/import mechanism available. Here are some key items to consider:
      • Data Sources: Use the Get all data sources API to list the data sources and then recreate them in the new account using the Create data sources API.
      • Scans: Set up scans in the new account based on the configurations from the TEST account.
      • Credentials: Since there is no API to extract credentials, you will need to recreate them manually in the new account.
      • Collections and Governance Domains: Use the List Collections API to get details of collections and recreate them in the new account.
      • Custom Attributes: Manually document and recreate any custom attributes that were set up in the TEST account.
    3. Run Scans: After setting up the new account, ensure that your self-hosted integration runtimes are configured and running. Running scans will help populate all assets with the default type definitions and ensure that all relationships and asset details are up to date.
    4. Manual Classifications and Resource Set Rules: You will also need to manually migrate any manual classifications and resource set rules by calling the respective APIs to get the details and then recreate them in the new account.

    By following these steps, you can effectively migrate your Microsoft Purview configuration and metadata from the TEST to the PROD environment while preserving the work done by your data stewards.

    References:

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.