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
This example creates a DLP policy named GlobalPolicy for the specified SharePoint Online and OneDrive for Business locations. The new policy has a descriptive comment and will be enabled on creation.
This example creates a DLP policy named PowerBIPolicy for all qualifying Power BI workspaces (that is, those hosted on Premium Gen2 capacities) except for the specified workspaces. The new policy has a descriptive comment and will be enabled on creation.
This example creates a DLP policy for Microsoft 365 Copilot (Preview) in several steps:
139
+
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
+
142
+
- The second command stores the GUID value of the sensitivity label in the variable named `$guidVar`.
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.
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).
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.
149
+
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 parameter specifies to whom, what, and where the DLP policy applies. This parameter uses the following properties:
485
+
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>}`.
490
+
491
+
You create and store the properties in a variable as shown in the following examples:
The Locations parameter specifies to whom, what, and where the DLP policy applies. This parameter uses the following properties:
747
+
748
+
- Workload: What the DLP policy applies to. Use the value `Applications`.
749
+
- Location: Where the DLP policy applies. For Microsoft 365 Copilot, (Preview), use the value `470f2276-e011-4e9d-a6ec-20768be3a4b0`.
750
+
- AddInclusions or RemoveInclusions: Add or remove security groups, distribution groups, or users to or from the scope of this DLP policy. 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>}`.
751
+
- AddExclusions or RemoveExclusions: Add or remove security groups, distribution groups, or users to or from exclusions to the scope of this DLP policy. 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>}`.
752
+
753
+
You create and store the properties in a variable as shown in the following examples:
>This feature has not been released yet and will have no changes if it is enabled or disabled.
170
+
171
+
Enables the user to use the AI Interpreter related features
172
+
173
+
Possible values:
174
+
175
+
- Disabled
176
+
- Enabled
177
+
178
+
```yaml
179
+
Type: String
180
+
Parameter Sets: (All)
181
+
Aliases:
182
+
Applicable: Microsoft Teams
183
+
184
+
Required: False
185
+
Position: Named
186
+
Default value: Enabled
187
+
Accept pipeline input: False
188
+
Accept wildcard characters: False
189
+
```
190
+
165
191
### -AllowAnonymousUsersToDialOut
166
192
Determines whether anonymous users are allowed to dial out to a PSTN number. Set this to TRUE to allow anonymous users to dial out. Set this to FALSE to #prohibit anonymous users from dialing out.
Controls how the join information in meeting invitations is displayed by enforcing a common language or enabling up to two languages to be displayed.
1404
-
Note: All Teams supported languages can be specified using language codes. For more information about its delivery date, see the [roadmap (Feature ID: 81521)](https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=81521).
1431
+
1432
+
> [!NOTE]
1433
+
> All Teams supported languages can be specified using language codes. For more information about its delivery date, see the [roadmap (Feature ID: 81521)](https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=81521).
1405
1434
1406
1435
The preliminary list of available languages is shown below:
Specifies the number of days before meeting recordings will expire and move to the recycle bin. Value can be from 1 to 99,999 days.
1425
1454
1426
-
NOTE: You may opt to set Meeting Recordings to never expire by entering the value -1.
1455
+
> [!NOTE]
1456
+
> You may opt to set Meeting Recordings to never expire by entering the value -1.
1427
1457
1428
1458
```yaml
1429
1459
Type: Int32
@@ -1516,7 +1546,8 @@ This parameter can take two possible values:
1516
1546
- Stream
1517
1547
- OneDriveForBusiness
1518
1548
1519
-
Note: The change of storing Teams meeting recordings from Classic Stream to OneDrive and SharePoint (ODSP) has been completed as of August 30th, 2021. All recordings are now stored in ODSP. This change overrides the RecordingStorageMode parameter, and modifying the setting in PowerShell no longer has any impact.
1549
+
> [!Note]
1550
+
> The change of storing Teams meeting recordings from Classic Stream to OneDrive and SharePoint (ODSP) has been completed as of August 30th, 2021. All recordings are now stored in ODSP. This change overrides the RecordingStorageMode parameter, and modifying the setting in PowerShell no longer has any impact.
Enabling people recognition requires the tenant CsTeamsMeetingPolicy roomPeopleNameUserOverride to be "On" and roomAttributeUserOverride to be Attribute for allowing individual voice and face profiles to be used for recognition in meetings.
1554
-
**Note**: In some locations, people recognition can't be used due to local laws or regulations.
1585
+
1586
+
> [!Note]
1587
+
> In some locations, people recognition can't be used due to local laws or regulations.
0 commit comments