Merge pull request MicrosoftDocs#4831 from MicrosoftDocs/master

Master to Live

Author: chrisda

exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2.md

@@ -18,7 +18,7 @@ description: "Learn how to download and use the Exchange Online PowerShell V2 mo
 
 # Use the Exchange Online PowerShell V2 module
 
-The Exchange Online PowerShell V2 module (abbreviated as the EXO V2 module) enables admins to connect to their Exchange Online environment in Office 365 to retrieve data, create new objects, update existing objects, remove objects as well as configure Exchange Online & its features.
+The Exchange Online PowerShell V2 module (abbreviated as the EXO V2 module) enables admins to connect to their Exchange Online environment in Office 365 to retrieve data, create new objects, update existing objects, remove objects as well as configure Exchange Online and its features.
 
 ## Report bugs and issues
 
@@ -34,9 +34,11 @@ Connect-ExchangeOnline -EnableErrorReporting -LogDirectoryPath <Path to store lo
 
 ## How the EXO V2 module works
 
-The Exchange Online PowerShell V2 module contains a small set of new cmdlets that are optimized for bulk data retrieval scenarios (think: thousands and thousands of objects). It also contains the 700 or more older remote PowerShell cmdlets baked into the same module. Note that after you install the EXO V2 module from the PowerShell Gallery, you only see new cmdlets in the module. You'll see the older remote PowerShell cmdlets after you create a session to connect to your Exchange Online environment. All the cmdlets in the V2 module use Modern auth for authentication. You can't use Basic auth in the EXO V2 module.
+The Exchange Online PowerShell V2 module contains a small set of new cmdlets that are optimized for bulk data retrieval scenarios (think: thousands and thousands of objects). Until you create a session to connect to your Exchange Online organization, you'll only see these new cmdlets in the module. After you connect to your Exchange Online organization, you'll see all of the older remote PowerShell cmdlets.
 
-The new cmdlets in the EXO V2 module are meant to replace their older, less efficient equivalents. However, the original cmdlets are still available in the EXO V2 module for backwards compatibility.
+The EXO V2 module use Modern authentication for all cmdlets. You can't use Basic authentication in the EXO V2 module; however, you still need to configure the Basic authentication setting in WinRM as described later in this topic.
+
+The new cmdlets in the EXO V2 module are meant to replace their older, less efficient equivalents. However, the original cmdlets are still available in the EXO V2 module for backwards compatibility **after** you create a session to connect to your Exchange Online organization.
 
 The new cmdlets in the EXO V2 module are listed in the following table:
 
@@ -57,7 +59,7 @@ The new cmdlets in the EXO V2 module are listed in the following table:
 
 You can download the EXO V2 module from the PowerShell gallery [here](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/).
 
-> [!NOTE]
+> [!NOTE] 
 > The latest version of PowerShell that's currently supported for the EXO V2 module is PowerShell 5.1. Support for PowerShell 6.0 or later is currently a work in progress and will be released soon. This also implies that EXO PowerShell V2 module won't work in Linux or Mac as of now. Support for Linux and Mac is a work in progress and will be announced soon.
 
 ### What do you need to know before you begin?
