Merge branch 'master' into master

Author: tomkau

exchange/docs-conceptual/app-only-auth-powershell-v2.md

@@ -19,6 +19,14 @@ description: "Learn about using the Exchange Online V2 module in scripts and oth
 
 # App-only authentication in the EXO V2 module
 
+**Note**:
+
+This feature is currently in Public Preview, and is available in the Preview release of Exchange Online PowerShell V2 Module. To install the Preview release of the EXO V2 module, run the following command: 
+
+     ```powershell
+     Install-Module -Name ExchangeOnlineManagement -RequiredVersion 2.0.3-Preview -AllowPrerelease
+     ```
+
 Auditing and reporting scenarios in Exchange Online often involve scripts that run unattended. In most cases, these unattended scripts access Exchange Online PowerShell using Basic authentication (a username and password). Even when the connection to Exchange Online PowerShell uses Modern authentication, the credentials are stored in a local file or a secret vault that's access at run-time.
 
 Because storing user credentials locally is not a safe practice, we're releasing this feature to support authentication for unattended scripts (automation) scenarios using AzureAD applications and self-signed certificates.
@@ -177,11 +185,13 @@ After you register the certificate with your application, you can use the public
 
 Azure AD has more than 50 admin roles available. For app-only authentication in Exchange Online, we currently support the previously mentioned roles:
 
-- Global administrator
-- Compliance administrator
-- Security reader
-- Security administrator
-- Helpdesk administrator
+   - Global administrator
+   - Compliance administrator
+   - Security reader
+   - Security administrator
+   - Helpdesk administrator
+   - Exchange Service administrator
+   - Global Reader
 
 1. In the Azure AD portal under **Manage Azure Active Directory**, click **View**.
 

exchange/docs-conceptual/connect-to-exchange-online-powershell.md

@@ -18,12 +18,17 @@ description: "Learn how to use remote PowerShell to connect to Exchange Online."
 # Connect to Exchange Online PowerShell
 
 > [!NOTE]
-> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](exchange-online-powershell-v2.md).
+> Since Basic Auth Deprecation has been announced and this method uses Basic Authentication on Server Side, 
 
 Exchange Online PowerShell allows you to manage your Exchange Online settings from the command line. You use Windows PowerShell on your local computer to create a remote PowerShell session to Exchange Online. It's a simple three-step process where you enter your Microsoft 365 credentials, provide the required connection settings, and then import the Exchange Online cmdlets into your local Windows PowerShell session so that you can use them.
 
-> [!IMPORTANT]
-> If you want to use multi-factor authentication (MFA) to connect to Exchange Online PowerShell, you need to download and use the Exchange Online Remote PowerShell Module. For more information, see [Connect to Exchange Online PowerShell using multi-factor authentication](mfa-connect-to-exchange-online-powershell.md). <br/><br/> If you're a standalone Exchange Online Protection (EOP) customer (for example, you're using EOP to protect your on-premises email environment), use the connection instructions in [Connect to Exchange Online Protection PowerShell](connect-to-exchange-online-protection-powershell.md). If your on-premises Exchange organization has Exchange Enterprise CAL with Services licenses, EOP is one of the included services, and the connection instructions in this topic will work for you.
+> [!NOTE]
+> 
+> - We're eventually going to [disable Basic authentication in Exchange Online](https://techcommunity.microsoft.com/t5/exchange-team-blog/basic-authentication-and-exchange-online-april-2020-update/ba-p/1275508), and the connection method described in this topic uses Basic authentication. We recommend that you use the [Exchange Online PowerShell V2 module](exchange-online-powershell-v2.md) to connect to Exchange Online PowerShell, because it uses Modern authentication in all scenarios.
+> 
+> - The Exchange Online PowerShell V2 module works with multi-factor authentication (MFA). For MFA connection instructions using the older Exchange Online Remote PowerShell Module, see [Connect to Exchange Online PowerShell using multi-factor authentication](mfa-connect-to-exchange-online-powershell.md).
+> 
+> - If you're a standalone Exchange Online Protection (EOP) customer (for example, you're using EOP to protect your on-premises email environment), use the connection instructions in [Connect to Exchange Online Protection PowerShell](connect-to-exchange-online-protection-powershell.md). If your on-premises Exchange organization has Exchange Enterprise CAL with Services licenses, EOP is one of the included services, and the connection instructions in this topic will work for you.
 
 ## What do you need to know before you begin?
 

exchange/exchange-ps/exchange/Get-ComplianceSearch.md

