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 cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
15
+
16
+
Use the Export-PurviewConfig cmdlet to export Microsoft Purview diagnostic configuration data for your organization. The exported data is returned as a compressed ZIP file (byte array) containing component-specific diagnostic information.
17
+
18
+
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
This cmdlet exports Purview diagnostic data for specified components in your organization. The data is returned as a ZIP archive (binary-encoded byte array) for each component. Each file contains the diagnostic configuration data for the component in a structured format.
34
+
35
+
The exported data is useful for troubleshooting and diagnostics of Purview configuration issues across DLP, MIP Labels, Classification, and Data Lifecycle Management.
36
+
37
+
You need to be assigned permissions in the Security & Compliance before you can use this cmdlet. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions).
38
+
39
+
## EXAMPLES
40
+
41
+
### Example 1
42
+
```powershell
43
+
Export-PurviewConfig -Components DLP
44
+
```
45
+
46
+
This example exports diagnostic configuration data for the DLP component.
This example exports diagnostic data for the DLP and MIPLabels components and saves the resulting ZIP file to disk.
56
+
57
+
## PARAMETERS
58
+
59
+
### -Components
60
+
61
+
> Applicable: Security & Compliance
62
+
63
+
The Components parameter specifies which Purview components to export diagnostic data for. Valid values are:
64
+
65
+
- ClassificationAndTextExtraction
66
+
- DLM
67
+
- DLP
68
+
- MIPLabels
69
+
70
+
You can specify multiple values separated by commas.
71
+
72
+
**Note**: If you specify an unsupported component value, a warning is logged and the component is skipped.
73
+
74
+
```yaml
75
+
Type: MultiValuedProperty
76
+
Parameter Sets: (All)
77
+
Aliases:
78
+
79
+
Required: True
80
+
Position: Named
81
+
Default value: None
82
+
Accept pipeline input: False
83
+
Accept wildcard characters: False
84
+
```
85
+
86
+
### -Confirm
87
+
88
+
> Applicable: Security & Compliance
89
+
90
+
The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
91
+
92
+
- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
93
+
- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.
94
+
95
+
```yaml
96
+
Type: SwitchParameter
97
+
Parameter Sets: (All)
98
+
Aliases: cf
99
+
100
+
Required: False
101
+
Position: Named
102
+
Default value: None
103
+
Accept pipeline input: False
104
+
Accept wildcard characters: False
105
+
```
106
+
107
+
### -DomainController
108
+
109
+
> Applicable: Security & Compliance
110
+
111
+
This parameter is reserved for internal Microsoft use.
112
+
113
+
```yaml
114
+
Type: Fqdn
115
+
Parameter Sets: (All)
116
+
Aliases:
117
+
118
+
Required: False
119
+
Position: 1
120
+
Default value: None
121
+
Accept pipeline input: False
122
+
Accept wildcard characters: False
123
+
```
124
+
125
+
### -PolicyName
126
+
127
+
> Applicable: Security & Compliance
128
+
129
+
The PolicyName parameter specifies the name of the policy to scope the export to.
130
+
131
+
```yaml
132
+
Type: String
133
+
Parameter Sets: (All)
134
+
Aliases:
135
+
136
+
Required: False
137
+
Position: 2
138
+
Default value: None
139
+
Accept pipeline input: False
140
+
Accept wildcard characters: False
141
+
```
142
+
143
+
### -UserPrincipalName
144
+
145
+
> Applicable: Security & Compliance
146
+
147
+
The UserPrincipalName parameter specifies the user principal name (UPN) of the user to scope the export to.
148
+
149
+
```yaml
150
+
Type: SmtpAddress
151
+
Parameter Sets: (All)
152
+
Aliases:
153
+
154
+
Required: False
155
+
Position: 3
156
+
Default value: None
157
+
Accept pipeline input: False
158
+
Accept wildcard characters: False
159
+
```
160
+
161
+
### -WhatIf
162
+
163
+
> Applicable: Security & Compliance
164
+
165
+
The WhatIf switch doesn't work in Security & Compliance PowerShell.
166
+
167
+
```yaml
168
+
Type: SwitchParameter
169
+
Parameter Sets: (All)
170
+
Aliases: wi
171
+
172
+
Required: False
173
+
Position: Named
174
+
Default value: None
175
+
Accept pipeline input: False
176
+
Accept wildcard characters: False
177
+
```
178
+
179
+
### CommonParameters
180
+
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](http://go.microsoft.com/fwlink/p/?LinkID=113216).
This parameter is available only in the cloud-based service.
452
453
453
-
The AllowedOrganizationAccountDomains parameter specifies domains where users can add work or school email accounts in the new Outlook for Windows. The default value is blank ($null), which allows work or school accounts from any domain. Setting this parameter to an empty list ([]) prevents any work or school accounts from being added.
454
+
The AllowedOrganizationAccountDomains parameter specifies domains where users can add work or school email accounts in Outlook (formerly known as the new Outlook for Windows). The default value is blank ($null), which allows work or school accounts from any domain. Setting this parameter to an empty list ([]) prevents any work or school accounts from being added.
454
455
455
456
```yaml
456
457
Type: String[]
@@ -490,6 +491,35 @@ Accept pipeline input: False
490
491
Accept wildcard characters: False
491
492
```
492
493
494
+
### -AttachmentsOfflineEnabledWin
495
+
496
+
> Applicable: Exchange Online
497
+
498
+
This parameter is available only in the cloud-based service.
499
+
500
+
The AttachmentsOfflineEnabledWin parameter specifies whether file attachments are available for offline use in Outlook (formerly known as the new Outlook for Windows).
501
+
502
+
This parameter only applies when offline capabilities are enabled in Outlook.
503
+
504
+
Valid values are:
505
+
506
+
- $true: Users can access file attachments while working offline in Outlook. This value is the default.
507
+
- $false: Users can't access file attachments while working offline in Outlook.
508
+
509
+
**Note**: If the OfflineEnabledWin parameter is set to $false, offline file attachments are disabled even if AttachmentsOfflineEnabledWin is set to $true.
This parameter is available only in the cloud-based service.
689
719
690
-
The ChangeSettingsAccountEnabled parameter specifies whether users can change the email account where app-wide settings (for example, theme and privacy settings) are associated in the new Outlook for Windows. Valid values are:
720
+
The ChangeSettingsAccountEnabled parameter specifies whether users can change the email account where app-wide settings (for example, theme and privacy settings) are associated in Outlook (formerly known as the new Outlook for Windows). Valid values are:
691
721
692
-
- $true: Users can change their settings account in the new Outlook for Windows. This value is the default.
693
-
- $false: Users can't change their settings account in the new Outlook for Windows.
722
+
- $true: Users can change their settings account in Outlook. This value is the default.
723
+
- $false: Users can't change their settings account in Outlook.
694
724
695
-
**Note**: The settings account is referred to as the primary account in the new Outlook for Windows setting at Settings \> Accounts \> Email accounts \> Manage.
725
+
**Note**: The settings account is referred to as the primary account in the Outlook setting at Settings \> Accounts \> Email accounts \> Manage.
This parameter is available only in the cloud-based service.
1788
1818
1789
-
The OfflineEnabledWin parameter specifies whether offline capabilities are available in the new Outlook for Windows, including saving items to the local device (view items without an internet connection). Valid values are:
1819
+
The OfflineEnabledWin parameter specifies whether offline capabilities are available in Outlook (formerly known as the new Outlook for Windows), including saving items to the local device (view items without an internet connection). Valid values are:
1790
1820
1791
-
- $true: Users can manage offline capabilities in the new Outlook for Windows. This value is the default.
1792
-
- $false: Users can't manage offline capabilities in the new Outlook for Windows. No items are saved to the user's device. Previously save items are deleted.
1821
+
- $true: Users can manage offline capabilities in Outlook. This value is the default.
1822
+
- $false: Users can't manage offline capabilities in Outlook. No items are saved to the user's device. Previously save items are deleted.
1793
1823
1794
-
When offline capabilities are available, users can turn offline capabilities on or off themselves in the New Outlook for Windows at Settings \> General \> Offline. By default, offline capabilities are turned on.
1824
+
When offline capabilities are available, users can turn offline capabilities on or off themselves in the Outlook at Settings \> General \> Offline. By default, offline capabilities are turned on.
This parameter is available only in the cloud-based service.
1833
1863
1834
-
The OneWinNativeOutlookEnabled parameter controls the availability of the new Outlook for Windows App. Valid values are:
1864
+
The OneWinNativeOutlookEnabled parameter controls the availability of Outlook (formerly known as the new Outlook for Windows). Valid values are:
1835
1865
1836
-
- $true: The New Outlook for Windows App is available. This value is the default.
1837
-
- $false: The new Outlook for Windows App isn't available.
1866
+
- $true: The Outlook app is available. This value is the default.
1867
+
- $false: The Outlook App isn't available.
1838
1868
1839
1869
```yaml
1840
1870
Type: System.Boolean
@@ -1939,7 +1969,7 @@ This parameter is available only in the cloud-based service.
1939
1969
1940
1970
The OutlookNewslettersAccessLevelAccess parameter specifies the access level in Outlook Newsletters. Valid values are:
1941
1971
1942
-
- NoAccess: No access to Outlook Newsletters in the New Outlook for Windows or Outlook on the web. Users can still read email messages sent or forwarded to them.
1972
+
- NoAccess: No access to Outlook Newsletters in Outlook (formerly known as the new Outlook for Windows) or Outlook on the web. Users can still read email messages sent or forwarded to them.
1943
1973
- ReadOnly: Read newsletters and browse pages in Outlook Newsletters.
1944
1974
- ReadWrite: Full authoring permissions to create pages and newsletters in Outlook Newsletters.
1945
1975
- Undefined: This value is the default. Currently, this value is equivalent to NoAccess.
This parameter is available only in the cloud-based service.
1964
1994
1965
-
The OutlookDataFile parameter specifies what users can do with .pst files in the new Outlook for Windows. Valid values are:
1995
+
The OutlookDataFile parameter specifies what users can do with .pst files in Outlook (formerly known as the new Outlook for Windows). Valid values are:
1966
1996
1967
1997
- Allow: The default value. Users can open .pst files, import from a .pst file to a mailbox, export from a mailbox to a .pst file, and copy items to and from .pst files.
1968
1998
- NoExport: Users can't export from a mailbox to a .pst file.
This parameter is available only in the cloud-based service.
2110
2140
2111
-
The PersonalAccountsEnabled parameter specifies whether to allow users to add their personal accounts (for example, Outlook.com, Gmail, or Yahoo!) in the new Outlook for Windows. Valid values are:
2141
+
The PersonalAccountsEnabled parameter specifies whether to allow users to add their personal accounts (for example, Outlook.com, Gmail, or Yahoo!) in Outlook (formerly known as the new Outlook for Windows). Valid values are:
2112
2142
2113
-
- $true: Users can add their personal accounts in the new Outlook for Windows. This value is the default.
2114
-
- $false: Users can't add their personal accounts in the new Outlook for Windows.
2143
+
- $true: Users can add their personal accounts in Outlook. This value is the default.
2144
+
- $false: Users can't add their personal accounts in Outlook.
> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
110
110
111
-
The OWAAllowUserChoiceOfSigningCertificate parameter specifies whether to allow users to select the certificate to use when they digitally sign email messages in Outlook on the web.
111
+
The OWAAllowUserChoiceOfSigningCertificate parameter specifies whether to allow users to select the certificate to use when they digitally sign email messages in Outlook on the web. Valid values are:
112
112
113
-
Valid input for this parameter is $true or $false. The default value is $false.
113
+
- $true: Users can manually select the certificate that's used to sign messages.
114
+
- $false: Outlook on the web automatically selects the signing certificate. The eligible S/MIME certificate with the most recent NotBefore value is used. The NotBefore value is evaluated as a full date and time value, with comparison precision up to seconds. Certificates issued on the same day are still differentiated if their NotBefore values differ by time. If two or more eligible certificates have the same NotBefore timestamp at seconds precision, the certificate that's selected is unspecified and isn't guaranteed to be the same across signing operations. This behavior is the default.
0 commit comments