@@ -88,7 +90,7 @@ You can download the EXO V2 module from the PowerShell gallery [here](https://ww
   winrm get winrm/config/client/auth
   ```
 
-  If you don't see the value `Basic = true`, you need to run this command to enable basic authentication for WinRM:
+  If you don't see the value `Basic = true`, you need to run this command to enable Basic authentication for WinRM:
 
   ```
   winrm set winrm/config/client/auth @{Basic="true"}
@@ -98,6 +100,9 @@ You can download the EXO V2 module from the PowerShell gallery [here](https://ww
 
   > The WinRM client cannot process the request. Basic authentication is currently disabled in the client configuration. Change the client configuration and try the request again.
 
+  > [!NOTE] 
+  > We never send the username and password combination here, but the Basic auth header is required to transport the session's OAuth token, since the client-side WinRM implementation has no support for OAuth.
+
 ### Install the EXO V2 module
 
 To install the EXO V2 module for the first time, run the following commands:
@@ -123,11 +128,11 @@ To install the EXO V2 module for the first time, run the following commands:
    ```
 
    **Notes**:
-
+   
    - You need to configure this setting only once on your computer. Read more about execution policies [here](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_execution_policies).
-
+   
    - If you don't do this step, you'll receive the following error when you try to connect:
-
+   
      > Files cannot be loaded because running scripts is disabled on this system. Provide a valid certificate with which to sign the files.
 
 3. Close and re-open the elevated Windows PowerShell window to get the changes from the previous steps.
@@ -272,7 +277,7 @@ The following example returns all properties for the 10 mailboxes:
 Get-EXOMailbox -ResultSize 10 -PropertySets All
 ```
 
-> [!NOTE]
+> [!NOTE]  
 > We highly discourage using the _PropertySets_ parameter with the value `All` because it slows down the cmdlet and reduces reliability. Always use the _PropertySets_ and _Properties_ parameters to retrieve only the requires properties.
 
 ## Release notes

exchange/exchange-ps/exchange/organization/Set-ExchangeServer.md

@@ -183,9 +183,7 @@ Accept wildcard characters: False
 ### -InternetWebProxyBypassList
 The InternetWebProxyBypassList parameter specifies a list of servers that bypass the web proxy server specified by the InternetWebProxy parameter. You identify the servers by their FQDN (for example, server01.contoso.com).
 
-To enter multiple values and overwrite any existing FQDN entries, use the following syntax: \<FQDN1\>,\<FQDN2\>,...\<FQDNX\>.
-
-To add or remove one or more values without affecting any existing FQDN entries, use the following syntax: @{Add="\<FQDN1\>","\<FQDN2\>"...; Remove="\<FQDN1\>","\<FQDN\>"...}.
+To enter multiple values and overwrite any existing FQDN entries, use the following syntax: @("host1.contoso.com","host2.contoso.com","host3.contoso.com").
 
 The maximum number of servers you can enter with this parameter is 100.
 

exchange/exchange-ps/exchange/organization/Set-OrganizationConfig.md

@@ -30,6 +30,7 @@ Set-OrganizationConfig
  [-AppsForOfficeEnabled <Boolean>]
  [-AsyncSendEnabled <Boolean>]
  [-AuditDisabled <Boolean>]
+ [-AutodiscoverPartialDirSync <Boolean>]
  [-AutoEnableArchiveMailbox <Boolean>]
  [-AutoExpandingArchive]
  [-BookingsEnabled <Boolean>]
@@ -542,6 +543,26 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -AutodiscoverPartialDirSync
+This parameter is available only in the cloud-based service.
+
+The AutodiscoverPartialDirSync parameter is for scenarios where tenants have Directory Synced some of their Active Directory users into the cloud, but still have on-premises Exchange users that are not Directory Synced. Setting this parameter to $true will cause unknown users to be redirected to the on-premises endpoint and will allow on-premises users to discover their mailbox automatically. Online email addresses will be susceptible to enumeration. We recommend full Directory Sync for all Active Directory users and leaving this parameter with the default $false.
+
+After you enable AutodiscoverPartialDirSync, it will take approximately 3 hours to fully saturate across the cloud.
+
+```yaml
+Type: Boolean
+Parameter Sets: Default
+Aliases:
+Applicable: Exchange Online
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -AutoEnableArchiveMailbox
 This parameter is available only in the cloud-based service.
 

exchange/exchange-ps/exchange/policy-and-compliance-audit/Search-UnifiedAuditLog.md

@@ -226,7 +226,7 @@ The RecordType parameter filters the log entries by record type. Valid values ar
 
 - AeD
 
-- AirInvestigation 
+- AirInvestigation
 
 - ApplicationAudit
 
@@ -244,9 +244,9 @@ The RecordType parameter filters the log entries by record type. Valid values ar
 
 - ComplianceDLPSharePointClassification
 
-- ComplianceSupervisionExchange 
+- ComplianceSupervisionExchange
 
-- CustomerKeyServiceEncryption 
+- CustomerKeyServiceEncryption
 
 - CRM
 
@@ -258,7 +258,7 @@ The RecordType parameter filters the log entries by record type. Valid values ar
 
 - Discovery
 
-- DLPEndpoint 
+- DLPEndpoint
 
 - ExchangeAdmin
 
@@ -276,15 +276,15 @@ The RecordType parameter filters the log entries by record type. Valid values ar
 
 - InformationWorkerProtection
 
-- InformationBarrierPolicyApplication 
+- InformationBarrierPolicyApplication
 
 - Kaizala
 
 - LabelExplorer
 
 - MailSubmission
 
-- MicrosoftFlow 
+- MicrosoftFlow
 
 - MicrosoftForms
 
@@ -294,7 +294,7 @@ The RecordType parameter filters the log entries by record type. Valid values ar
 
 - MicrosoftTeamsAdmin
 
-- MicrosoftTeamsDevice 
+- MicrosoftTeamsDevice
 
 - MicrosoftTeamsAddOns
 
@@ -320,7 +320,7 @@ The RecordType parameter filters the log entries by record type. Valid values ar
 
 - PowerAppsPlan
 
-- Quarantine 
+- Quarantine
 
 - SecurityComplianceAlerts
 
@@ -332,15 +332,15 @@ The RecordType parameter filters the log entries by record type. Valid values ar
 
 - SharePointCommentOperation
 
-- SharePointContentTypeOperation 
+- SharePointContentTypeOperation
 
 - SharePointFileOperation
 
 - SharePointFieldOperation
 
 - SharePointListOperation
 
-- SharePointListItemOperation 
+- SharePointListItemOperation
 
 - SharePointSharingOperation
 
@@ -485,8 +485,7 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 ###  
 The OutVariable parameter accepts objects of type ArrayList. Here's an example of how to use it:
 
-$start = (Get-Date).AddDays(-1); $end = (Get-Date).AddDays(-0.5); $auditData = New-Object System.Collections.ArrayList; 
-Search-UnifiedAuditLog -StartDate $start -EndDate $end -OutVariable +auditData | Out-Null
+$start = (Get-Date).AddDays(-1); $end = (Get-Date).AddDays(-0.5); $auditData = New-Object System.Collections.ArrayList; Search-UnifiedAuditLog -StartDate $start -EndDate $end -OutVariable +auditData | Out-Null
 
 ## NOTES