MicrosoftEchoing everyone else's confusion here but hopefully offering a small glimmer of light.
This could have all been avoided is this blog post had a simple table saying something like
"If you use WIP for Feature XXX then migrate to Feature YYY"
For Pavel Otych & David_Swenson (and others!) you can restrict copy and paste from M365 files using Office 365 App Security (included in E3) https://docs.microsoft.com/en-us/defender-cloud-apps/editions-cloud-app-security-o365
For the other things you mention Pavel, I'm not sure if there will be anything simple to move to that wouldn't increase cost of complexity (Personal/Work separation, App Control, Defender for Endpoint, 3rd party cloud proxy - e.g. Zscaler).
Seamus Mc Bride The "Apache Atlas" link to Purview is only for the Data Catlog feature which is related to Azure databases, not M365. Microsoft rebranded everything to do with data governance/compliance to Purview, including the Microsoft Information Protection and DLP features mentioned in this post.
More bad news that is not in the post (and I think Rafal_Sosnowski should update) is that there is a deadline for WIP-WE:
We will remove support for WIPwithout enrollmentscenario by the end of calendar year 2022 (Source)
There is slightly more information on how to remove WIP here but it doens't help with what to migrate to
