Merge branch 'main' into RevItems-chrisda

Author: chrisda

exchange/exchange-ps/exchange/Add-RoleGroupMember.md

@@ -93,11 +93,9 @@ The Member parameter specifies who you want to add to the role group. You can sp
 
 - Mailbox users
 - Mail users
-- Mail-enabled security groups (don't use in Security & Compliance PowerShell)
+- Mail-enabled security groups
 - Security groups (on-premises Exchange only)
 
-You can't add security groups or mail-enabled security groups as members of the role group in the Microsoft Purview portal. You should add them via PowerShell with this parameter.
-
 You can use any value that uniquely identifies the user or group. For example:
 
 - Name

exchange/exchange-ps/exchange/Get-BlockedConnector.md

@@ -0,0 +1,73 @@
+---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-blockedconnector
+applicable: Exchange Online, Exchange Online Protection
+title: Get-BlockedConnector
+schema: 2.0.0
+author: chrisda
+ms.author: chrisda
+ms.reviewer:
+---
+
+# Get-BlockedConnector
+
+## SYNOPSIS
+This cmdlet is available only in the cloud-based service.
+
+Use the Get-BlockedConnector cmdlet to view inbound connectors that have been detected as potentially compromised. Blocked connectors are prevented from sending email.
+
+For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
+
+## SYNTAX
+
+```
+Get-BlockedConnector [-ConnectorId <Guid>] [<CommonParameters>]
+```
+
+## DESCRIPTION
+You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+
+## EXAMPLES
+
+### Example 1
+```powershell
+Get-BlockedConnector
+```
+
+This example returns a summary list of all blocked connectors.
+
+### Example 2
+```powershell
+Get-BlockedConnector -ConnectorId 159eb7c4-75d7-43e2-95fe-ced44b3e0a56 | Format-List
+```
+
+This example returns detailed information for the specified blocked connector.
+
+## PARAMETERS
+
+### -ConnectorId
+The ConnectorId parameter specifies the blocked connector that you want to view. The value is a GUID (for example, 159eb7c4-75d7-43e2-95fe-ced44b3e0a56).
+
+```yaml
+Type: Guid
+Parameter Sets: (All)
+Aliases:
+Applicable: Exchange Online, Exchange Online Protection
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+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://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_commonparameters).
+
+## INPUTS
+
+## OUTPUTS
+
+## NOTES
+
+## RELATED LINKS

exchange/exchange-ps/exchange/New-TenantAllowBlockListItems.md

@@ -173,6 +173,10 @@ The Allow switch specifies that you're creating an allow entry. You don't need t
 
 You can't use this switch with the Block switch.
 
+**Note**: See [Allow entries in the Tenant Allow/Block List](https://learn.microsoft.com/microsoft-365/security/office-365-security/tenant-allow-block-list-about#allow-entries-in-the-tenant-allowblock-list), before you try to create an allow entry.
+
+You can also use allow entries for third-party phishing simulation URLs with no expiration. For more information, see [Configure the delivery of third-party phishing simulations to users and unfiltered messages to SecOps mailboxes](https://learn.microsoft.com/microsoft-365/security/office-365-security/skip-filtering-phising-simulations-sec-ops-mailboxes).
+
 ```yaml
 Type: SwitchParameter
 Parameter Sets: (All)

exchange/exchange-ps/exchange/Release-QuarantineMessage.md

@@ -291,9 +291,9 @@ Accept wildcard characters: False
 ```
 
 ### -ReportFalsePositive
-The ReportFalsePositive switch sends a notification message indicating the specified message was not spam. You don't need to specify a value with this switch.
+The ReportFalsePositive switch specifies whether to report the message as a false positive to Microsoft (good message marked as bad). You don't need to specify a value with this switch.
 
-This switch is only available for quarantined spam messages.
+This switch is available only for quarantined spam messages.
 
 ```yaml
 Type: SwitchParameter

exchange/exchange-ps/exchange/Remove-BlockedConnector.md

@@ -0,0 +1,82 @@
+---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/remove-blockedconnector
+applicable: Exchange Online, Exchange Online Protection
+title: Remove-BlockedConnector
+schema: 2.0.0
+author: chrisda
+ms.author: chrisda
+ms.reviewer:
+---
+
+# Remove-BlockedConnector
+
+## SYNOPSIS
+This cmdlet is available only in the cloud-based service.
+
+Use the Remove-BlockedConnector cmdlet to unblock inbound connectors that have been detected as potentially compromised. Blocked connectors are prevented from sending email.
+
+For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
+
+## SYNTAX
+
+```
+Remove-BlockedConnector -ConnectorId <Guid> [-Reason <String>] [<CommonParameters>]
+```
+
+## DESCRIPTION
+You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+
+## EXAMPLES
+
+### Example 1
+```powershell
+Remove-BlockedConnector -ConnectorId 159eb7c4-75d7-43e2-95fe-ced44b3e0a56
+```
+
+This unblocks the specified blocked connector.
+
+## PARAMETERS
+
+### -ConnectorId
+The ConnectorId parameter specifies the blocked connector that you want to unblock. The value is a GUID (for example, 159eb7c4-75d7-43e2-95fe-ced44b3e0a56). You can find this value from the output of the Get-BlockedConnector command.
+
+```yaml
+Type: Guid
+Parameter Sets: (All)
+Aliases:
+Applicable: Exchange Online, Exchange Online Protection
+
+Required: True
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Reason
+The Reason parameter specifies comments about why you're unblocking the blocked connector. If the value contains spaces, enclose the value in quotation marks (").
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+Applicable: Exchange Online, Exchange Online Protection
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+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://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_commonparameters).
+
+## INPUTS
+
+## OUTPUTS
+
+## NOTES
+
+## RELATED LINKS

exchange/exchange-ps/exchange/Remove-RoleGroupMember.md

@@ -93,7 +93,7 @@ The Member parameter specifies who to remove from the role group. You can specif
 
 - Mailbox users
 - Mail users
-- Mail-enabled security groups (don't use in Security & Compliance PowerShell)
+- Mail-enabled security groups
 - Security groups (on-premises Exchange only)
 
 You can use any value that uniquely identifies the user or group. For example:

exchange/exchange-ps/exchange/Set-CaseHoldPolicy.md

@@ -16,6 +16,8 @@ This cmdlet is available only in Security & Compliance PowerShell. For more info
 
 Use the Set-CaseHoldPolicy cmdlet to modify existing case hold policies in the Microsoft Purview compliance portal.
 
+**Note**: Running this cmdlet causes a full synchronization across your organization, which is a significant operation. If you need to update multiple policies, wait until the policy distribution is successful before running the cmdlet again for the next policy. If you need to update a policy multiple times, make all changes in a single call of the cmdlet. For information about the distribution status, see [Get-CaseHoldPolicy](https://learn.microsoft.com/powershell/module/exchange/get-caseholdpolicy).
+
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
 ## SYNTAX

exchange/exchange-ps/exchange/Set-HostedConnectionFilterPolicy.md

@@ -162,6 +162,8 @@ The IPAllowList parameter specifies IP addresses from which messages are always
 
 You can specify multiple IP addresses of the same type separated by commas. For example, `SingleIP1, SingleIP2,...SingleIPN` or `CIDRIP1,CIDRIP2,...CIDRIPN`. To specify multiple IP addresses of different types at the same time, you need to use the following multivalued property syntax: `@{Add="SingleIP1","IPRange1","CIDRIP1",...}`.
 
+**Note**: IPv6 ranges are not supported.
+
 ```yaml
 Type: MultiValuedProperty
 Parameter Sets: (All)
@@ -184,6 +186,8 @@ The IPBlockList parameter specifies IP addresses from which messages are never a
 
 You can specify multiple IP addresses of the same type separated by commas. For example, `SingleIP1, SingleIP2,...SingleIPN` or `CIDRIP1,CIDRIP2,...CIDRIPN`. To specify multiple IP addresses of different types at the same time, you need to use the following multivalued property syntax: `@{Add="SingleIP1","IPRange1","CIDRIP1",...}`.
 
+**Note**: IPv6 ranges are not supported.
+
 ```yaml
 Type: MultiValuedProperty
 Parameter Sets: (All)

exchange/exchange-ps/exchange/exchange.md

@@ -206,6 +206,8 @@ Exchange PowerShell is built on Windows PowerShell technology and provides a pow
 
 ### [Get-AttachmentFilterListConfig](Get-AttachmentFilterListConfig.md)
 
+### [Get-BlockedConnector](Get-BlockedConnector.md)
+
 ### [Get-BlockedSenderAddress](Get-BlockedSenderAddress.md)
 
 ### [Get-ConfigAnalyzerPolicyRecommendation](Get-ConfigAnalyzerPolicyRecommendation.md)
@@ -324,6 +326,8 @@ Exchange PowerShell is built on Windows PowerShell technology and provides a pow
 
 ### [Remove-AttachmentFilterEntry](Remove-AttachmentFilterEntry.md)
 
+### [Remove-BlockedConnector](Remove-BlockedConnector.md)
+
 ### [Remove-BlockedSenderAddress](Remove-BlockedSenderAddress.md)
 
 ### [Remove-ContentFilterPhrase](Remove-ContentFilterPhrase.md)

exchange/mapping/serviceMapping.json

@@ -90,6 +90,7 @@
   "Get-AgentLog": "antispam-antimalware",
   "Get-AttachmentFilterEntry": "antispam-antimalware",
   "Get-AttachmentFilterListConfig": "antispam-antimalware",
+  "Get-BlockedConnector": "antispam-antimalware",
   "Get-BlockedSenderAddress": "antispam-antimalware",
   "Get-ConfigAnalyzerPolicyRecommendation": "antispam-antimalware",
   "Get-ContentFilterConfig": "antispam-antimalware",
@@ -150,6 +151,7 @@
   "Preview-QuarantineMessage": "antispam-antimalware",
   "Release-QuarantineMessage": "antispam-antimalware",
   "Remove-AttachmentFilterEntry": "antispam-antimalware",
+  "Remove-BlockedConnector": "antispam-antimalware",
   "Remove-BlockedSenderAddress": "antispam-antimalware",
   "Remove-ContentFilterPhrase": "antispam-antimalware",
   "Remove-EOPProtectionPolicyRule": "antispam-antimalware",