Forum Discussion
Is it possible to prevent Microsoft Purview from being applied to M365 within the tenant?
Hello. Thank you for viewing my post.
I am currently considering trying out Purview to enhance data management within Microsoft Fabric.
However, I am facing an issue where I cannot proceed to proof-of-concept testing because the impact on the M365 environment used within the tenant is unknown.
I have reviewed Microsoft's official information and understand the following:
・Using Purview features for M365 requires an E5 license
・Using Purview for Fabric requires a pay-as-you-go Purview subscription
However, I still haven't confirmed what specific impact it might have on M365.
I'm looking for ways to use Purview solely for Fabric, or methods to identify specific operations/settings that could affect M365.
I would greatly appreciate any insights you could share.
The majority of features included within Purview need to be configured first, before they take effect in any given tenant. There are also some features that use a "secure by default" approach, meaning you get a default set of policies/configuration, but you can toggle those off as needed.
Still, it's best to verify things in a test/dev environment first.
1 Reply
The majority of features included within Purview need to be configured first, before they take effect in any given tenant. There are also some features that use a "secure by default" approach, meaning you get a default set of policies/configuration, but you can toggle those off as needed.
Still, it's best to verify things in a test/dev environment first.