From 717a8e68678f58f6dba5fd6a1b5be2fa08556f6c Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Wed, 11 Dec 2024 14:57:04 -0800 Subject: [PATCH 1/2] Updates to CAR deprecation --- exchange/exchange-ps/exchange/Get-ClientAccessRule.md | 2 +- exchange/exchange-ps/exchange/New-ClientAccessRule.md | 2 +- exchange/exchange-ps/exchange/Remove-ClientAccessRule.md | 2 +- exchange/exchange-ps/exchange/Set-ClientAccessRule.md | 2 +- exchange/exchange-ps/exchange/Test-ClientAccessRule.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/exchange/exchange-ps/exchange/Get-ClientAccessRule.md b/exchange/exchange-ps/exchange/Get-ClientAccessRule.md index 17b0b978dd..0e40aa0d98 100644 --- a/exchange/exchange-ps/exchange/Get-ClientAccessRule.md +++ b/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. diff --git a/exchange/exchange-ps/exchange/New-ClientAccessRule.md b/exchange/exchange-ps/exchange/New-ClientAccessRule.md index 8157f8a884..af5e934438 100644 --- a/exchange/exchange-ps/exchange/New-ClientAccessRule.md +++ b/exchange/exchange-ps/exchange/New-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. diff --git a/exchange/exchange-ps/exchange/Remove-ClientAccessRule.md b/exchange/exchange-ps/exchange/Remove-ClientAccessRule.md index ed65cabff8..df3b17ddf9 100644 --- a/exchange/exchange-ps/exchange/Remove-ClientAccessRule.md +++ b/exchange/exchange-ps/exchange/Remove-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. diff --git a/exchange/exchange-ps/exchange/Set-ClientAccessRule.md b/exchange/exchange-ps/exchange/Set-ClientAccessRule.md index 6d39cc3131..9a82144d26 100644 --- a/exchange/exchange-ps/exchange/Set-ClientAccessRule.md +++ b/exchange/exchange-ps/exchange/Set-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. diff --git a/exchange/exchange-ps/exchange/Test-ClientAccessRule.md b/exchange/exchange-ps/exchange/Test-ClientAccessRule.md index b500411382..3389d80031 100644 --- a/exchange/exchange-ps/exchange/Test-ClientAccessRule.md +++ b/exchange/exchange-ps/exchange/Test-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. From 53148691c4fc4f2ae7e35aca74bef42c6484de3f Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Wed, 11 Dec 2024 17:47:54 -0800 Subject: [PATCH 2/2] Blind cmdlet sweep ExO --- .openpublishing.redirection.json | 10 ++ .../Get-FederatedOrganizationIdentifier.md | 10 +- exchange/exchange-ps/exchange/Get-MailUser.md | 37 ++++- exchange/exchange-ps/exchange/Get-Mailbox.md | 21 +++ .../exchange/Get-PhishSimOverrideRule.md | 146 ------------------ .../exchange/Get-SecOpsOverrideRule.md | 146 ------------------ exchange/exchange-ps/exchange/New-MailUser.md | 44 +++++- .../exchange/New-MigrationBatch.md | 19 +++ .../exchange-ps/exchange/New-MoveRequest.md | 23 +++ .../exchange/Set-AcceptedDomain.md | 19 +++ .../exchange/Set-CASMailboxPlan.md | 68 ++++++++ .../exchange/Set-DistributionGroup.md | 19 +++ .../exchange/Set-DynamicDistributionGroup.md | 19 +++ .../Set-FederatedOrganizationIdentifier.md | 20 +-- exchange/exchange-ps/exchange/Set-MailUser.md | 34 +++- .../exchange-ps/exchange/Set-MoveRequest.md | 19 +++ .../exchange/Set-OrganizationConfig.md | 20 +++ exchange/exchange-ps/exchange/exchange.md | 4 - exchange/mapping/serviceMapping.json | 2 - 19 files changed, 361 insertions(+), 319 deletions(-) delete mode 100644 exchange/exchange-ps/exchange/Get-PhishSimOverrideRule.md delete mode 100644 exchange/exchange-ps/exchange/Get-SecOpsOverrideRule.md diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index ded9d9dd48..6a71f4fa5c 100644 --- a/.openpublishing.redirection.json +++ b/.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", diff --git a/exchange/exchange-ps/exchange/Get-FederatedOrganizationIdentifier.md b/exchange/exchange-ps/exchange/Get-FederatedOrganizationIdentifier.md index ca4520fe7c..141f7f644a 100644 --- a/exchange/exchange-ps/exchange/Get-FederatedOrganizationIdentifier.md +++ b/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 diff --git a/exchange/exchange-ps/exchange/Get-MailUser.md b/exchange/exchange-ps/exchange/Get-MailUser.md index 706e768d1a..acaf5fe057 100644 --- a/exchange/exchange-ps/exchange/Get-MailUser.md +++ b/exchange/exchange-ps/exchange/Get-MailUser.md @@ -52,6 +52,19 @@ Get-MailUser [[-Identity] ] [] ``` +### LOBAppAccount +``` +Get-MailUser [-LOBAppAccount] + [-Filter ] + [-OrganizationalUnit ] + [-ProgressAction ] + [-ResultSize ] + [-SharedWithMailUser] + [-SoftDeletedMailUser] + [-SortBy ] + [] +``` + ### 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,10 +247,10 @@ 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 @@ -227,9 +258,9 @@ 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 ``` diff --git a/exchange/exchange-ps/exchange/Get-Mailbox.md b/exchange/exchange-ps/exchange/Get-Mailbox.md index e4ae95d1d0..5e1a74512d 100644 --- a/exchange/exchange-ps/exchange/Get-Mailbox.md +++ b/exchange/exchange-ps/exchange/Get-Mailbox.md @@ -39,6 +39,7 @@ Get-Mailbox [-Anr ] [-IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames] [-IncludeAcceptMessagesOnlyFromWithDisplayNames] [-IncludeEmailAddressDisplayNames] + [-IncludeGrantSendOnBehalfToWithDisplayNames] [-IncludeInactiveMailbox] [-Migration] [-Monitoring] @@ -96,6 +97,7 @@ Get-Mailbox [[-Identity] ] [-IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames] [-IncludeAcceptMessagesOnlyFromWithDisplayNames] [-IncludeEmailAddressDisplayNames] + [-IncludeGrantSendOnBehalfToWithDisplayNames] [-IncludeInactiveMailbox] [-Migration] [-Monitoring] @@ -147,6 +149,7 @@ Get-Mailbox [-MailboxPlan ] [-IncludeAcceptMessagesOnlyFromSendersOrMembersWithDisplayNames] [-IncludeAcceptMessagesOnlyFromWithDisplayNames] [-IncludeEmailAddressDisplayNames] + [-IncludeGrantSendOnBehalfToWithDisplayNames] [-IncludeInactiveMailbox] [-Migration] [-OrganizationalUnit ] @@ -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. diff --git a/exchange/exchange-ps/exchange/Get-PhishSimOverrideRule.md b/exchange/exchange-ps/exchange/Get-PhishSimOverrideRule.md deleted file mode 100644 index 2132bfc705..0000000000 --- a/exchange/exchange-ps/exchange/Get-PhishSimOverrideRule.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/get-phishsimoverriderule -applicable: Exchange Online, Security & Compliance -title: Get-PhishSimOverrideRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: ---- - -# Get-PhishSimOverrideRule - -## SYNOPSIS -**Note**: The \*-PhishSimOverrideRule cmdlets in Security & Compliance PowerShell have been replaced by the \*-ExoPhishSimOverrideRule cmdlets in Exchange Online PowerShell. - -This cmdlet is functional only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). - -Use the Get-PhishSimOverrideRule cmdlet to view third-party phishing simulation override rules to bypass Exchange Online Protection filtering. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). - -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-PhishSimOverrideRule [[-Identity] ] - [-Confirm] - [-Policy ] - [-WhatIf] - [] -``` - -## DESCRIPTION -You need to be assigned permissions in the Security & Compliance before you can use this cmdlet. For more information, see [Permissions in the Security & Compliance](https://learn.microsoft.com/defender-office-365/scc-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-PhishSimOverrideRule -``` - -This example returns detailed information about the one and only phishing simulation override rule. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the phishing simulation override rule that you want to view. You can use any value that uniquely identifies the rule. For example: - -- Name -- Id -- Distinguished name (DN) -- GUID - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Security & Compliance - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Confirm -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Security & Compliance - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -Policy -The Policy parameter filters the results by phishing simulator override policy. You can use any value that uniquely identifies the policy. For example: - -- Name -- Id -- Distinguished name (DN) -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Security & Compliance - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Online, Security & Compliance - -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://go.microsoft.com/fwlink/p/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/Get-SecOpsOverrideRule.md b/exchange/exchange-ps/exchange/Get-SecOpsOverrideRule.md deleted file mode 100644 index 7e9878414f..0000000000 --- a/exchange/exchange-ps/exchange/Get-SecOpsOverrideRule.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -external help file: Microsoft.Exchange.TransportMailflow-Help.xml -online version: https://learn.microsoft.com/powershell/module/exchange/get-secopsoverriderule -applicable: Exchange Online, Security & Compliance, Exchange Online Protection -title: Get-SecOpsOverrideRule -schema: 2.0.0 -author: chrisda -ms.author: chrisda -ms.reviewer: ---- - -# Get-SecOpsOverrideRule - -## SYNOPSIS -**Note**: The \*-SecOpsOverrideRule cmdlets in Security & Compliance PowerShell have been replaced by the \*-ExoSecOpsOverrideRule cmdlets in Exchange Online PowerShell. - -This cmdlet is functional only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell). - -Use the Get-SecOpsOverrideRule cmdlet to view SecOps mailbox override rules to bypass Exchange Online Protection filtering. For more information, see [Configure the advanced delivery policy for third-party phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure). - -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-SecOpsOverrideRule [[-Identity] ] - [-Confirm] - [-Policy ] - [-WhatIf] - [] -``` - -## DESCRIPTION -You need to be assigned permissions in the Security & Compliance before you can use this cmdlet. For more information, see [Permissions in the Security & Compliance](https://learn.microsoft.com/defender-office-365/scc-permissions). - -## EXAMPLES - -### Example 1 -```powershell -Get-SecOpsOverrideRule -``` - -This example returns detailed information about the one and only SecOps mailbox override rule. - -## PARAMETERS - -### -Identity -The Identity parameter specifies the SecOps override rule that you want to view. You can use any value that uniquely identifies the rule. For example: - -- Name -- Id -- Distinguished name (DN) -- GUID - -```yaml -Type: ComplianceRuleIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection - -Required: False -Position: 0 -Default value: None -Accept pipeline input: True (ByPropertyName, ByValue) -Accept wildcard characters: False -``` - -### -Confirm -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: cf -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -DomainController -This parameter is reserved for internal Microsoft use. - -```yaml -Type: Fqdn -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 -``` - -### -Policy -The Policy parameter filters the results by SecOps mailbox override policy. You can use any value that uniquely identifies the policy. For example: - -- Name -- Id -- Distinguished name (DN) -- GUID - -```yaml -Type: PolicyIdParameter -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Security & Compliance, Exchange Online Protection - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -WhatIf -This parameter is reserved for internal Microsoft use. - -```yaml -Type: SwitchParameter -Parameter Sets: (All) -Aliases: wi -Applicable: Exchange Online, Security & Compliance, 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://go.microsoft.com/fwlink/p/?LinkID=113216). - -## INPUTS - -## OUTPUTS - -## NOTES - -## RELATED LINKS diff --git a/exchange/exchange-ps/exchange/New-MailUser.md b/exchange/exchange-ps/exchange/New-MailUser.md index 4dfdf52920..27ea5d62e4 100644 --- a/exchange/exchange-ps/exchange/New-MailUser.md +++ b/exchange/exchange-ps/exchange/New-MailUser.md @@ -125,7 +125,7 @@ New-MailUser [-Name] -FederatedIdentity [] ``` -### LOBAppAccount +### HVEAccount ``` New-MailUser [-Name] -Password [-HVEAccount] [-Alias ] @@ -146,6 +146,28 @@ New-MailUser [-Name] -Password [-HVEAccount] [] ``` +### LOBAppAccount +``` +New-MailUser [-Name] -Password [-LOBAppAccount] + [-Alias ] + [-Confirm] + [-DisplayName ] + [-FirstName ] + [-ImmutableId ] + [-Initials ] + [-LastName ] + [-MailboxRegion ] + [-ModeratedBy ] + [-ModerationEnabled ] + [-OrganizationalUnit ] + [-PrimarySmtpAddress ] + [-ProgressAction ] + [-RemotePowerShellEnabled ] + [-SendModerationNotifications ] + [-WhatIf] + [] +``` + ### MicrosoftOnlineServicesFederatedUser ``` New-MailUser [-Name] -FederatedIdentity -MicrosoftOnlineServicesID @@ -318,7 +340,7 @@ You can use the following methods as a value for this parameter: ```yaml Type: SecureString -Parameter Sets: EnabledUser, LOBAppAccount, MicrosoftOnlineServicesID +Parameter Sets: EnabledUser, HVEAccount, LOBAppAccount, MicrosoftOnlineServicesID Aliases: Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection @@ -549,6 +571,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -LOBAppAccount +This parameter is available only in the cloud-based service. + +{{ Fill LOBAppAccount Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: LOBAppAccount +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -MacAttachmentFormat The MacAttachmentFormat parameter specifies the Apple Macintosh operating system attachment format to use for messages sent to the mail contact or mail user. Valid values are: diff --git a/exchange/exchange-ps/exchange/New-MigrationBatch.md b/exchange/exchange-ps/exchange/New-MigrationBatch.md index 0ed22a58a6..f0c57ea06f 100644 --- a/exchange/exchange-ps/exchange/New-MigrationBatch.md +++ b/exchange/exchange-ps/exchange/New-MigrationBatch.md @@ -250,6 +250,7 @@ New-MigrationBatch -Name [-CSVData ] [-DisallowExistingUsers] [ [-ExcludeFolders ] [-ForwardingDisposition ] [-IncludeFolders ] + [-IncludeOtherContacts] [-LargeItemLimit ] [-Locale ] [-MigrateTasks] @@ -1244,6 +1245,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -IncludeOtherContacts +This parameter is available only in the cloud-based service. + +{{ Fill IncludeOtherContacts Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: Onboarding +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -LargeItemLimit The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the migration request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used. diff --git a/exchange/exchange-ps/exchange/New-MoveRequest.md b/exchange/exchange-ps/exchange/New-MoveRequest.md index 6ce38e9b62..85f5f280eb 100644 --- a/exchange/exchange-ps/exchange/New-MoveRequest.md +++ b/exchange/exchange-ps/exchange/New-MoveRequest.md @@ -55,6 +55,7 @@ New-MoveRequest [-Identity] -RemoteHostName ] [-RequestExpiryInterval ] [-SkipMoving ] + [-SourceEndpoint ] [-StartAfter ] [-Suspend] [-SuspendComment ] @@ -97,6 +98,7 @@ New-MoveRequest [-Identity] -RemoteHostName ] [-RequestExpiryInterval ] [-SkipMoving ] + [-SourceEndpoint ] [-StartAfter ] [-Suspend] [-SuspendComment ] @@ -134,6 +136,7 @@ New-MoveRequest [-Identity] -RemoteCredential ] [-RequestExpiryInterval ] [-SkipMoving ] + [-SourceEndpoint ] [-StartAfter ] [-Suspend] [-SuspendComment ] @@ -175,6 +178,7 @@ New-MoveRequest [-Identity] [-ProxyToMailbox ] [-RequestExpiryInterval ] [-SkipMoving ] + [-SourceEndpoint ] [-StartAfter ] [-Suspend] [-SuspendComment ] @@ -240,6 +244,7 @@ New-MoveRequest [-Identity] -TargetDeliveryDomain [-ProxyToMailbox ] [-RequestExpiryInterval ] [-SkipMoving ] + [-SourceEndpoint ] [-StartAfter ] [-Suspend] [-SuspendComment ] @@ -1076,6 +1081,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -SourceEndpoint +This parameter is available only in the cloud-based service. + +{{ Fill SourceEndpoint Description }} + +```yaml +Type: MigrationEndpointIdParameter +Parameter Sets: MigrationOutbound, MigrationRemote, MigrationRemoteLegacy, MigrationLocal, MigrationRemoteCrossTenant +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -StartAfter The StartAfter parameter specifies a delay before the request is started. The request isn't started until the date/time you specify with this parameter. diff --git a/exchange/exchange-ps/exchange/Set-AcceptedDomain.md b/exchange/exchange-ps/exchange/Set-AcceptedDomain.md index 41140bc16f..36e0eb7998 100644 --- a/exchange/exchange-ps/exchange/Set-AcceptedDomain.md +++ b/exchange/exchange-ps/exchange/Set-AcceptedDomain.md @@ -35,6 +35,7 @@ Set-AcceptedDomain [-Identity] [-PendingCompletion ] [-PendingRemoval ] [-SendingFromDomainDisabled ] + [-SendingToDomainDisabled ] [-WhatIf] [] ``` @@ -321,6 +322,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -SendingToDomainDisabled +This parameter is available only in the cloud-based service. + +{{ Fill SendingToDomainDisabled Description }} + +```yaml +Type: Boolean +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 +``` + ### -WhatIf The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. diff --git a/exchange/exchange-ps/exchange/Set-CASMailboxPlan.md b/exchange/exchange-ps/exchange/Set-CASMailboxPlan.md index 087eda2a0a..5901e16225 100644 --- a/exchange/exchange-ps/exchange/Set-CASMailboxPlan.md +++ b/exchange/exchange-ps/exchange/Set-CASMailboxPlan.md @@ -24,7 +24,11 @@ For information about the parameter sets in the Syntax section below, see [Excha Set-CASMailboxPlan [-Identity] [-ActiveSyncEnabled ] [-Confirm] + [-ECPEnabled ] + [-EwsEnabled ] [-ImapEnabled ] + [-MAPIEnabled ] + [-OWAEnabled ] [-OwaMailboxPolicy ] [-PopEnabled ] [-WhatIf] @@ -107,6 +111,38 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -ECPEnabled +{{ Fill ECPEnabled Description }} + +```yaml +Type: Boolean +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 +``` + +### -EwsEnabled +{{ Fill EwsEnabled Description }} + +```yaml +Type: System.Int32 +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 +``` + ### -ImapEnabled The ImapEnabled parameter enables or disables access to the mailbox by using IMAP4 clients. Valid values are: @@ -126,6 +162,38 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -MAPIEnabled +{{ Fill MAPIEnabled Description }} + +```yaml +Type: Boolean +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 +``` + +### -OWAEnabled +{{ Fill OWAEnabled Description }} + +```yaml +Type: Boolean +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 +``` + ### -OwaMailboxPolicy The OwaMailboxPolicy parameter specifies the Outlook on the web (formerly known as Outlook Web App) mailbox policy for the mailbox. You can use any value that uniquely identifies the policy. For example: diff --git a/exchange/exchange-ps/exchange/Set-DistributionGroup.md b/exchange/exchange-ps/exchange/Set-DistributionGroup.md index e7fc2a9503..7d84dcf397 100644 --- a/exchange/exchange-ps/exchange/Set-DistributionGroup.md +++ b/exchange/exchange-ps/exchange/Set-DistributionGroup.md @@ -89,6 +89,7 @@ Set-DistributionGroup [-Identity] [-SendOofMessageToOriginatorEnabled ] [-SimpleDisplayName ] [-UMDtmfMap ] + [-UpdateMemberCount] [-WhatIf] [-WindowsEmailAddress ] [] @@ -1654,6 +1655,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -UpdateMemberCount +This parameter is available only in the cloud-based service. + +{{ Fill UpdateMemberCount Description }} + +```yaml +Type: SwitchParameter +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 +``` + ### -WhatIf The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. diff --git a/exchange/exchange-ps/exchange/Set-DynamicDistributionGroup.md b/exchange/exchange-ps/exchange/Set-DynamicDistributionGroup.md index c27087309f..4b26f36939 100644 --- a/exchange/exchange-ps/exchange/Set-DynamicDistributionGroup.md +++ b/exchange/exchange-ps/exchange/Set-DynamicDistributionGroup.md @@ -103,6 +103,7 @@ Set-DynamicDistributionGroup [-Identity] [-SendOofMessageToOriginatorEnabled ] [-SimpleDisplayName ] [-UMDtmfMap ] + [-UpdateMemberCount] [-WhatIf] [-WindowsEmailAddress ] [] @@ -1987,6 +1988,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -UpdateMemberCount +This parameter is available only in the cloud-based service. + +{{ Fill UpdateMemberCount Description }} + +```yaml +Type: SwitchParameter +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 +``` + ### -WhatIf The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. diff --git a/exchange/exchange-ps/exchange/Set-FederatedOrganizationIdentifier.md b/exchange/exchange-ps/exchange/Set-FederatedOrganizationIdentifier.md index 1fc313723b..92e99bb1fe 100644 --- a/exchange/exchange-ps/exchange/Set-FederatedOrganizationIdentifier.md +++ b/exchange/exchange-ps/exchange/Set-FederatedOrganizationIdentifier.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml online version: https://learn.microsoft.com/powershell/module/exchange/set-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: Set-FederatedOrganizationIdentifier schema: 2.0.0 author: chrisda @@ -74,7 +74,7 @@ The Identity parameter specifies the federated organization identifier. 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 @@ -90,7 +90,7 @@ The AccountNamespace parameter specifies the federated domain to be used to esta Type: SmtpDomain 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 @@ -109,7 +109,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho Type: SwitchParameter Parameter Sets: (All) Aliases: cf -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 @@ -125,7 +125,7 @@ The DefaultDomain parameter specifies the federated domain used for delegation t Type: SmtpDomain Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -141,7 +141,7 @@ The DelegationFederationTrust parameter specifies the identity of the federation Type: FederationTrustIdParameter 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 @@ -151,6 +151,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 @@ -175,7 +177,7 @@ Setting the parameter to $false disables federation. Type: Boolean 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 @@ -191,7 +193,7 @@ The OrganizationContact parameter specifies the SMTP address of the federation c Type: SmtpAddress 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 @@ -207,7 +209,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -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 diff --git a/exchange/exchange-ps/exchange/Set-MailUser.md b/exchange/exchange-ps/exchange/Set-MailUser.md index cd88382a78..d63d4b1527 100644 --- a/exchange/exchange-ps/exchange/Set-MailUser.md +++ b/exchange/exchange-ps/exchange/Set-MailUser.md @@ -144,6 +144,7 @@ Set-MailUser [-Identity] [-EnableLitigationHoldForMigratio [-HVEAccount] [-ImmutableId ] [-JournalArchiveAddress ] + [-LOBAppAccount] [-MacAttachmentFormat ] [-MailTip ] [-MailTipTranslations ] @@ -219,6 +220,7 @@ Set-MailUser [-Identity] [-ExcludeFromAllOrgHolds] [-HiddenFromAddressListsEnabled ] [-HVEAccount] [-ImmutableId ] + [-LOBAppAccount] [-JournalArchiveAddress ] [-MacAttachmentFormat ] [-MailTip ] @@ -296,6 +298,7 @@ Set-MailUser [-Identity] [-ExcludeFromOrgHolds ] [-HVEAccount] [-ImmutableId ] [-JournalArchiveAddress ] + [-LOBAppAccount] [-MacAttachmentFormat ] [-MailboxRegion ] [-MailTip ] @@ -372,6 +375,7 @@ Set-MailUser [-Identity] [-RecalculateInactiveMailUser] [-HVEAccount] [-ImmutableId ] [-JournalArchiveAddress ] + [-LOBAppAccount] [-MacAttachmentFormat ] [-MailboxRegion ] [-MailTip ] @@ -448,6 +452,7 @@ Set-MailUser [-Identity] [-RemoveComplianceTagHoldApplied] [-HVEAccount] [-ImmutableId ] [-JournalArchiveAddress ] + [-LOBAppAccount] [-MacAttachmentFormat ] [-MailboxRegion ] [-MailTip ] @@ -524,6 +529,7 @@ Set-MailUser [-Identity] [-RemoveDelayHoldApplied] [-HVEAccount] [-ImmutableId ] [-JournalArchiveAddress ] + [-LOBAppAccount] [-MacAttachmentFormat ] [-MailTip ] [-MailTipTranslations ] @@ -600,6 +606,7 @@ Set-MailUser [-Identity] [-RemoveDelayReleaseHoldApplied] [-HVEAccount] [-ImmutableId ] [-JournalArchiveAddress ] + [-LOBAppAccount] [-MacAttachmentFormat ] [-MailTip ] [-MailTipTranslations ] @@ -675,6 +682,7 @@ Set-MailUser [-Identity] [-RemoveDisabledArchive] [-HVEAccount] [-ImmutableId ] [-JournalArchiveAddress ] + [-LOBAppAccount] [-MacAttachmentFormat ] [-MailboxRegion ] [-MailTip ] @@ -749,6 +757,7 @@ Set-MailUser [-Identity] [-RemoveLitigationHoldEnabled] [-HVEAccount] [-ImmutableId ] [-JournalArchiveAddress ] + [-LOBAppAccount] [-MacAttachmentFormat ] [-MailTip ] [-MailTipTranslations ] @@ -825,6 +834,7 @@ Set-MailUser [-Identity] [-RemoveOrphanedHolds ] [-HVEAccount] [-ImmutableId ] [-JournalArchiveAddress ] + [-LOBAppAccount] [-MacAttachmentFormat ] [-MailTip ] [-MailTipTranslations ] @@ -1810,6 +1820,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: EnableLitigationHoldForMigration, ExcludeFromAllOrgHolds, ExcludeFromOrgHolds, RecalculateInactiveMailUser, RemoveComplianceTagHoldApplied, RemoveDelayHoldApplied, RemoveDelayReleaseHoldApplied, RemoveDisabledArchive, RemoveLitigationHoldEnabled, RemoveOrphanedHolds +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. @@ -1869,10 +1897,10 @@ 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 @@ -1880,9 +1908,9 @@ Parameter Sets: EnableLitigationHoldForMigration, ExcludeFromAllOrgHolds, Exclud Aliases: Applicable: Exchange Online, Exchange Online Protection +Required: False Position: Named Default value: None -Required: False Accept pipeline input: False Accept wildcard characters: False ``` diff --git a/exchange/exchange-ps/exchange/Set-MoveRequest.md b/exchange/exchange-ps/exchange/Set-MoveRequest.md index 9f8e03ee7a..1d1ecd41fb 100644 --- a/exchange/exchange-ps/exchange/Set-MoveRequest.md +++ b/exchange/exchange-ps/exchange/Set-MoveRequest.md @@ -45,6 +45,7 @@ Set-MoveRequest [-Identity] [-RequestExpiryInterval ] [-SkipMoving ] [-SkippedItemApprovalTime ] + [-SourceEndpoint ] [-StartAfter ] [-SuspendWhenReadyToComplete ] [-TargetDatabase ] @@ -542,6 +543,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -SourceEndpoint +This parameter is available only in the cloud-based service. + +{{ Fill SourceEndpoint Description }} + +```yaml +Type: MigrationEndpointIdParameter +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -StartAfter The StartAfter parameter specifies a delay before the request is started. The request isn't started until the date/time you specify with this parameter. diff --git a/exchange/exchange-ps/exchange/Set-OrganizationConfig.md b/exchange/exchange-ps/exchange/Set-OrganizationConfig.md index 6d86faf076..fe6238ab03 100644 --- a/exchange/exchange-ps/exchange/Set-OrganizationConfig.md +++ b/exchange/exchange-ps/exchange/Set-OrganizationConfig.md @@ -23,6 +23,7 @@ For information about the parameter sets in the Syntax section below, see [Excha ### ShortenEventScopeParameter ``` Set-OrganizationConfig -ShortenEventScopeDefault + [-AcceptedDomainApprovedSendersEnabled ] [-ActivityBasedAuthenticationTimeoutEnabled ] [-ActivityBasedAuthenticationTimeoutInterval ] [-ActivityBasedAuthenticationTimeoutWithSingleSignOnEnabled ] @@ -324,6 +325,7 @@ Set-OrganizationConfig [-AdfsAuthenticationConfiguration ] ### DelayedDelicensingParameterSet ``` Set-OrganizationConfig [-DelayedDelicensingEnabled ] [-EndUserMailNotificationForDelayedDelicensingEnabled ] [-TenantAdminNotificationForDelayedDelicensingEnabled ] + [-AcceptedDomainApprovedSendersEnabled ] [-ActivityBasedAuthenticationTimeoutEnabled ] [-ActivityBasedAuthenticationTimeoutInterval ] [-ActivityBasedAuthenticationTimeoutWithSingleSignOnEnabled ] @@ -570,6 +572,24 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -AcceptedDomainApprovedSendersEnabled +This parameter is available only in the cloud-based service. + +{{ Fill AcceptedDomainApprovedSendersEnabled Description }} + +```yaml +Type: Boolean +Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet +Aliases: +Applicable: Exchange Online + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -ACLableSyncedObjectEnabled This parameter is available only in on-premises Exchange. diff --git a/exchange/exchange-ps/exchange/exchange.md b/exchange/exchange-ps/exchange/exchange.md index 132c15a522..10208980c0 100644 --- a/exchange/exchange-ps/exchange/exchange.md +++ b/exchange/exchange-ps/exchange/exchange.md @@ -262,8 +262,6 @@ Exchange PowerShell is built on Windows PowerShell technology and provides a pow ### [Get-PhishSimOverridePolicy](Get-PhishSimOverridePolicy.md) -### [Get-PhishSimOverrideRule](Get-PhishSimOverrideRule.md) - ### [Get-QuarantineMessage](Get-QuarantineMessage.md) ### [Get-QuarantineMessageHeader](Get-QuarantineMessageHeader.md) @@ -278,8 +276,6 @@ Exchange PowerShell is built on Windows PowerShell technology and provides a pow ### [Get-SecOpsOverridePolicy](Get-SecOpsOverridePolicy.md) -### [Get-SecOpsOverrideRule](Get-SecOpsOverrideRule.md) - ### [Get-SenderFilterConfig](Get-SenderFilterConfig.md) ### [Get-SenderIdConfig](Get-SenderIdConfig.md) diff --git a/exchange/mapping/serviceMapping.json b/exchange/mapping/serviceMapping.json index 32efdb1e0b..ab94e97812 100644 --- a/exchange/mapping/serviceMapping.json +++ b/exchange/mapping/serviceMapping.json @@ -119,7 +119,6 @@ "Get-MalwareFilterPolicy": "antispam-antimalware", "Get-MalwareFilterRule": "antispam-antimalware", "Get-PhishSimOverridePolicy": "antispam-antimalware", - "Get-PhishSimOverrideRule": "antispam-antimalware", "Get-QuarantineMessage": "antispam-antimalware", "Get-QuarantineMessageHeader": "antispam-antimalware", "Get-QuarantinePolicy": "antispam-antimalware", @@ -127,7 +126,6 @@ "Get-ReportSubmissionPolicy": "antispam-antimalware", "Get-ReportSubmissionRule": "antispam-antimalware", "Get-SecOpsOverridePolicy": "antispam-antimalware", - "Get-SecOpsOverrideRule": "antispam-antimalware", "Get-SenderFilterConfig": "antispam-antimalware", "Get-SenderIdConfig": "antispam-antimalware", "Get-SenderReputationConfig": "antispam-antimalware",