@@ -22,8 +22,11 @@ For information about the parameter sets in the Syntax section below, see [Excha
 ## SYNTAX
 
 ```
-Get-ComplianceSearch [[-Identity] <ComplianceSearchIdParameter>] [-Case <String>] [-DomainController <Fqdn>]
- [-ResultSize <Unlimited>] [<CommonParameters>]
+Get-ComplianceSearch [[-Identity] <ComplianceSearchIdParameter>]
+ [-Case <String>]
+ [-DomainController <Fqdn>]
+ [-ResultSize <Unlimited>]
+ [<CommonParameters>]
 ```
 
 ## DESCRIPTION
@@ -52,7 +55,9 @@ This examples show details of the compliance search named Case 1234.
 ## PARAMETERS
 
 ### -Case
-This parameter is reserved for internal Microsoft use.
+The Case parameter filters the results by the name of a Core eDiscovery case that the compliance search is associated with. If the value contains spaces, enclose the value in quotation marks.
+
+You can't use this parameter to view compliance searches associated with Advanced eDiscovery cases.
 
 ```yaml
 Type: String

exchange/exchange-ps/exchange/New-ComplianceSearch.md

@@ -132,7 +132,9 @@ Accept wildcard characters: False
 ```
 
 ### -Case
-The Case parameter specifies the name of an eDiscovery case that the new compliance search will be associated with. If the value contains spaces, enclose the value in quotation marks.
+The Case parameter specifies the name of a Core eDiscovery case to associate the new compliance search with. If the value contains spaces, enclose the value in quotation marks.
+
+You can't use this parameter to create compliance searches associated with Advanced eDiscovery cases.
 
 If the Name parameter contains spaces, the value of the ExchangeLocation parameter is cleared when you use the Case parameter.
 

exchange/exchange-ps/exchange/Set-AtpPolicyForO365.md

@@ -38,7 +38,6 @@ Set-AtpPolicyForO365 [[-Identity] <AtpPolicyForO365IdParameter>]
  [-EnableATPForSPOTeamsODB <Boolean>]
  [-EnableSafeDocs <Boolean>]
  [-EnableSafeLinksForO365Clients <Boolean>]
- [-EnableSafeLinksForWebAccessCompanion <Boolean>]
  [-TrackClicks <Boolean>]
  [-WhatIf] [<CommonParameters>]
 ```
@@ -214,26 +213,6 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -EnableSafeLinksForWebAccessCompanion
-The EnableSafeLinksForWebAccessCompanion parameter specifies whether Safe Links is enabled for Microsoft 365 apps on the web. Valid values are:
-
-- $true: Safe Links are enabled for Microsoft 365 web apps. This is the default value.
-
-- $false: Safe Links are disabled for Microsoft 365 web apps.
-
-```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
-```
-
 ### -TrackClicks
 The TrackClicks parameter specifies whether to track user clicks related to blocked URLs. Valid values are:
 

exchange/exchange-ps/exchange/Set-IRMConfiguration.md

@@ -271,11 +271,13 @@ Accept wildcard characters: False
 ### -ExternalLicensingEnabled
 This parameter is available only in on-premises Exchange.
 
-The ExternalLicensingEnabled parameter specifies whether to enable IRM features for messages that are sent to external recipients. Valid values are:
+The ExternalLicensingEnabled parameter specifies whether Exchange will try to acquire licenses from clusters other than the one it is configured to use. Without this setting, if Exchange receives many messages protected with a random key, the server will devote excessive resources to validating signatures and decrypting messages, even if the keys aren't valid.
 
-- $true: IRM features are enabled for external messages.
+Valid values are:
 
-- $false: IRM features are disabled for external messages. This is the default value.
+- $true: Exchange will try to acquire licenses from clusters other than the one it is configured to use. This value can help prevent denial of service (DoS) attacks.
+
+- $false: Exchange will try to acquire licenses only from clusters that it is configured to use. This is the default value. The *LicensingLocation* parameter specifies the list of allowed clusters. 
 
 ```yaml
 Type: Boolean

exchange/exchange-ps/exchange/Set-Mailbox.md

@@ -5021,7 +5021,9 @@ A valid value is a number from 32 to 256 kilobytes (32768 to 262144 bytes). When
 
 Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
 
-The default value is 64 kilobytes (65536 bytes).
+In Exchange Online, Exchange 2019, Exchange 2016, and Exchange 2013, the default value is 256 kilobytes (262,144 bytes).
+
+In Exchange 2010, the default value is 64 kilobytes (65,536 bytes).
 
 The quota for Inbox rules applies only to enabled rules. There is no restriction on the number of disabled rules a mailbox can have. However, the total size of rules that are enabled or active can't exceed the value specified for this parameter.