Publish main to live, 12/12, 11:00 AM IST

.openpublishing.redirection.json

@@ -7133,6 +7133,16 @@
       "redirect_url": "/exchange/exchange-hybrid",
       "redirect_document_id": false
     },
+    {
+      "source_path": "exchange/virtual-folder/exchange/Get-PhishSimOverrideRule.md",
+      "redirect_url": "/powershell/module/exchange/get-exophishsimoverriderule",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "exchange/virtual-folder/exchange/Get-SecOpsOverrideRule.md",
+      "redirect_url": "/powershell/module/exchange/get-exosecopsoverriderule",
+      "redirect_document_id": false
+    },
     {
       "source_path": "skype/virtual-folder/skype/Disable-CsOnlineSipDomain.md",
       "redirect_url": "/powershell/module/teams/Disable-CsOnlineSipDomain",

exchange/exchange-ps/exchange/Get-ClientAccessRule.md

@@ -13,7 +13,7 @@ ms.reviewer:
 
 ## SYNOPSIS
 > [!NOTE]
-> Beginning in October 2022, we've disabled access to client access rules for all existing Exchange Online organizations that weren't using them. In September 2024, support for client access rules will end for all Exchange Online organizations. For more information, see [Update: Deprecation of Client Access Rules in Exchange Online](https://techcommunity.microsoft.com/t5/exchange-team-blog/update-deprecation-of-client-access-rules-in-exchange-online/ba-p/3790165).
+> Beginning in October 2022, client access rules were deprecated for all Exchange Online organizations that weren't using them. Client access rules will be deprecated for all remaining organizations on September 1, 2025. If you choose to turn off client access rules before the deadline, the feature will be disabled in your organization. For more information, see [Update on Client Access Rules Deprecation in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809).
 
 This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
 

exchange/exchange-ps/exchange/Get-FederatedOrganizationIdentifier.md

@@ -1,7 +1,7 @@
 ---
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 online version: https://learn.microsoft.com/powershell/module/exchange/get-federatedorganizationidentifier
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
 title: Get-FederatedOrganizationIdentifier
 schema: 2.0.0
 author: chrisda
@@ -12,7 +12,7 @@ ms.reviewer:
 # Get-FederatedOrganizationIdentifier
 
 ## SYNOPSIS
-This cmdlet is available only in on-premises Exchange.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
 
 Use the Get-FederatedOrganizationIdentifier cmdlet to retrieve the Exchange organization's federated organization identifier and related details, such as federated domains, organization contact and status.
 
@@ -57,7 +57,7 @@ The Identity parameter specifies the organization ID.
 Type: OrganizationIdParameter
 Parameter Sets: (All)
 Aliases:
-Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
 
 Required: False
 Position: 1
@@ -67,6 +67,8 @@ Accept wildcard characters: False
 ```
 
 ### -DomainController
+This parameter is available only in on-premises Exchange.
+
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
 ```yaml
@@ -91,7 +93,7 @@ The status is returned with each domain in the Domains property.
 Type: SwitchParameter
 Parameter Sets: (All)
 Aliases:
-Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
 
 Required: False
 Position: Named

exchange/exchange-ps/exchange/Get-MailUser.md

@@ -52,6 +52,19 @@ Get-MailUser [[-Identity] <MailUserIdParameter>]
  [<CommonParameters>]
 ```
 
+### LOBAppAccount
+```
+Get-MailUser [-LOBAppAccount]
+ [-Filter <String>]
+ [-OrganizationalUnit <OrganizationalUnitIdParameter>]
+ [-ProgressAction <ActionPreference>]
+ [-ResultSize <Unlimited>]
+ [-SharedWithMailUser]
+ [-SoftDeletedMailUser]
+ [-SortBy <String>]
+ [<CommonParameters>]
+```
+
 ### HVEAccount
 ```
 Get-MailUser [-HVEAccount]
@@ -193,6 +206,24 @@ Accept pipeline input: false
 Accept wildcard characters: False
 ```
 
+### -HVEAccount
+This parameter is available only in the cloud-based service.
+
+The HVEAccount switch specifies that this mail user account is specifically used for the [High volume email service](https://learn.microsoft.com/exchange/mail-flow-best-practices/high-volume-mails-m365). You don't need to specify a value with this switch.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: LOBAppAccount
+Aliases:
+Applicable: Exchange Online, Exchange Online Protection
+
+Position: Named
+Default value: None
+Required: False
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -IgnoreDefaultScope
 This parameter is available only in on-premises Exchange.
 
@@ -216,20 +247,20 @@ Accept pipeline input: false
 Accept wildcard characters: False
 ```
 
-### -HVEAccount
+### -LOBAppAccount
 This parameter is available only in the cloud-based service.
 
-The HVEAccount switch specifies that this mail user account is specifically used for the [High volume email service](https://learn.microsoft.com/exchange/mail-flow-best-practices/high-volume-mails-m365). You don't need to specify a value with this switch.
+{{ Fill LOBAppAccount Description }}
 
 ```yaml
 Type: SwitchParameter
 Parameter Sets: LOBAppAccount
 Aliases:
 Applicable: Exchange Online, Exchange Online Protection
 
+Required: False
 Position: Named
 Default value: None
-Required: False
 Accept pipeline input: False
 Accept wildcard characters: False
 ```

exchange/exchange-ps/exchange/Get-Mailbox.md

@@ -39,6 +39,7 @@ Get-Mailbox [-Anr <String>]
  [-IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames]
  [-IncludeAcceptMessagesOnlyFromWithDisplayNames]
  [-IncludeEmailAddressDisplayNames]
+ [-IncludeGrantSendOnBehalfToWithDisplayNames]
  [-IncludeInactiveMailbox]
  [-Migration]
  [-Monitoring]
@@ -96,6 +97,7 @@ Get-Mailbox [[-Identity] <MailboxIdParameter>]
  [-IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames]
  [-IncludeAcceptMessagesOnlyFromWithDisplayNames]
  [-IncludeEmailAddressDisplayNames]
+ [-IncludeGrantSendOnBehalfToWithDisplayNames]
  [-IncludeInactiveMailbox]
  [-Migration]
  [-Monitoring]
@@ -147,6 +149,7 @@ Get-Mailbox [-MailboxPlan <MailboxPlanIdParameter>]
  [-IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames]
  [-IncludeAcceptMessagesOnlyFromWithDisplayNames]
  [-IncludeEmailAddressDisplayNames]
+ [-IncludeGrantSendOnBehalfToWithDisplayNames]
  [-IncludeInactiveMailbox]
  [-Migration]
  [-OrganizationalUnit <OrganizationalUnitIdParameter>]
@@ -555,6 +558,24 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -IncludeGrantSendOnBehalfToWithDisplayNames
+This parameter is available only in the cloud-based service.
+
+{{ Fill IncludeGrantSendOnBehalfToWithDisplayNames Description }}
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: Identity, AnrSet, MailboxPlanSet
+Aliases:
+Applicable: Exchange Online
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -IncludeInactiveMailbox
 This parameter is available only in the cloud-based service.