Remember that these controls should be part of your holistic data security strategy in any case. However, if adopting M365 Copilot can serve as the catalyst to implement these controls in your organization, then take advantage of that opportunity and get them in place!

The collaboration of Microsoft Purview and M365 Copilot represents a significant advancement in the realm of AI-driven productivity tools when paired with robust security measures.

By applying sensitivity labels, businesses can control who has access to different types of information, reducing the risk of unauthorized data exposure.

A fundamental recommendation is using Sensitivity labels in Purview. These labels are crucial to maintaining data security and compliance, particularly when using AI tools like M365 Copilot.

It also allows you to set guardrails around the sensitive data in Azure SQL DB, ADLS Gen2 and Azure Blob Storage in addition to M365 assets and AWS S3 - it is a massive step up in capability, and well worth the investment it will take to get across it!

Now, for the update - this preview release enables Enterprise Admins to centrally define and manage cross cutting policies across data sources in a multi-cloud environment.

With that said, today we can identify sensitive information in data assets (think Azure Blob storage or an Azure SQL database) and apply sensitivity labels to those assets with the integration between automatic labelling and the data map.

With the portal convergence of these areas, I am hoping that customers can see and consider them as the one unifying solution - we aim to provide these governance capabilities across your entire environment, not just in silos.

To resolve this and to provide the ability to govern and protection your entire data estate in one place, we are combining both portals together to provide the one pane of glass you need to ensure data security across your ecosystem.

Learn about the new Microsoft Purview portal:

First up, the unified portal (take a note that it is in Preview), but you can likely already see the option to enable it. There has always been a lot of confusion as to why these are located in two different areas, one in Azure and the other in the M365 portal.