Purview DLP policy not applying to meeting requests sent from MS Teams

curious7 151 Reputation points
2024-06-19T13:02:51.0533333+00:00

We have a Purview DLP policy that was originally applied to exchange location and applied to mail enabled security group. The users in these groups get the policy applied successfully and MS Teams meeting invite without classification label gets blocked.

Then we added few more M365 groups to this DLP policy. But the users in these M365 groups are not getting the policy and the MS Teams meeting invite without classification label can still be sent successfully by users in these M365 groups.

I looked at the exchange trace log for invite sent by one of these users and see the invite does not match any DLP rule and is thus sent. For a meeting invite from user in the mail enabled group the rule matches and it is blocked.

Are M365 groups not supported for this type of DLP policy?

What other logs or steps I can take to resolve this?

Microsoft 365
Microsoft 365
Formerly Office 365, is a line of subscription services offered by Microsoft which adds to and includes the Microsoft Office product line.
4,197 questions
Microsoft Exchange Online
Microsoft Purview
Microsoft Purview
A Microsoft data governance service that helps manage and govern on-premises, multicloud, and software-as-a-service data. Previously known as Azure Purview.
1,020 questions
{count} votes

1 answer

Sort by: Most helpful
  1. BhargavaGunnam-MSFT 28,446 Reputation points Microsoft Employee
    2024-06-19T20:14:19.1+00:00

    Hello curious7,

    You can apply DLP policies to M365 groups

    Can you check the below to troubleshoot the issue.

    Please ensure that the M365 groups are correctly added to the policy and that there are no exclusions or conditions that might be preventing the policy from being applied.

    Consider checking the Endpoint DLP Settings, especially the "Browser and Domain restrictions to sensitive data" option

    also, confirm that the account creating and deploying policies has the necessary permissions.

    0 comments No comments