Merge branch 'master' into patch-372

Author: tiburd

exchange/exchange-ps/exchange/New-MigrationBatch.md

@@ -1375,9 +1375,15 @@ Accept wildcard characters: False
 ```
 
 ### -TargetArchiveDatabases
-The TargetArchiveDatabases parameter specifies the database where the archive mailboxes specified in the migration batch will be migrated to.
+The TargetArchiveDatabases parameter specifies the database where the archive mailboxes specified in the migration batch will be migrated to. You can use any value that uniquely identifies the database. For example:
 
-You can also specify multiple databases for the value of this parameter. The migration service selects one database as the target database to move the archive mailbox to. For example: -TargetArchiveDatabases @(MBXDB01,MBXDB02,MBXDB03)
+- Name
+- Distinguished name (DN)
+- GUID
+
+You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
+
+When you enter multiple values, the migration service selects one database as the target database to move the archive mailbox to.
 
 You can only use this parameter for local moves and remote move migrations.
 
@@ -1395,17 +1401,20 @@ Accept wildcard characters: False
 ```
 
 ### -TargetDatabases
-The TargetDatabases parameter specifies the identity of the database that you're moving mailboxes to. You can use the following values:
+The TargetDatabases parameter specifies the identity of the database that you're moving mailboxes to. You can use any value that uniquely identifies the database. For example:
 
-- Database GUID
-- Database name
+- Name
+- Distinguished name (DN)
+- GUID
 
-If you don't specify the TargetDatabases parameter for a local move, the cmdlet uses the automatic mailbox distribution logic to select the database.
+You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
 
-You can also specify multiple databases for the value of this parameter. The migration service will select one as the target database to move the mailbox to. For example: -TargetDatabases @(MBXDB01,MBXDB02,MBXDB03)
+When you enter multiple values, the migration service selects one database as the target database to move the mailbox to.
 
 You can only use this parameter for local moves and remote move migrations.
 
+If you don't use this parameter for a local move, the cmdlet uses the automatic mailbox distribution logic to select the database.
+
 ```yaml
 Type: MultiValuedProperty
 Parameter Sets: Local, Onboarding, Offboarding

exchange/exchange-ps/exchange/Set-ExternalInOutlook.md

@@ -76,7 +76,9 @@ Accept wildcard characters: False
 ```
 
 ### -AllowList
-The AllowList parameter specifies exceptions to external sender identification in supported versions of Outlook. Messages received from the specified senders or senders in the specified domains don't receive native External sender identification. Valid values are an individual domain (contoso.com), a domain and all subdomains (*.contoso.com) or email addresses ([email protected]).
+The AllowList parameter specifies exceptions to external sender identification in supported versions of Outlook. Messages received from the specified senders or senders in the specified domains don't receive native External sender identification. The allow list uses the `5322.From` address (also known as the **From** address or P2 sender).
+
+Valid values are an individual domain (contoso.com), a domain and all subdomains (*.contoso.com) or email addresses ([email protected]).
 
 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"`.
 

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

@@ -2973,7 +2973,10 @@ Accept wildcard characters: False
 ```
 
 ### -SendFromAliasEnabled
-This parameter is available only in the cloud-based service.
+This parameter is available only in the cloud-based service. 
+
+Note: This feature is in Preview and has not yet been officially released. Do not enable it if you are not willing to lose certain functionality or have a degraded experience. 
+An official announcement will be released via the EHLO blog and Message Center in due time.
 
 The SendFromAliasEnabled parameter allows mailbox users to send messages using aliases (proxy addresses). It does this by disabling the rewriting of aliases to their primary SMTP address. This change is implemented in the Exchange Online service. At the same time, Outlook clients are making changes to natively support aliases for sending and receiving messages. Even without an updated client, changes in behavior may be seen for users using any email client as the setting affects all messages sent and received by a mailbox. Valid values are: