With the new MS Purview how do we test something out since there is no option of having multiple instances like the classic version?

Question

With Classic Purview we had the capability to have multiple instances so we had the option to have one instance just for testing. With the New MS Purview there is no such option. So what are the capabilities/options around having a test environment without having to test things out in our live environment? Our one instance will be our Live/Production environment. Our one instance will be our PRD Environment.

Answer 1

Hi Ipshita,
Thankyou for reaching microsoft Q&A!
In the new Microsoft Purview experience, the service operates at a tenant level, so multiple instances like Classic Purview are no longer supported. For testing, the recommended approach is to use domains and collections to create logical separation within the same environment. You can create a dedicated Dev/Test domain, build separate collection hierarchies, and apply scoped RBAC roles so testing activities do not impact production assets. Register non-production data sources and validate scans, classifications, and policies within these isolated collections. If complete isolation is required, the supported option is to use a separate non-production tenant rather than requesting additional Purview instances.

Answer 2

In the new Microsoft Purview, you are correct that the ability to create multiple instances like in the classic version is no longer available. However, you can still explore testing options by utilizing the free version of Microsoft Purview for initial evaluations and development scenarios. Here are some options to consider:

1. Free Version: You can start with the free version of Microsoft Purview, which allows you to test capabilities with limited features. This can be useful for development and testing purposes without affecting your production environment.
2. Use of APIs: You can also use the APIs provided by Microsoft Purview to create new entities and manage data assets programmatically. This allows you to test various functionalities without impacting your live environment.
3. Sandbox Environment: If your organization has the capability, consider setting up a sandbox environment using separate Azure resources that mimic your production setup. This can help you test configurations and features safely.
4. Staging Area: You might also consider using a staging area within your existing instance where you can perform tests with non-critical data before deploying changes to your production environment.

These approaches can help you mitigate risks while exploring the features of the new Microsoft Purview without compromising your live data or operations.