diff --git a/exchange/docs-conceptual/connect-to-exchange-online-powershell.md b/exchange/docs-conceptual/connect-to-exchange-online-powershell.md index 1e04fc8795..fee77d3618 100644 --- a/exchange/docs-conceptual/connect-to-exchange-online-powershell.md +++ b/exchange/docs-conceptual/connect-to-exchange-online-powershell.md @@ -21,7 +21,7 @@ description: "Learn how to use the Exchange Online PowerShell V3 module to conne This article contains instructions for how to connect to Exchange Online PowerShell using the Exchange Online PowerShell module with or without multifactor authentication (MFA). > [!TIP] -> The connection instructions in this article also apply to Exchange Online Protection PowerShell for cloud protection of on-premises email environments without cloud mailboxes. +> The connection instructions in this article also apply to [the Built-in security add-on for on-premises mailboxes](/exchange/standalone-eop/standalone-eop). The Exchange Online PowerShell module uses modern authentication for connecting to Exchange Online PowerShell and Security & Compliance PowerShell. For more information about the Exchange Online PowerShell module, see [About the Exchange Online PowerShell module](exchange-online-powershell-v2.md). diff --git a/exchange/docs-conceptual/disable-access-to-exchange-online-powershell.md b/exchange/docs-conceptual/disable-access-to-exchange-online-powershell.md index 4e60f0d49a..dd7a1acf24 100644 --- a/exchange/docs-conceptual/disable-access-to-exchange-online-powershell.md +++ b/exchange/docs-conceptual/disable-access-to-exchange-online-powershell.md @@ -16,7 +16,7 @@ description: "Admins can learn how to disable or enable access to Exchange Onlin # Enable or disable access to Exchange Online PowerShell -Exchange Online PowerShell is the administrative interface that enables you to manage the Exchange Online part of your Microsoft 365 organization from the command line (including many default email protections for all cloud mailboxes and protections in Microsoft Defender for Office 365). +Exchange Online PowerShell is the administrative interface that enables you to manage the Exchange Online part of your Microsoft 365 organization from the command line (including many built-in security features for all cloud mailboxes and protections in Microsoft Defender for Office 365). By default, all accounts in Microsoft 365 are allowed to use Exchange Online PowerShell. This access doesn't give users administrative capabilities. They're still limited by [role based access control (RBAC)](/exchange/permissions-exo/permissions-exo). For example, they can configure some settings on their own mailbox and manage distribution groups that they own, but not much else. diff --git a/exchange/docs-conceptual/exchange-cmdlet-syntax.md b/exchange/docs-conceptual/exchange-cmdlet-syntax.md index 0018f40777..abe23f5552 100644 --- a/exchange/docs-conceptual/exchange-cmdlet-syntax.md +++ b/exchange/docs-conceptual/exchange-cmdlet-syntax.md @@ -10,7 +10,7 @@ ms.topic: article ms.service: exchange-online ms.localizationpriority: medium ms.assetid: 85ffe9c8-7f03-4877-8e55-3cbd40228d84 -description: "Learn about the structure and syntax of cmdlets in Exchange PowerShell, Exchange Online PowerShell, Security & Compliance PowerShell, and Exchange Online Protection PowerShell for cloud protection of on-premises email environments." +description: "Learn about the structure and syntax of cmdlets in Exchange PowerShell, Exchange Online PowerShell, and Security & Compliance PowerShell, and PowerShell for the Built-in security add-on for on-premises mailboxes." --- # Exchange cmdlet syntax diff --git a/exchange/docs-conceptual/exchange-online-powershell-v2.md b/exchange/docs-conceptual/exchange-online-powershell-v2.md index e13b2110a6..007c8700e1 100644 --- a/exchange/docs-conceptual/exchange-online-powershell-v2.md +++ b/exchange/docs-conceptual/exchange-online-powershell-v2.md @@ -20,14 +20,14 @@ description: "Admins can learn about the installation, maintenance, and design o # About the Exchange Online PowerShell module -The Exchange Online PowerShell module (also known as the Exchange Online PowerShell V3 module or EXO V3 module since 2022) uses modern authentication and works with or without multifactor authentication (MFA) for connecting to all Exchange cloud-related PowerShell environments: Exchange Online PowerShell, Security & Compliance PowerShell, and Exchange Online Protection PowerShell for cloud protection of on-premises email environments. +The Exchange Online PowerShell module (also known as the Exchange Online PowerShell V3 module or EXO V3 module since 2022) uses modern authentication and works with or without multifactor authentication (MFA) for connecting to all Exchange cloud-related PowerShell environments: Exchange Online PowerShell, Security & Compliance PowerShell, and PowerShell for [the Built-in security add-on for on-premises mailboxes](/exchange/standalone-eop/standalone-eop). For connection instructions using the module, see the following articles: - [Connect to Exchange Online PowerShell](connect-to-exchange-online-powershell.md) > [!TIP] - > Exchange Online Protection PowerShell for cloud protection of on-premises email environments uses the same connection instructions as Exchange Online PowerShell. + > Connection instructions for PowerShell in [the Built-in security add-on for on-premises mailboxes](/exchange/standalone-eop/standalone-eop) are the same as connection instructions for Exchange Online PowerShell. - [Connect to Security & Compliance PowerShell](connect-to-scc-powershell.md) - [App-only authentication for unattended scripts in Exchange Online PowerShell and Security & Compliance PowerShell](app-only-auth-powershell-v2.md) diff --git a/exchange/docs-conceptual/exchange-online-powershell.md b/exchange/docs-conceptual/exchange-online-powershell.md index 08f67e71e1..a631bb84b5 100644 --- a/exchange/docs-conceptual/exchange-online-powershell.md +++ b/exchange/docs-conceptual/exchange-online-powershell.md @@ -16,7 +16,7 @@ description: "Learn about articles that are available for using PowerShell in Ex # Exchange Online PowerShell -Exchange Online PowerShell is the administrative interface that enables you to manage the Exchange Online part of your Microsoft 365 organization from the command line (including many default email protections for all cloud mailboxes and protections in Microsoft Defender for Office 365). For example, you can use Exchange Online PowerShell to configure mail flow rules (also known as transport rules) and connectors. The following articles provide information about using Exchange Online PowerShell: +Exchange Online PowerShell is the administrative interface that enables you to manage the Exchange Online part of your Microsoft 365 organization from the command line (including many built-in security features for all cloud mailboxes and protections in Microsoft Defender for Office 365). For example, you can use Exchange Online PowerShell to configure mail flow rules (also known as transport rules) and connectors. The following articles provide information about using Exchange Online PowerShell: - To learn about the ExchangeOnlineManagement module that's required to connect to Exchange Online PowerShell, see [About the Exchange Online PowerShell module](exchange-online-powershell-v2.md). diff --git a/exchange/docs-conceptual/exchange-online-protection-powershell.md b/exchange/docs-conceptual/exchange-online-protection-powershell.md index 31ef739a0b..7f8db13a5a 100644 --- a/exchange/docs-conceptual/exchange-online-protection-powershell.md +++ b/exchange/docs-conceptual/exchange-online-protection-powershell.md @@ -1,36 +1,36 @@ --- -title: "Exchange Online Protection PowerShell for cloud protection of on-premises email environments" +title: "PowerShell for the Built-in security add-on for on-premises mailboxes" ms.author: chrisda author: chrisda manager: orspodek -ms.date: 07/11/2025 +ms.date: 12/16/2025 ms.audience: Admin audience: Admin ms.topic: article ms.service: exchange-powershell ms.localizationpriority: medium ms.assetid: f7918a88-774a-405e-945b-bc2f5ee9f748 -description: "Learn about the articles available for using Exchange Online Protection PowerShell to manage cloud protection features for on-premises email environments." +description: "Learn about the articles available for using PowerShell for the Built-in security add-on for on-premises mailboxes." --- -# Exchange Online Protection PowerShell for cloud protection of on-premises email environments +# PowerShell for the Built-in security add-on for on-premises mailboxes -Exchange Online Protection PowerShell is the administrative interface that enables you to manage cloud protection features for on-premises email environments from the command line. For example, you can use Exchange Online Protection PowerShell to configure anti-spam policies, mail flow rules (also known as transport rules) and connectors to support on-premises email protection. +PowerShell is the administrative interface that enables you to manage features in [the Built-in security add-on for on-premises mailboxes](/exchange/standalone-eop/standalone-eop) from the command line. For example, you can use PowerShell to configure anti-spam policies, mail flow rules (also known as transport rules) and connectors to support on-premises email protection. > [!TIP] -> All organizations with cloud mailboxes (Microsoft 365 A3/E3/G3, A5/E5/G5, Microsoft 365 Business Premium, etc.) use [Exchange Online PowerShell](exchange-online-powershell.md) to manage these same features for cloud email protection. +> All organizations with cloud mailboxes (Microsoft 365 A3/E3/G3, Microsoft 365 Business Standard, Microsoft 365 Business Premium, etc.) use [Exchange Online PowerShell](exchange-online-powershell.md) to manage these same features for cloud email protection. -Exchange Online Protection PowerShell for cloud protection of on-premises email environments is available in the following scenarios: +PowerShell in the Built-in security add-on for on-premises mailboxes is available in the following scenarios: -- **On-premises email environments (not just Microsoft Exchange)**: Mail from the internet passes through cloud protection and filtering before delivery to on-premises recipients. The cloud environment contains no mailboxes. -- **Exchange Enterprise CAL with Services**: The licenses for your on-premises Exchange organization include Exchange Enterprise CAL with Services (cloud protection of on-premises mailboxes is one of the services). +- **On-premises email environments (not just Microsoft Exchange)**: Mail from the internet passes through the Microsoft cloud organization for protection and filtering before delivery to on-premises recipients. The Microsoft cloud organization contains no cloud mailboxes. +- **Exchange Enterprise CAL with Services**: The licenses for your on-premises Exchange organization include Exchange Enterprise CAL with Services (the Built-in security add-on for on-premises mailboxes is one of the services). -The following articles provide information about using Exchange Online Protection PowerShell for cloud protection of on-premises email environments: +The following articles provide information about using PowerShell in the Built-in security add-on for on-premises mailboxes: -- To learn about the ExchangeOnlineManagement module that's required to connect to Exchange Online Protection PowerShell, see [About the Exchange Online PowerShell module](exchange-online-powershell-v2.md). +- To learn about the ExchangeOnlineManagement module that's required to connect to PowerShell, see [About the Exchange Online PowerShell module](exchange-online-powershell-v2.md). To learn about what's new in the Exchange Online PowerShell module, see [What's new in the Exchange Online PowerShell module](whats-new-in-the-exo-module.md). -- The connection instructions for Exchange Online Protection PowerShell and Exchange Online PowerShell are the same. For instructions, see [Connect to Exchange Online PowerShell](connect-to-exchange-online-powershell.md). +- The connection instructions for PowerShell in the Built-in security add-on for on-premises mailboxes and in Exchange Online PowerShell are the same. For instructions, see [Connect to Exchange Online PowerShell](connect-to-exchange-online-powershell.md). - To learn about the structure and layout of the cmdlet reference articles, see [Exchange cmdlet syntax](exchange-cmdlet-syntax.md). diff --git a/exchange/docs-conceptual/index.yml b/exchange/docs-conceptual/index.yml index b13eb4f65e..5636070ae9 100644 --- a/exchange/docs-conceptual/index.yml +++ b/exchange/docs-conceptual/index.yml @@ -31,7 +31,7 @@ landingContent: url: /powershell/exchange/exchange-online-powershell - text: Security & Compliance PowerShell url: /powershell/exchange/scc-powershell - - text: Exchange Online Protection PowerShell for cloud protection of on-premises email environments + - text: PowerShell for the Built-in security add-on for on-premises mailboxes url: /powershell/exchange/exchange-online-protection-powershell - title: Connect linkLists: diff --git a/exchange/docs-conceptual/scc-powershell.md b/exchange/docs-conceptual/scc-powershell.md index 7042012d8f..fb9d5ff24c 100644 --- a/exchange/docs-conceptual/scc-powershell.md +++ b/exchange/docs-conceptual/scc-powershell.md @@ -37,6 +37,6 @@ Security & Compliance PowerShell contains the following types of cmdlets: - Basic cmdlets that are also available in Exchange Online PowerShell (for example, [Get-User](/powershell/module/exchangepowershell/get-user), and [Get-RoleGroup](/powershell/module/exchangepowershell/get-rolegroup)). - A few cmdlets that correspond to default protections for cloud mailboxes and protections in Microsoft Defender for Office 365 in the Microsoft Defender portal (for example, [Set-SecOpsOverridePolicy](/powershell/module/exchangepowershell/set-secopsoverridepolicy)). - Cmdlets for most EOP and Defender for Office 365 security features (for example, [anti-spam policies](/defender-office-365/anti-spam-protection-about)) are available only in [Exchange Online PowerShell](exchange-online-powershell.md). + Cmdlets for most built-in security features for all cloud mailboxes and Defender for Office 365 security features (for example, [anti-spam policies](/defender-office-365/anti-spam-protection-about)) are available only in [Exchange Online PowerShell](exchange-online-powershell.md). Check the **Applies to** value in the cmdlet references article to verify the PowerShell environment where the cmdlet actually resides. diff --git a/exchange/docs-conceptual/toc.yml b/exchange/docs-conceptual/toc.yml index fdf23fce6e..c4028d2a18 100644 --- a/exchange/docs-conceptual/toc.yml +++ b/exchange/docs-conceptual/toc.yml @@ -72,12 +72,12 @@ href: client-advanced-settings.md - name: What's new in the Exchange Online PowerShell module href: whats-new-in-the-exo-module.md - - name: Exchange Online Protection PowerShell for cloud protection of on-premises email environments + - name: PowerShell for the Built-in security add-on for on-premises mailboxes href: exchange-online-protection-powershell.md items: - name: About the Exchange Online PowerShell module href: exchange-online-powershell-v2.md - - name: Connect to Exchange Online Protection PowerShell + - name: Connect to PowerShell for the Built-in security add-on for on-premises mailboxes href: connect-to-exchange-online-powershell.md - name: Exchange cmdlet syntax href: exchange-cmdlet-syntax.md diff --git a/exchange/docs-conceptual/whats-new-in-the-exo-module.md b/exchange/docs-conceptual/whats-new-in-the-exo-module.md index 460b7ed7c6..7e74dced86 100644 --- a/exchange/docs-conceptual/whats-new-in-the-exo-module.md +++ b/exchange/docs-conceptual/whats-new-in-the-exo-module.md @@ -20,7 +20,7 @@ description: "Learn about the new features and functionality available in the la # What's new in the Exchange Online PowerShell module -This article lists new features in the Exchange Online PowerShell module used for connecting to Exchange Online PowerShell, Security & Compliance PowerShell, and Exchange Online Protection PowerShell for cloud protection of on-premises email environments. Features that are currently in preview are denoted with **(preview)**. +This article lists new features in the Exchange Online PowerShell module used for connecting to Exchange Online PowerShell, Security & Compliance PowerShell, and PowerShell for [the Built-in security add-on for on-premises mailboxes](/exchange/standalone-eop/standalone-eop). Features that are currently in preview are denoted with **(preview)**. ## August 2025 @@ -88,7 +88,7 @@ This article lists new features in the Exchange Online PowerShell module used fo - [Version 3.2.0](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.2.0) has been released. -- [Virtually all](https://techcommunity.microsoft.com/t5/exchange-team-blog/deprecation-of-remote-powershell-rps-protocol-in-security-and/ba-p/3815432) Security & Compliance PowerShell cmdlets are now backed by the REST API, and REST API is used by default. To connect using remote PowerShell mode (which requires [Basic authentication in WinRM](exchange-online-powershell-v2.md#turn-on-basic-authentication-in-winrm)), use the _UseRPSSession_ switch in the **Connect-IPPSSession** command. +- [Virtually all](https://techcommunity.microsoft.com/t5/exchange-team-blog/deprecation-of-remote-powershell-rps-protocol-in-security-and/ba-p/3815432) Security & Compliance PowerShell cmdlets are now backed by the REST API, and REST API is used by default. To connect using remote PowerShell mode (which requires Basic authentication in WinRM), use the _UseRPSSession_ switch in the **Connect-IPPSSession** command. For information about what's in this release, see [Version 3.2.0](exchange-online-powershell-v2.md#version-320). @@ -101,7 +101,7 @@ This article lists new features in the Exchange Online PowerShell module used fo This version supports the Preview of Security & Compliance cmdlets backed by the REST API. Some, but not all cmdlets are supported. Basic authentication in WinRM is not required in Security & Compliance PowerShell for REST API cmdlets. > [!NOTE] - > The default value of the _UseRPSSession_ switch in **Connect-IPSSession** is now the same as **Connect-ExchangeOnline**. To connect in REST API mode, don't use the _UseRPSSession_ switch in the **Connect-IPPSSession** command. To connect using remote PowerShell mode (which requires [Basic authentication in WinRM](exchange-online-powershell-v2.md#turn-on-basic-authentication-in-winrm)), use the _UseRPSSession_ switch in the **Connect-IPPSSession** command. + > The default value of the _UseRPSSession_ switch in **Connect-IPSSession** is now the same as **Connect-ExchangeOnline**. To connect in REST API mode, don't use the _UseRPSSession_ switch in the **Connect-IPPSSession** command. To connect using remote PowerShell mode (which requires Basic authentication in WinRM), use the _UseRPSSession_ switch in the **Connect-IPPSSession** command. > > REST API connections in the EXO V3 module require the PowerShellGet and PackageManagement modules. For more information, see [PowerShellGet for REST-based connections in Windows](exchange-online-powershell-v2.md#powershellget-for-rest-api-connections-in-windows). @@ -112,7 +112,7 @@ This article lists new features in the Exchange Online PowerShell module used fo This version supports the Preview of Security & Compliance cmdlets backed by the REST API. Some, but not all cmdlets are supported. Basic authentication in WinRM is not required in Security & Compliance PowerShell for REST API cmdlets. > [!NOTE] - > The default value of the _UseRPSSession_ switch in **Connect-IPSSession** is opposite of **Connect-ExchangeOnline**. To connect in REST API mode, use `-UseRPSSession:$false` in the **Connect-IPPSSession** command. To connect using remote PowerShell mode (which requires [Basic authentication in WinRM](exchange-online-powershell-v2.md#turn-on-basic-authentication-in-winrm)), don't use the _UseRPSSession_ switch in the **Connect-IPPSSession** command. The default behavior will change in a later version of the module as more Security & Compliance cmdlets are available in REST API mode. + > The default value of the _UseRPSSession_ switch in **Connect-IPSSession** is opposite of **Connect-ExchangeOnline**. To connect in REST API mode, use `-UseRPSSession:$false` in the **Connect-IPPSSession** command. To connect using remote PowerShell mode (which requires Basic authentication in WinRM), don't use the _UseRPSSession_ switch in the **Connect-IPPSSession** command. The default behavior will change in a later version of the module as more Security & Compliance cmdlets are available in REST API mode. ## January 2023 diff --git a/exchange/exchange-ps/ExchangePowerShell/Connect-ExchangeOnline.md b/exchange/exchange-ps/ExchangePowerShell/Connect-ExchangeOnline.md index ba0b188989..2cea80e706 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Connect-ExchangeOnline.md +++ b/exchange/exchange-ps/ExchangePowerShell/Connect-ExchangeOnline.md @@ -15,7 +15,7 @@ title: Connect-ExchangeOnline ## SYNOPSIS This cmdlet is available only in the Exchange Online PowerShell module. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module). -Use the Connect-ExchangeOnline cmdlet in the Exchange Online PowerShell module to use modern authentication to connect to Exchange Online PowerShell or Exchange Online Protection PowerShell for cloud protection of on-premises email environments. This cmdlet works for accounts with or without multi-factor authentication (MFA). +Use the Connect-ExchangeOnline cmdlet in the Exchange Online PowerShell module to use modern authentication to connect to Exchange Online PowerShell or PowerShell for the Built-in security add-on for on-premises mailboxes. This cmdlet works for accounts with or without multi-factor authentication (MFA). To connect to Security & Compliance PowerShell, use the [Connect-IPPSSession](https://learn.microsoft.com/powershell/module/exchangepowershell/connect-ippssession) cmdlet. diff --git a/exchange/exchange-ps/ExchangePowerShell/ExchangePowerShell.md b/exchange/exchange-ps/ExchangePowerShell/ExchangePowerShell.md index d7853f2f0f..79d36f8a44 100644 --- a/exchange/exchange-ps/ExchangePowerShell/ExchangePowerShell.md +++ b/exchange/exchange-ps/ExchangePowerShell/ExchangePowerShell.md @@ -12,7 +12,7 @@ Exchange PowerShell is built on PowerShell technology to a powerful command-line - [Exchange Server PowerShell (Exchange Management Shell)](https://learn.microsoft.com/powershell/exchange/exchange-management-shell) - [Exchange Online PowerShell](https://learn.microsoft.com/powershell/exchange/exchange-online-powershell) - [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell) -- [Exchange Online Protection PowerShell for cloud protection of on-premises email environments](https://learn.microsoft.com/powershell/exchange/exchange-online-protection-powershell) +- [PowerShell for the Built-in security add-on for on-premises mailboxes](https://learn.microsoft.com/powershell/exchange/exchange-online-protection-powershell) > [!NOTE] > For cloud environments, use the [ExchangeOnlineManagement](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/) in the PowerShell Gallery. For more information, see [About the Exchange Online PowerShell module](../../docs-conceptual/exchange-online-powershell-v2.md). diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ATPBuiltInProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ATPBuiltInProtectionRule.md index 3469e8d8a9..52ef54aa3d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ATPBuiltInProtectionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ATPBuiltInProtectionRule.md @@ -26,7 +26,7 @@ Get-ATPBuiltInProtectionRule [[-Identity] ] [-Stat ``` ## DESCRIPTION -For more information about preset security policies, see [Preset security policies in EOP and Microsoft Defender for Office 365](https://learn.microsoft.com/defender-office-365/preset-security-policies). +For more information about preset security policies, see [Preset security policies in cloud organizations](https://learn.microsoft.com/defender-office-365/preset-security-policies). You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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). diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ConfigAnalyzerPolicyRecommendation.md b/exchange/exchange-ps/ExchangePowerShell/Get-ConfigAnalyzerPolicyRecommendation.md index ea9f4cd215..8d018558e4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ConfigAnalyzerPolicyRecommendation.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ConfigAnalyzerPolicyRecommendation.md @@ -29,7 +29,7 @@ Get-ConfigAnalyzerPolicyRecommendation -RecommendedPolicyType Applicable: Exchange Online, Exchange Online Protection -The OutboundConnector parameter specifies the name of the outbound connector configured on the EOP service for a hybrid deployment configured with an on-premises Exchange organization. +The OutboundConnector parameter specifies the name of the outbound connector configured in Microsoft 365 for a hybrid deployment with an on-premises Exchange organization. ```yaml Type: OutboundConnectorIdParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-EOPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-EOPProtectionPolicyRule.md index 5c64c8e9df..cd91523b35 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-EOPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-EOPProtectionPolicyRule.md @@ -15,7 +15,7 @@ title: Remove-EOPProtectionPolicyRule ## SYNOPSIS This cmdlet is available only in the cloud-based service. -Use the Remove-EOPProtectionPolicyRule cmdlet to remove rules for default email protections for all cloud mailboxes in preset security policies. The rules specify recipient conditions and exceptions for the protection, and also allow you to turn on and turn off the associated preset security policies. +Use the Remove-EOPProtectionPolicyRule cmdlet to remove rules for the built-in security features for all cloud mailboxes in preset security policies. The rules specify recipient conditions and exceptions for the protection, and also allow you to turn on and turn off the associated preset security policies. **Note**: Use this cmdlet to remove a rule only if you plan to immediately recreate the rule using the New-EOPProtectionPolicyRule cmdlet. The affected preset security policy can't function without a corresponding rule. @@ -42,7 +42,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi Remove-EOPProtectionPolicyRule -Identity "Standard Preset Security Policy" ``` -This example removes the existing rule for EOP protections in the Standard preset security policy. +This example removes the existing rule for the built-in security features for all cloud mailboxes in the Standard preset security policy. ## PARAMETERS diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AccessToCustomerDataRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-AccessToCustomerDataRequest.md index aaedd38eb6..1548e99af5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AccessToCustomerDataRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AccessToCustomerDataRequest.md @@ -108,7 +108,7 @@ Accept wildcard characters: False The ServiceName parameter specifies the related service. Valid values are: -- EOP +- EOP (built-in security features for all cloud mailboxes) - Exchange - SharePoint - Teams diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-EOPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-EOPProtectionPolicyRule.md index 158f4efa73..b4febd23b7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-EOPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-EOPProtectionPolicyRule.md @@ -15,7 +15,7 @@ title: Set-EOPProtectionPolicyRule ## SYNOPSIS This cmdlet is available only in the cloud-based service. -Use the Set-EOPProtectionPolicyRule cmdlet to modify rules associated with default email protections for all cloud mailboxes in preset security policies. +Use the Set-EOPProtectionPolicyRule cmdlet to modify rules associated with the built-in security features for all cloud mailboxes in preset security policies. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -52,7 +52,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi Set-EOPProtectionPolicyRule -Identity "Standard Preset Security Policy" -ExceptIfSentToMemberOf "Test Group1","Test Group2" ``` -This example provides exceptions to EOP protections in the Standard preset security policy for members of the specified groups. +This example provides exceptions to the built-in security features for all cloud mailboxes in the Standard preset security policy for members of the specified groups. ### Example 2 ```powershell diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterPolicy.md index 65a16298ad..b72630007c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterPolicy.md @@ -179,7 +179,7 @@ Accept wildcard characters: False The AllowedSenderDomains parameter specifies trusted domains that aren't processed by the spam filter. Messages from senders in these domains are stamped with `SFV:SKA` in the `X-Forefront-Antispam-Report header` and receive a spam confidence level (SCL) of -1, so the messages are delivered to the recipient's inbox. Valid values are one or more SMTP domains. -**Caution**: Think very carefully before you add domains here. For more information, see [Create safe sender lists in EOP](https://learn.microsoft.com/defender-office-365/create-safe-sender-lists-in-office-365). +**Caution**: Think very carefully before you add domains here. For more information, see [Create sender allowlists for cloud mailboxes](https://learn.microsoft.com/defender-office-365/create-safe-sender-lists-in-office-365). To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -203,7 +203,7 @@ Accept wildcard characters: False The AllowedSenders parameter specifies a list of trusted senders that skip spam filtering. Messages from these senders are stamped with SFV:SKA in the X-Forefront-Antispam-Report header and receive an SCL of -1, so the messages are delivered to the recipient's inbox. Valid values are one or more SMTP email addresses. -**Caution**: Think very carefully before you add senders here. For more information, see [Create safe sender lists in EOP](https://learn.microsoft.com/defender-office-365/create-safe-sender-lists-in-office-365). +**Caution**: Think very carefully before you add senders here. For more information, see [Create sender allowlists for cloud mailboxes](https://learn.microsoft.com/defender-office-365/create-safe-sender-lists-in-office-365). To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -227,7 +227,7 @@ Accept wildcard characters: False The BlockedSenderDomains parameter specifies domains that are always marked as spam sources. Messages from senders in these domains are stamped with `SFV:SKB` value in the `X-Forefront-Antispam-Report` header and receive an SCL of 6 (spam). Valid values are one or more SMTP domains. -**Note**: Manually blocking domains isn't dangerous, but it can increase your administrative workload. For more information, see [Create block sender lists in EOP](https://learn.microsoft.com/defender-office-365/create-block-sender-lists-in-office-365). +**Note**: Manually blocking domains isn't dangerous, but it can increase your administrative workload. For more information, see [Create sender blocklists for cloud mailboxes](https://learn.microsoft.com/defender-office-365/create-block-sender-lists-in-office-365). To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -251,7 +251,7 @@ Accept wildcard characters: False The BlockedSenders parameter specifies senders that are always marked as spam sources. Messages from these senders are stamped with `SFV:SKB` in the `X-Forefront-Antispam-Report` header and receive an SCL of 6 (spam). Valid values are one or more SMTP email addresses. -**Note**: Manually blocking senders isn't dangerous, but it can increase your administrative workload. For more information, see [Create block sender lists in EOP](https://learn.microsoft.com/defender-office-365/create-block-sender-lists-in-office-365). +**Note**: Manually blocking senders isn't dangerous, but it can increase your administrative workload. For more information, see [Create sender blocklists for cloud mailboxes](https://learn.microsoft.com/defender-office-365/create-block-sender-lists-in-office-365). To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`. @@ -306,7 +306,7 @@ The BulkSpamAction parameter specifies the action to take on messages that are m - AddXHeader: Add the AddXHeaderValue parameter value to the message header and deliver the message. - Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). -- MoveToJmf: This value is the default. Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid). +- MoveToJmf: This value is the default. Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Deliver cloud-detected spam to the Junk Email folder in on-premises mailboxes](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid). - NoAction - Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as bulk email are available to the intended recipients and admins. Or, you can use the BulkQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages. - Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. @@ -329,7 +329,7 @@ Accept wildcard characters: False The BulkThreshold parameter specifies the BCL on messages that triggers the action specified by the BulkSpamAction parameter (greater than or equal to the specified BCL value). A valid value is an integer from 1 to 9. The default value is 7, which means a BCL of 7, 8, or 9 on messages triggers the action specified by the BulkSpamAction parameter. -A higher BCL indicates the message is more likely to generate complaints (and is therefore more likely to be spam). For more information, see [Bulk complaint level (BCL) in EOP](https://learn.microsoft.com/defender-office-365/anti-spam-bulk-complaint-level-bcl-about). +A higher BCL indicates the message is more likely to generate complaints (and is therefore more likely to be spam). For more information, see [Bulk complaint level (BCL) in cloud organizations](https://learn.microsoft.com/defender-office-365/anti-spam-bulk-complaint-level-bcl-about). ```yaml Type: Int32 @@ -607,7 +607,7 @@ The HighConfidenceSpamAction parameter specifies the action to take on messages - AddXHeader: Add the AddXHeaderValue parameter value to the message header, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). - Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). -- MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid). +- MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Deliver cloud-detected spam to the Junk Email folder in on-premises mailboxes](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid). - Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as high confidence spam are available to the intended recipients and admins. Or, you can use the HighConfidenceSpamQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages. - Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. @@ -1285,7 +1285,7 @@ The SpamAction parameter specifies the action to take on messages that are marke - AddXHeader: Add the AddXHeaderValue parameter value to the message header, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). - Delete : Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message. - ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf). -- MoveToJmf: This value is the default. Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid). +- MoveToJmf: This value is the default. Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Deliver cloud-detected spam to the Junk Email folder in on-premises mailboxes](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid). - Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as spam are available to the intended recipients and admins. Or, you can use the SpamQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages. - Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxJunkEmailConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxJunkEmailConfiguration.md index 264b0132ca..82409b4978 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxJunkEmailConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxJunkEmailConfiguration.md @@ -349,7 +349,7 @@ To empty the list of email addresses and domains, use the value $null. - You can't add sender email addresses from the same domain as the recipient's email address. All mailboxes in the global address list (GAL) are automatically considered as trusted senders. - You can't directly modify the Safe Recipients list by using this cmdlet. You use this parameter to modify the Safe Senders list, and the email addresses and domains are synchronized to the Safe Recipients list. -- In standalone EOP with directory synchronization, domain entries aren't synchronized by default, but you can enable synchronization for domains. For more information, see [Configure Content Filtering to Use Safe Domain Data](/exchange/configure-content-filtering-to-use-safe-domain-data-exchange-2013-help). +- In hybrid Exchange organizations with directory synchronization, domain entries aren't synchronized by default, but you can enable synchronization for domains. For more information, see [Configure Content Filtering to Use Safe Domain Data](https://learn.microsoft.com/exchange/configure-content-filtering-to-use-safe-domain-data-exchange-2013-help). ```yaml Type: MultiValuedProperty diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OnPremisesOrganization.md b/exchange/exchange-ps/ExchangePowerShell/Set-OnPremisesOrganization.md index a6c3d1ea65..f5f296d3fc 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OnPremisesOrganization.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OnPremisesOrganization.md @@ -187,7 +187,7 @@ Accept wildcard characters: False > Applicable: Exchange Online -The OutboundConnector parameter specifies the name of the outbound connector configured on the EOP service for a hybrid deployment configured with an on-premises Exchange organization. +The OutboundConnector parameter specifies the name of the outbound connector configured in Microsoft 365 for a hybrid deployment with an on-premises Exchange organization. ```yaml Type: OutboundConnectorIdParameter diff --git a/repo_docs/NEW_CMDLETS.md b/repo_docs/NEW_CMDLETS.md index baa731cabf..db0953df1c 100644 --- a/repo_docs/NEW_CMDLETS.md +++ b/repo_docs/NEW_CMDLETS.md @@ -57,15 +57,15 @@ You probably know how to connect, but the available workloads and connection met - Exchange Online PowerShell: [Connect to Exchange Online PowerShell](https://learn.microsoft.com/powershell/exchange/connect-to-exchange-online-powershell) > [!TIP] - > These instructions also apply to Exchange Online Protection PowerShell (PowerShell in [the Built-in security add-on for on-premises mailboxes](/exchange/standalone-eop/standalone-eop)). + > These instructions also apply to [PowerShell for the Built-in security add-on for on-premises mailboxes](/exchange/standalone-eop/standalone-eop). - Security & Compliance PowerShell: [Connect to Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/connect-to-scc-powershell) - Exchange Server PowerShell: [Connect to Exchange servers using remote PowerShell](https://learn.microsoft.com/powershell/exchange/connect-to-exchange-servers-using-remote-powershell) > [!TIP] -> You might need to connect to the service in an elevated Windows PowerShell prompt (Teams and Exchange environments don't require an elevated Windows PowerShell prompt). The connection instructions article should plainly state this and other connection requirements. +> You might need to connect to the service in an elevated Windows PowerShell prompt (not required by Teams and Exchange environments). The corresponding connection instructions article should plainly state this and other connection requirements. > -> In Exchange and Security & Compliance PowerShell environments, role-based access control (RBAC) controls the available cmdlets. Most cmdlets and parameters are available to administrators by default, but some aren't (for example, the "Mailbox Search" and "Mailbox Import Export" roles. +> In Exchange and Security & Compliance PowerShell environments, role-based access control (RBAC) controls the available cmdlets. Most cmdlets and parameters are available to administrators by default, but some aren't (for example, the "Mailbox Search" and "Mailbox Import Export" roles). > > Remote PowerShell connections are deprecated in Exchange Online PowerShell and Security & Compliance PowerShell in favor of REST API connections. For more information, see the following articles: >