Skip to content

Commit c227bd3

Browse files
authored
Merge branch 'main' into patch-26
2 parents 92e725f + ab2b509 commit c227bd3

File tree

69 files changed

+3365
-443
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

69 files changed

+3365
-443
lines changed

exchange/docs-conceptual/client-advanced-settings.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -429,7 +429,7 @@ To ensure that the NTFS owner value is preserved, set the *UseCopyAndPreserveNTF
429429
> [!CAUTION]
430430
> For the scanner: Define this advanced setting only when you can ensure a low-latency, reliable network connection between the scanner and the scanned repository. A network failure during the automatic labeling process can cause the file to be lost.
431431
432-
Example PowerShell command, where your label policy is named "Scanner"
432+
Example PowerShell command, where your label policy is named "Global"
433433

434434
```PowerShell
435435
Set-LabelPolicy -Identity Global -AdvancedSettings @{UseCopyAndPreserveNTFSOwner ="true"}
Lines changed: 225 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,225 @@
1+
---
2+
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
3+
online version: https://learn.microsoft.com/powershell/module/exchange/invoke-compliancesecurityfilteraction
4+
applicable: Security & Compliance
5+
title: Invoke-ComplianceSecurityFilterAction
6+
schema: 2.0.0
7+
author: chrisda
8+
ms.author: chrisda
9+
ms.reviewer:
10+
---
11+
12+
# Invoke-ComplianceSecurityFilterAction
13+
14+
## SYNOPSIS
15+
This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
16+
17+
Use the Invoke-ComplianceSecurityFilterAction cmdlet to view and set compliance boundaries for Microsoft OneDrive sites in cloud-based organizations.
18+
19+
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
20+
21+
## SYNTAX
22+
23+
```
24+
Invoke-ComplianceSecurityFilterAction [-Action] <String> [-PropertyName] <String> [[-PropertyValue] <String>] [-SiteUrl] <String>
25+
[-Confirm]
26+
[-WhatIf]
27+
[<CommonParameters>]
28+
```
29+
30+
## DESCRIPTION
31+
This cmdlet is useful in scenarios where the OneDrive site has fallen out of the compliance boundary due to a departed user and a corresponding inactive mailbox.
32+
33+
To use this cmdlet in Security & Compliance PowerShell, you need to be a member of the Compliance Administrator role group. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions).
34+
35+
## EXAMPLES
36+
37+
### Example 1
38+
```powershell
39+
PS C:\> Invoke-ComplianceSecurityFilterAction -Action GetStatus -PropertyName CustomAttribute1 -SiteUrl https://contoso-my.sharepoint.com/personal/lila_contoso_onmicrosoft_com/_layouts/15/onedrive.aspx
40+
41+
SiteUrlOrEmailAddress : https://contoso-my.sharepoint.com/personal/lila_contoso_onmicrosoft_com/_layouts/15/onedrive.aspx
42+
BoundaryType : UserMailbox
43+
BoundaryInstruction : Set via Set-Mailbox
44+
BoundaryObjectId : SPO_f82ace6e-817e-4752-8917-67164dabde98@SPO_775ea11f-a2af-7821-b04c-9848e903ce47
45+
BoundaryStatus : Success
46+
BoundaryProperty : CustomAttribute1
47+
BoundaryPropertyValue :
48+
```
49+
50+
This example returns the status of a OneDrive site to indicate it's associated to a UserMailbox and the CustomAttribute1 property isn't currently set.
51+
52+
### Example 2
53+
```powershell
54+
PS C:\> Invoke-ComplianceSecurityFi1terAction Action GetStatus -PropertyName "CustomAttribute3" -EmailAddress "nina@contoso.onmicrosoft.com"
55+
56+
SiteUrlOrEmailAddress : nina@contoso.onmicrosoft.com
57+
BoundaryType : UserMailbox
58+
BoundaryInstruction : Set via Set-Mailbox
59+
BoundaryObjectId : nina@contoso.onmicrosoft.com
60+
BoundaryStatus : Success
61+
BoundaryProperty : CustomAttribute3
62+
BoundaryPropertyVa1ue :
63+
```
64+
65+
This example returns the status of a mailbox to indicate the mailbox is inactive, and the CustomAttribute3 property isn't currently set.
66+
67+
### Example 3
68+
```powershell
69+
PS C:\> Invoke-ComplianceSecurityFi1terAction -Action GetStatus -PropertyName "CustomAttribute3" -EmailAddress "zhexuan@contoso.onmicrosoft.com"
70+
71+
SiteUrlOrEmailAddress : zhexuan@contoso.onmicrosoft.com
72+
BoundaryType : InactiveMailbox
73+
BoundaryInstruction : Set via Invoke-ComplianceSecurityFiIterAction -Set
74+
BoundaryObjectId : zhexuan@contoso.onmicrosoft.com
75+
BoundaryStatus : Success
76+
BoundaryProperty : CustomAttribute3
77+
BoundaryPropertyVa1ue : test33
78+
```
79+
80+
This example returns the status of a mailbox to indicate the mailbox is inactive, and the CustomAttribute3 property is currently set to test33.
81+
82+
### Example 4
83+
```powershell
84+
Invoke-ComplianceSecurityFilterAction -Action Set -PropertyName CustomAttribute1 -PropertyValue "Research and Development" -SiteUrl https://contoso-my.sharepoint.com/personal/lila_contoso_onmicrosoft_com/_layouts/15/onedrive.aspx
85+
```
86+
87+
This example sets the boundary of the specified OneDrive site for a user who left the company.
88+
89+
### Example 5
90+
```powershell
91+
PS C:\> Invoke-ComplianceSecurityFiIterAction -Action Set -PropertyName "CustomAttribute3" -PropertyValue "ProjectX" -EmailAddress "zhexuan@contoso.onmicrosoft.com"
92+
93+
Set action succeeded, please use GetStatus to check the result.
94+
95+
PS C:\> Invoke-ComplianceSecurityFiIterAction -Action GetStatus -PropertyName "CustomAttribute3" -EmailAddress "zhexuan@contoso.onmicrosoft.com"
96+
97+
SiteUrlOrEmailAddress : zhexuan@contoso.onmicrosoft.com
98+
BoundaryType : InactiveMailbox
99+
BoundaryInstruction : Set via Invoke-ComplianceSecurityFiIterAction -Set
100+
BoundaryObjectId : zhexuan@contoso.onmicrosoft.com
101+
BoundaryStatus : Success
102+
BoundaryProperty : CustomAttribute3
103+
BoundaryPropertyVa1ue : ProjectX
104+
```
105+
106+
This example sets the boundary of the specified OneDrive site to the specified CustomAttribute3 property value, and runs another command to review the result.
107+
108+
## PARAMETERS
109+
110+
### -Action
111+
The Action parameter specifies the action for the command. Valid values are:
112+
113+
- GetStatus
114+
- Set
115+
116+
```yaml
117+
Type: String
118+
Parameter Sets: (All)
119+
Aliases:
120+
Applicable: Security & Compliance
121+
122+
Required: True
123+
Position: 1
124+
Default value: None
125+
Accept pipeline input: False
126+
Accept wildcard characters: False
127+
```
128+
129+
### -PropertyName
130+
The PropertyName parameter specifies the name of the property of the compliance boundary for the OneDrive site that you want to view or modify. Valid values are:
131+
132+
- CustomAttribute1 to CustomAttribute15
133+
134+
Use the PropertyValue parameter to set the compliance boundary.
135+
136+
```yaml
137+
Type: String
138+
Parameter Sets: (All)
139+
Aliases:
140+
Applicable: Security & Compliance
141+
142+
Required: True
143+
Position: 2
144+
Default value: None
145+
Accept pipeline input: False
146+
Accept wildcard characters: False
147+
```
148+
149+
### -PropertyValue
150+
The PropertyValue parameter specifies the value of the PropertyName value when you use the Action parameter value Set to set the compliance boundary of a OneDrive site. If the value contains spaces, enclose the value in quotation marks (").
151+
152+
```yaml
153+
Type: String
154+
Parameter Sets: (All)
155+
Aliases:
156+
Applicable: Security & Compliance
157+
158+
Required: False
159+
Position: 3
160+
Default value: None
161+
Accept pipeline input: False
162+
Accept wildcard characters: False
163+
```
164+
165+
### -SiteUrl
166+
The SiteUrl parameter specifies the OneDrive site that you want to view or modify. This parameter uses the syntax `https://<domain>-my.sharepoint.com/personal/<user>_<domain>_onmicrosoft_com/_layouts/15/onedrive.aspx`. For example: `https://contoso-my.sharepoint.com/personal/lila_contoso_onmicrosoft_com/_layouts/15/onedrive.aspx`.
167+
168+
```yaml
169+
Type: String
170+
Parameter Sets: (All)
171+
Aliases:
172+
Applicable: Security & Compliance
173+
174+
Required: True
175+
Position: 4
176+
Default value: None
177+
Accept pipeline input: False
178+
Accept wildcard characters: False
179+
```
180+
181+
### -Confirm
182+
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.
183+
184+
- 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`.
185+
- 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.
186+
187+
```yaml
188+
Type: SwitchParameter
189+
Parameter Sets: (All)
190+
Aliases: cf
191+
Applicable: Security & Compliance
192+
193+
Required: False
194+
Position: Named
195+
Default value: None
196+
Accept pipeline input: False
197+
Accept wildcard characters: False
198+
```
199+
200+
### -WhatIf
201+
The WhatIf switch doesn't work in Security & Compliance PowerShell.
202+
203+
```yaml
204+
Type: SwitchParameter
205+
Parameter Sets: (All)
206+
Aliases: wi
207+
Applicable: Security & Compliance
208+
209+
Required: False
210+
Position: Named
211+
Default value: None
212+
Accept pipeline input: False
213+
Accept wildcard characters: False
214+
```
215+
216+
### CommonParameters
217+
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/p/?LinkID=113216).
218+
219+
## INPUTS
220+
221+
## OUTPUTS
222+
223+
## NOTES
224+
225+
## RELATED LINKS

exchange/exchange-ps/exchange/New-AddressBookPolicy.md

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -115,7 +115,19 @@ Accept wildcard characters: False
115115
```
116116
117117
### -RoomList
118-
The RoomList parameter specifies the room address list that will be used by mailbox users who are assigned this address book policy. You can specify only one room list for each address book policy.
118+
The RoomList parameter specifies an address list that used for location experiences for mailbox users who have this address book policy assigned to them.
119+
120+
- When using location experiences (for example, Room Finder or selecting a conference room when scheduling a meeting), users see only resources that match the [RecipientFilter](https://learn.microsoft.com/powershell/module/exchange/new-addresslist#-recipientfilter) results from the address list that's specified by this parameter.
121+
- When using experiences that aren't location specific (for example, the To or Cc fields of a calendar event), the address lists specified by the AddressLists parameter in this address book policy are applied. The address list specified by this parameter isn't used.
122+
123+
A valid value for this parameter is one address list. You can use any value that uniquely identifies the address list. For example:
124+
125+
- Name
126+
- Distinguished name (DN)
127+
- GUID
128+
129+
> [!NOTE]
130+
> There's no automatic association between this parameter and [room list distribution groups](https://learn.microsoft.com/exchange/recipients/room-mailboxes#create-a-room-list), which also use a parameter named RoomList in the New-DistributionGroup and Set-DistributionGroup cmdlets. You still need to create room list distribution groups and assign resources as group members. Location experiences are filtered to show only rooms included in the address list that's specified by the RoomList property of the address book policy that's assigned to the user (if any).
119131
120132
```yaml
121133
Type: AddressListIdParameter

exchange/exchange-ps/exchange/New-DistributionGroup.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -304,7 +304,7 @@ The HiddenGroupMembershipEnabled switch specifies whether to hide the members of
304304

305305
You can use this setting to help comply with regulations that require you to hide group membership from members or outsiders (for example, a distribution group that represents students enrolled in a class).
306306

307-
**Note**: You can't change this setting after you create the group. If you create the group with hidden membership, you can't edit the group later to reveal the membership to the group, or vice-versa.
307+
**Note**: If you create the group with hidden membership, you can't edit the group later to reveal the membership to the group.
308308

309309
```yaml
310310
Type: SwitchParameter

exchange/exchange-ps/exchange/New-InboundConnector.md

Lines changed: 14 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ Accept wildcard characters: False
9292
```
9393
9494
### -SenderDomains
95-
The SenderDomains parameter specifies the source domains that the connector accepts messages for. A valid value is an SMTP domain. Wildcards are supported to indicate a domain and all subdomains (for example, \*.contoso.com), but you can't embed the wildcard character (for example, domain.\*.contoso.com is not valid).
95+
The SenderDomains parameter specifies the source domains that a Partner type connector accepts messages for (limits the scope of a Partner type connector). A valid value is an SMTP domain. Wildcards are supported to indicate a domain and all subdomains (for example, `*.contoso.com`). However, you can't embed the wildcard character (for example, `domain.*.contoso.com` isn't valid).
9696

9797
You can specify multiple domains separated by commas.
9898

@@ -227,7 +227,7 @@ Accept wildcard characters: False
227227
The ConnectorType parameter specifies the category for the source domains that the connector accepts messages for. Valid values are:
228228

229229
- Partner: External partners or services.
230-
- OnPremises: Your on-premises email organization. Use this value for accepted domains in your cloud-based organization that are also specified by the SenderDomains parameter.
230+
- OnPremises: The connector services domains that are used by your on-premises organization. OnPremises connectors grant special rights to an email that matches the connector and additional requirements. For example: allowing relay through the tenant to internet destinations, promoting emails from on-premises or other environments as internal (in a hybrid configuration), or enabling other more complex mail flows.
231231

232232
```yaml
233233
Type: TenantConnectorType
@@ -353,11 +353,13 @@ Accept wildcard characters: False
353353
```
354354

355355
### -RequireTls
356-
The RequireTLS parameter specifies whether to require TLS transmission for all messages that are received by the connector. Valid values are:
356+
The RequireTLS parameter specifies whether to require TLS transmission for all messages that are received by a Partner type connector. Valid values are:
357357

358358
- $true: Reject messages if they aren't sent over TLS. This is the default value
359359
- $false: Allow messages if they aren't sent over TLS.
360360

361+
**Note**: This parameter applies only to Partner type connectors.
362+
361363
```yaml
362364
Type: Boolean
363365
Parameter Sets: (All)
@@ -372,11 +374,13 @@ Accept wildcard characters: False
372374
```
373375

374376
### -RestrictDomainsToCertificate
375-
The RestrictDomainsToCertificate parameter specifies whether the Subject value of the TLS certificate is checked before messages can use the connector. Valid values are:
377+
The RestrictDomainsToCertificate parameter specifies whether the Subject value of the TLS certificate is checked before messages can use the Partner type connector. Valid values are:
376378

377379
- $true: Mail is allowed to use the connector only if the Subject value of the TLS certificate that the source email server uses to authenticate matches the TlsSenderCertificateName parameter value.
378380
- $false: The Subject value of the TLS certificate that the source email server uses to authenticate doesn't control whether mail from that source uses the connector. This is the default value.
379381

382+
**Note**: This parameter applies only to Partner type connectors.
383+
380384
```yaml
381385
Type: Boolean
382386
Parameter Sets: (All)
@@ -391,11 +395,13 @@ Accept wildcard characters: False
391395
```
392396

393397
### -RestrictDomainsToIPAddresses
394-
The RestrictDomainsToIPAddresses parameter specifies whether to reject mail that comes from unknown source IP addresses. Valid values are:
398+
The RestrictDomainsToIPAddresses parameter specifies whether to reject mail that comes from unknown source IP addresses for Partner type connectors. Valid values are:
395399

396400
- $true: Automatically reject mail from domains that are specified by the SenderDomains parameter if the source IP address isn't also specified by the SenderIPAddress parameter.
397401
- $false: Don't automatically reject mail from domains that are specified by the SenderDomains parameter based on the source IP address. This is the default value.
398402

403+
**Note**: This parameter applies only to Partner type connectors.
404+
399405
```yaml
400406
Type: Boolean
401407
Parameter Sets: (All)
@@ -426,7 +432,7 @@ Accept wildcard characters: False
426432
```
427433

428434
### -SenderIPAddresses
429-
The SenderIPAddresses parameter specifies the source IPV4 IP addresses that the connector accepts messages from. Valid values are:
435+
The SenderIPAddresses parameter specifies the source IPV4 IP addresses that the Partner type connector accepts messages from when the value of the RestrictDomainsToIPAddresses parameter is $true. Valid values are:
430436

431437
- Single IP address: For example, 192.168.1.1.
432438
- Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. Valid subnet mask values are /24 through /32.
@@ -435,6 +441,8 @@ You can specify multiple IP addresses separated by commas.
435441

436442
IPv6 addresses are not supported.
437443

444+
**Note**: This parameter applies to Partner type connectors only if the value of the RestrictDomainsToIPAddresses parameter is $true.
445+
438446
```yaml
439447
Type: MultiValuedProperty
440448
Parameter Sets: (All)

exchange/exchange-ps/exchange/New-LabelPolicy.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -110,6 +110,8 @@ Supported settings for built-in labeling:
110110

111111
- **EnableAudit**: Prevent Office apps from sending sensitivity label data to Microsoft 365 auditing solutions. Supported apps: Word, Excel, and PowerPoint on Windows (version 2201+), macOS (version 16.57+), iOS (version 2.57+), and Android (version 16.0.14827+); Outlook on Windows (version 2201+), Outlook on the web, and rolling out to macOS, iOS, and Android. Example: `New-LabelPolicy -Identity Global -AdvancedSettings @{EnableAudit="False"}`.
112112

113+
- **EnableRevokeGuiSupport**: Remove the Track & Revoke button from the sensitivity menu in Office clients. Supported apps: Word, Excel, and PowerPoint on Windows (version 2406+). Example: `New-LabelPolicy -Identity Global -AdvancedSettings @{EnableRevokeGuiSupport="False"}`. For more information about this configuration choice, see [Track and revoke document access](https://learn.microsoft.com/purview/track-and-revoke-admin).
114+
113115
- **DisableMandatoryInOutlook**: Outlook apps that support this setting exempt Outlook messages from mandatory labeling. Example: `New-LabelPolicy -Identity Global -AdvancedSettings @{DisableMandatoryInOutlook="True"}`. For more information about this configuration choice, see [Outlook-specific options for default label and mandatory labeling](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#outlook-specific-options-for-default-label-and-mandatory-labeling).
114116

115117
- **DisableShowSensitiveContent**: For Office apps that highlight the sensitive content that caused a label to be recommended, turn off these highlights and corresponding indications about the sensitive content. For more information, see [Sensitivity labels are automatically applied or recommended for your files and emails in Office](https://support.microsoft.com/office/sensitivity-labels-are-automatically-applied-or-recommended-for-your-files-and-emails-in-office-622e0d9c-f38c-470a-bcdb-9e90b24d71a1). Supported apps: Word for Windows (version 2311+). Example: `Set-LabelPolicy -Identity Global -AdvancedSettings @{DisableShowSensitiveContent="True"}`

0 commit comments

Comments
 (0)