You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/New-DlpCompliancePolicy.md
+21-10Lines changed: 21 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -139,13 +139,13 @@ This example creates a DLP policy for Microsoft 365 Copilot (Preview) in several
139
139
140
140
- The first command returns information about all sensitivity labels. Select the GUID value of the sensitivity label that you want to use. For example, `e222b65a-b3a8-46ec-ae12-00c2c91b71c0`.
141
141
142
-
- The second command stores the GUID value of the sensitivity label in the variable named $guidVar.
142
+
- The second command stores the GUID value of the sensitivity label in the variable named `$guidVar`.
143
143
144
-
- The third command stores the Microsoft 365 Copilot location (470f2276-e011-4e9d-a6ec-20768be3a4b0) in the variable named $loc. Update the $loc value based on the Inclusions/Exclusions scoping that you want to provide.
144
+
- The third command stores the Microsoft 365 Copilot location (`470f2276-e011-4e9d-a6ec-20768be3a4b0`) in the variable named `$loc`. Update the `$loc` value based on the Inclusions/Exclusions scoping that you want to provide.
145
145
146
-
- The fourth command creates the DLP policy using the $loc variable for the value of the Locations parameter, and "Copilot Policy" as the name of the policy (use any unique name).
146
+
- The fourth command creates the DLP policy using the `$loc` variable for the value of the Locations parameter, and "Copilot Policy" as the name of the policy (use any unique name).
147
147
148
-
- The fifth command creates the variable named $advRule. The advanced rule needs to be updated depending on the grouping of labels you want to provide as input.
148
+
- The fifth command creates the variable named `$advRule`. The advanced rule needs to be updated depending on the grouping of labels you want to provide as input.
149
149
150
150
- The last command creates the DLP rule with the name "Copilot Rule" (use any unique name). Use the name of the DLP policy from step four as the value of the Policy parameter.
The Locations param specifies the workload, location, and security groups, distribution groups, or users that the DLP policy applies to. You can use this parameter with the following properties:
484
+
The Locations parameter specifies to who, what, and where the DLP policy applies. This parameter uses the following properties:
485
485
486
-
- Workload: Workloads where DLP policy should apply to. Set the value to Applications.
487
-
- Location: Specific locations where DLP policy should apply to. For Microsoft 365 Copilot location (Preview), use the value 470f2276-e011-4e9d-a6ec-20768be3a4b0.
488
-
- Inclusions: Add security groups, distribution list or individuals to the scope of this DLP policy.
486
+
- Workload: What the DLP policy applies to. Use the value `Applications`.
487
+
- Location: Where the DLP policy applies. For Microsoft 365 Copilot, (Preview), use the value `470f2276-e011-4e9d-a6ec-20768be3a4b0`.
488
+
- Inclusions: Who the DLP policy applies to. For users, use the email address in this syntax: `{Type:IndividualResource,Identity:<EmailAddress>}`. For security groups or distribution groups, use the ObjectId value of the group from the Microsoft Entra portal in this syntax: `{Type:Group,Identity:<ObjectId>}`. For the entire tenant, use this value: `{Type:"Tenant",Identity:"All"}`.
489
+
- Exclusions: Exclude security groups, distribution groups, or users from the scope of this DLP policy. For users, use the email address in this syntax: `{Type:IndividualResource,Identity:<EmailAddress>}`. For groups, use the ObjectId value of the group from the Microsoft Entra portal in this syntax: `{Type:Group, Identity:<ObjectId>}`.
489
490
490
-
For example:
491
+
You create and store the properties in a variable as shown in the following examples:
0 commit comments