Skip to content

Commit e08c785

Browse files
committed
Update New-DlpCompliancePolicy.md
Locations parameter updates per TR
1 parent 72095e4 commit e08c785

File tree

1 file changed

+21
-10
lines changed

1 file changed

+21
-10
lines changed

exchange/exchange-ps/exchange/New-DlpCompliancePolicy.md

Lines changed: 21 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -139,13 +139,13 @@ This example creates a DLP policy for Microsoft 365 Copilot (Preview) in several
139139

140140
- 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`.
141141

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`.
143143

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.
145145

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).
147147

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.
149149

150150
- 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.
151151

@@ -481,17 +481,28 @@ Accept wildcard characters: False
481481
```
482482

483483
### -Locations
484-
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:
485485

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>}`.
489490

490-
For example:
491+
You create and store the properties in a variable as shown in the following examples:
492+
493+
DLP policy scoped to all users in the tenant:
491494

492495
`$loc = "[{"Workload":"Applications","Location":"470f2276-e011-4e9d-a6ec-20768be3a4b0","Inclusions":[{Type:"Tenant",Identity:"All"}]}]"`
493496

494-
And then use the value $loc for this parameter.
497+
DLP policy scoped to the specified user and groups:
498+
499+
`$loc = "[{"Workload":"Applications","Location":"470f2276-e011-4e9d-a6ec-20768be3a4b0","Inclusions":[{"Type":"Group","Identity":"fef0dead-5668-4bfb-9fc2-9879a47f9bdb"},{"Type":"Group","Identity":"b4dc1e1d-8193-4525-b59c-6d6e0f1718d2"},{"Type":"IndividualResource","Identity":"[email protected]"}]}]"`
500+
501+
DLP policy scoped to all users in the tenant except for members of the specified group:
502+
503+
`$loc = "[{"Workload":"Applications","Location":"470f2276-e011-4e9d-a6ec-20768be3a4b0","Inclusions":[{Type:"Tenant",Identity:"All"}]}],"Exclusions":[{"Type":"Group","Identity":"fef0dead-5668-4bfb-9fc2-9879a47f9bdb"}]}]"`
504+
505+
After you create the `$loc` variable, use the value `$loc` for this parameter.
495506

496507
```yaml
497508
Type: String

0 commit comments

Comments
 (0)