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/docs-conceptual/client-advanced-settings.md
+24-1Lines changed: 24 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: PowerShell advanced settings for Microsoft Purview Information Protection
3
3
ms.author: yangczhang
4
4
author: zhang-yangchen
5
5
manager: aashishr
6
-
ms.date: 04/15/2024
6
+
ms.date: 04/17/2024
7
7
ms.audience: Admin
8
8
audience: Admin
9
9
ms.topic: article
@@ -42,6 +42,7 @@ The advanced settings that are supported by sensitivity labels built into Micros
42
42
|[EnableGlobalization](#enableglobalization)|Turn on classification globalization features|
43
43
|[JustificationTextForUserText](#justificationtextforusertext)|Customize justification prompt texts for modified labels|
44
44
|[LogMatchedContent](#logmatchedcontent)|Send information type matches to Microsoft Purview|
45
+
|[OfficeContentExtractionTimeout](#officecontentextractiontimeout)|Configure the auto-labeling timeout for Office files|
45
46
|[PFileSupportedExtensions](#pfilesupportedextensions)|Change which file types to protect|
46
47
|[ReportAnIssueLink](#reportanissuelink)|Add "Report an Issue" for users|
47
48
|[ScannerMaxCPU](#scannermaxcpu)|Limit CPU consumption|
@@ -237,6 +238,27 @@ Example PowerShell command, where your label policy is named "Global":
237
238
Set-LabelPolicy -Identity Global -AdvancedSettings @{LogMatchedContent="True"}
238
239
```
239
240
241
+
## OfficeContentExtractionTimeout
242
+
243
+
By default, the scanner's auto-labeling timeout on Office files is 3 seconds.
244
+
245
+
If you have a complex Excel file with many sheets or rows, 3 seconds might not be enough to automatically apply labels. To increase this timeout for the selected label policy, specify the following strings:
246
+
247
+
- Key: **OfficeContentExtractionTimeout**
248
+
249
+
- Value: Seconds, in the following format: `hh:mm:ss`.
250
+
251
+
> [!IMPORTANT]
252
+
> We recommend that you don't raise this timeout to higher than 15 seconds.
253
+
254
+
Example PowerShell command, where your label policy is named "Global":
255
+
256
+
```PowerShell
257
+
Set-LabelPolicy -Identity Global -AdvancedSettings @{OfficeContentExtractionTimeout="00:00:15"}
258
+
```
259
+
260
+
The updated timeout applies to auto-labeling on all Office files.
261
+
240
262
## PFileSupportedExtensions
241
263
242
264
With this setting, you can change which file types are encrypted but you cannot change the default encryption level from native to generic. For example, for users running the file labeler, you can change the default setting so that only Office files and PDF files are encrypted instead of all file types. But you cannot change these file types to be generically encrypted with a .pfile file name extension.
@@ -284,6 +306,7 @@ Example PowerShell command, where your label policy is named "Global":
284
306
Set-LabelPolicy -Identity Global -AdvancedSettings @{ReportAnIssueLink="mailto:[email protected]"}
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/New-Label.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -167,7 +167,7 @@ The AdvancedSettings parameter enables specific features and capabilities for a
167
167
168
168
Specify this parameter with the identity (name or GUID) of the sensitivity label, with key/value pairs in a [hash table](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_hash_tables). To remove an advanced setting, use the same AdvancedSettings parameter syntax, but specify a null string value.
169
169
170
-
Some of the settings that you configure with this parameter are supported only by the Azure Information Protection unified labeling client and not by Office apps and services that support built-in labeling. For a list of these and instructions, see [Custom configurations for the Azure Information Protection unified labeling client](https://learn.microsoft.com/azure/information-protection/rms-client/clientv2-admin-guide-customizations).
170
+
Some of the settings that you configure with this parameter are supported only by the Microsoft Purview Information Protection client and not by Office apps and services that support built-in labeling. For a list of these, see [Advanced settings for Microsoft Purview Information Protection client](https://learn.microsoft.com/powershell/exchange/client-advanced-settings).
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/New-LabelPolicy.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -102,7 +102,7 @@ The AdvancedSettings parameter enables client-specific features and capabilities
102
102
103
103
Specify this parameter with the identity (name or GUID) of the policy, with key/value pairs in a [hash table](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_hash_tables). To remove an advanced setting, use the same AdvancedSettings parameter syntax, but specify a null string value.
104
104
105
-
Some of the settings that you configure with this parameter are supported only by the Azure Information Protection unified labeling client and not by Office apps that support built-in labeling. For instructions, see [Custom configurations for the Azure Information Protection unified labeling client](https://learn.microsoft.com/azure/information-protection/rms-client/clientv2-admin-guide-customizations).
105
+
Some of the settings that you configure with this parameter are supported only by the Microsoft Purview Information Protection client and not by Office apps and services that support built-in labeling. For a list of these, see [Advanced settings for Microsoft Purview Information Protection client](https://learn.microsoft.com/powershell/exchange/client-advanced-settings).
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/Set-Label.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -147,7 +147,7 @@ The AdvancedSettings parameter enables specific features and capabilities for a
147
147
148
148
Specify this parameter with the identity (name or GUID) of the sensitivity label, with key/value pairs in a [hash table](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_hash_tables). To remove an advanced setting, use the same AdvancedSettings parameter syntax, but specify a null string value.
149
149
150
-
Some of the settings that you configure with this parameter are supported only by the Azure Information Protection unified labeling client and not by Office apps and services that support built-in labeling. For a list of these and instructions, see [Custom configurations for the Azure Information Protection unified labeling client](https://learn.microsoft.com/azure/information-protection/rms-client/clientv2-admin-guide-customizations).
150
+
Some of the settings that you configure with this parameter are supported only by the Microsoft Purview Information Protection client and not by Office apps and services that support built-in labeling. For a list of these, see [Advanced settings for Microsoft Purview Information Protection client](https://learn.microsoft.com/powershell/exchange/client-advanced-settings).
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/Set-LabelPolicy.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -366,7 +366,7 @@ The AdvancedSettings parameter enables client-specific features and capabilities
366
366
367
367
Specify this parameter with the identity (name or GUID) of the policy, with key/value pairs in a [hash table](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_hash_tables). To remove an advanced setting, use the same AdvancedSettings parameter syntax, but specify a null string value.
368
368
369
-
Most of the settings that you configure with this parameter are supported only by the Azure Information Protection unified labeling client and not by Office apps that support built-in labeling. For instructions, see [Custom configurations for the Azure Information Protection unified labeling client](https://learn.microsoft.com/azure/information-protection/rms-client/clientv2-admin-guide-customizations).
369
+
Some of the settings that you configure with this parameter are supported only by the Microsoft Purview Information Protection client and not by Office apps and services that support built-in labeling. For a list of these, see [Advanced settings for Microsoft Purview Information Protection client](https://learn.microsoft.com/powershell/exchange/client-advanced-settings).
@@ -27,6 +27,11 @@ Each AA can be associated with phone numbers that allow callers to reach specifi
27
27
28
28
You can create new AAs by using the New-CsAutoAttendant cmdlet; each newly created AA gets assigned a random string that serves as the identity of the AA.
29
29
30
+
> [!CAUTION]
31
+
> The following configuration parameters are currently only available in PowerShell and do not appear in Teams admin center. Saving a call queue configuration through Teams admin center will _remove_ any of these configured items:
32
+
>
33
+
> - -HideAuthorizedUsers
34
+
30
35
**NOTES**:
31
36
32
37
- To setup your AA for calling, you need to create an application instance first using `New-CsOnlineApplicationInstance` cmdlet , then associate it with your AA configuration using `New-CsOnlineApplicationInstanceAssociation` cmdlet.
@@ -466,6 +471,40 @@ Accept pipeline input: False
466
471
Accept wildcard characters: False
467
472
```
468
473
474
+
### -AuthorizedUsers
475
+
This is a list of GUIDs for users who are authorized to make changes to this call queue. The users must also have a TeamsVoiceApplications policy assigned. The GUID should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
476
+
477
+
```yaml
478
+
Type: List
479
+
Parameter Sets: (All)
480
+
Aliases:
481
+
applicable: Microsoft Teams
482
+
483
+
Required: False
484
+
Position: Named
485
+
Default value: None
486
+
Accept pipeline input: False
487
+
Accept wildcard characters: False
488
+
```
489
+
490
+
### -HideAuthorizedUsers
491
+
_Saving a call queue configuration through Teams admin center will *remove* this setting._
492
+
493
+
This is a list of GUIDs of authorized users who should not appear on the list of supervisors for the agents who are members of this queue. The GUID should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
The NoAgentApplyTo parameter defines if the NoAgentAction applies to calls already in queue and new calls arriving to the queue, or only new calls that arrive once the No Agents condition occurs. The default value is AllCalls.
360
+
361
+
PARAMVALUE: AllCalls | NewCalls
362
+
363
+
```yaml
364
+
Type: Object
365
+
Parameter Sets: (All)
366
+
Aliases:
367
+
applicable: Microsoft Teams
368
+
369
+
Required: False
370
+
Position: Named
371
+
Default value: Disconnect
372
+
Accept pipeline input: False
373
+
Accept wildcard characters: False
374
+
```
375
+
358
376
### -NoAgentAction
359
377
The NoAgentAction parameter defines the action to take if the no agents condition is reached. The NoAgentAction property must be set to one of the following values: Queue, Disconnect, Forward, Voicemail, and SharedVoicemail. The default value is Queue.
The NoAgentRedirectPhoneNumberAudioFilePrompt parameter indicates the unique identifier for the Audio file prompt which is played to the caller when being redirected to an external PSTN phone number due to no agents.
A Teams Channel can only be linked to one Call Queue at a time. To force reassignment of the Teams Channel to a new Call Queue, set this to $true.
1507
+
1508
+
```yaml
1509
+
Type: Boolean
1510
+
Parameter Sets: (All)
1511
+
Aliases:
1512
+
1513
+
Required: False
1514
+
Position: Named
1515
+
Default value: False
1516
+
Accept pipeline input: False
1517
+
Accept wildcard characters: False
1518
+
```
1519
+
1486
1520
### CommonParameters
1487
1521
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
0 commit comments