Merge branch 'master' into patch-16

Author: kenwith

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

@@ -16,7 +16,7 @@ description: "Learn how to connect to Exchange Online PowerShell by using multi-
 If you want to use multi-factor authentication (MFA) to connect to Exchange Online PowerShell, you can't use the instructions at [Connect to Exchange Online PowerShell](connect-to-exchange-online-powershell.md) to use remote PowerShell to connect to Exchange Online. MFA requires you to install the Exchange Online Remote PowerShell Module, and use the **Connect-EXOPSSession** cmdlet to connect.
 
 > [!NOTE]
-> • You can't use the Exchange Online Remote PowerShell Module to connect to Exchange Online PowerShell and Security & Compliance Center PowerShell in the same session (window). You need to use separate sessions of the Exchange Online Remote PowerShell Module. <br/>• Delegated Access Permission (DAP) partners can't use the procedures in this topic to connect to their customer tenant organizations in Exchange Online PowerShell. MFA and the Exchange Online Remote PowerShell Module don't work with delegated authentication. <br/>• The Exchange Online Remote PowerShell Module is not supported in PowerShell Core (macOS, Linux, or Windows Nano Server). As a workaround, you can install the module on a computer that's running a supported version of Windows (physical or virtual), and use remote desktop software to connect.
+> • Delegated Access Permission (DAP) partners can't use the procedures in this topic to connect to their customer tenant organizations in Exchange Online PowerShell. MFA and the Exchange Online Remote PowerShell Module don't work with delegated authentication. <br/>• The Exchange Online Remote PowerShell Module is not supported in PowerShell Core (macOS, Linux, or Windows Nano Server). As a workaround, you can install the module on a computer that's running a supported version of Windows (physical or virtual), and use remote desktop software to connect.
 
 ## What do you need to know before you begin?
 

exchange/docs-conceptual/exchange-server/recipient-filters/recipientfilter-properties.md

@@ -314,6 +314,6 @@ The recipient properties that have been  *confirmed*  to work with the _Recipien
 
 ## For more information
 
-Exchange 2007 was the first version of Exchange that required OPATH filters instead of LDAP filters. For more information about converting LDAP filters to OPATH filters, see the Microsoft Exchange Team Blog article, [Need help converting your LDAP filters to OPATH?](https://go.microsoft.com/fwlink/p/?LinkId=88854).
+Exchange 2007 was the first version of Exchange that required OPATH filters instead of LDAP filters. For more information about converting LDAP filters to OPATH filters, see the Microsoft Exchange Team Blog article, [Need help converting your LDAP filters to OPATH?](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Need-help-converting-your-LDAP-filters-to-OPATH/ba-p/595108).
 
 For more information about the syntax that can be used within OPATH filters, see [Exchange cmdlet syntax](../exchange-cmdlet-syntax.md).

exchange/docs-conceptual/office-365-scc/connect-to-scc-powershell/mfa-connect-to-scc-powershell.md

@@ -16,7 +16,7 @@ description: "Learn how to connect to Security & Compliance Center PowerShell by
 If your account uses multi-factor authentication (MFA) or federated authentication, you can't use the instructions at [Connect to Office 365 Security & Compliance Center PowerShell](connect-to-scc-powershell.md) to use remote PowerShell to connect to the Office 365 Security & Compliance Center. Instead, you need to install the Exchange Online Remote PowerShell Module, and use the **Connect-IPPSSession** cmdlet to connect to Security & Compliance Center PowerShell.
 
 > [!NOTE]
-> • You can't use the Exchange Online Remote PowerShell Module to connect to Exchange Online PowerShell and Security & Compliance Center PowerShell in the same session (window). You need to use separate sessions of the Exchange Online Remote PowerShell Module. <br/>• Delegated Access Permission (DAP) partners can't use the procedures in this topic to connect to their customer tenant organizations in Security & Compliance Center PowerShell. MFA and the Exchange Online Remote PowerShell Module don't work with delegated authentication. <br/>• The Exchange Online Remote PowerShell Module is not supported in PowerShell Core (macOS, Linux, or Windows Nano Server). As a workaround, you can install the module on a computer that's running a supported version of Windows (physical or virtual), and use remote desktop software to connect.
+> • Delegated Access Permission (DAP) partners can't use the procedures in this topic to connect to their customer tenant organizations in Security & Compliance Center PowerShell. MFA and the Exchange Online Remote PowerShell Module don't work with delegated authentication. <br/>• The Exchange Online Remote PowerShell Module is not supported in PowerShell Core (macOS, Linux, or Windows Nano Server). As a workaround, you can install the module on a computer that's running a supported version of Windows (physical or virtual), and use remote desktop software to connect.
 
 ## What do you need to know before you begin?
 
@@ -111,6 +111,19 @@ If your account uses multi-factor authentication (MFA) or federated authenticati
 4. **(MFA only)**: In the verification window that opens, enter the verification code, and then click **Sign in**.
 
     ![Enter your verification code in the Exchange Online Remote PowerShell window](../../media/d3a405ce-5364-4732-a7bb-2cc9c678da2d.png)
+    
+5. **(Optional)**: If you want to connect to an Exchange Online PowerShell module session in the same window, you need to run
+
+    ```
+    $EXOSession=New-ExoPSSSession -UserPrincipalName <UPN> [-ConnectionUri <ConnectionUri> -AzureADAuthorizationEndPointUri <AzureADUri>]
+    ```
+    
+    and then import the Exchange Online session into the current one using an specific prefix
+    
+    ```
+    Import-PSSession $EXOSession -Prefix EXO
+    ```
+    
 
 ## How do you know this worked?
 

exchange/exchange-ps/exchange/antispam-antimalware/Set-HostedOutboundSpamFilterPolicy.md

@@ -22,9 +22,13 @@ For information about the parameter sets in the Syntax section below, see Exchan
 
 ```
 Set-HostedOutboundSpamFilterPolicy [-Identity] <HostedOutboundSpamFilterPolicyIdParameter>
- [-AdminDisplayName <String>] [-BccSuspiciousOutboundAdditionalRecipients <MultiValuedProperty>]
- [-BccSuspiciousOutboundMail <$true | $false>] [-Confirm] [-NotifyOutboundSpam <$true | $false>]
- [-NotifyOutboundSpamRecipients <MultiValuedProperty>] [-WhatIf] [<CommonParameters>]
+ [-AdminDisplayName <String>]
+ [-BccSuspiciousOutboundAdditionalRecipients <MultiValuedProperty>]
+ [-BccSuspiciousOutboundMail <$true | $false>]
+ [-Confirm]
+ [-NotifyOutboundSpam <$true | $false>]
+ [-NotifyOutboundSpamRecipients <MultiValuedProperty>]
+ [-WhatIf] [<CommonParameters>]
 ```
 
 ## DESCRIPTION

exchange/exchange-ps/exchange/database-availability-groups/Set-DatabaseAvailabilityGroup.md

@@ -256,7 +256,7 @@ Accept wildcard characters: False
 ```
 
 ### -AutoDagBitlockerEnabled
-This parameter is reserved for internal Microsoft use.
+The AutoDagBitlockerEnabled parameter ensures that Disk Reclaimer handles spare disks correctly and encrypts them with BitLocker. If Bitlocker is used to encrypt database disks, set the value of this parameter to $true on all Mailbox servers in the DAG after they are all running Exchange 2013 CU13 or later, or Exchange 2016 CU2 or later.
 
 ```yaml
 Type: $true | $false

exchange/exchange-ps/exchange/devices/New-ActiveSyncMailboxPolicy.md

@@ -16,7 +16,7 @@ This cmdlet is available in on-premises Exchange and in the cloud-based service.
 
 Use the New-ActiveSyncMailboxPolicy cmdlet to create a Microsoft Mobile Device mailbox policy object.
 
-Note: In Exchange 2013 or later, use the New-MobileMailboxPolicy cmdlet instead. If you have scripts that use New-ActiveSyncMailboxPolicy, update them to use New-MobileMailboxPolicy.
+Note: In Exchange 2013 or later, use the New-MobileDeviceMailboxPolicy cmdlet instead. If you have scripts that use New-ActiveSyncMailboxPolicy, update them to use New-MobileDeviceMailboxPolicy.
 
 For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).
 

exchange/exchange-ps/exchange/encryption-and-certificates/Set-IRMConfiguration.md

@@ -119,7 +119,7 @@ The AzureRMSLicensingEnabled parameter specifies whether the Exchange Online org
 
 - $true: The Exchange Online organization can connect directly to Azure Rights Management. This enables Office 365 Message Encryption.
 
-- $false: The Exchange Online organization can't connect directly to Azure Rights Management. Do not configure this value unless you're directed to do so by Microsoft Customer Service and Support.
+- $false: The Exchange Online organization can't connect directly to Azure Rights Management.
 
 ```yaml
 Type: $true | $false
@@ -136,11 +136,11 @@ Accept wildcard characters: False
 ### -ClientAccessServerEnabled
 This parameter is available only in on-premises Exchange.
 
-The ClientAccessServerEnabled parameter specifies whether to enable IRM for Outlook on the web (formerly known as Outlook Web App) and Exchange ActiveSync. Valid values are:
+The ClientAccessServerEnabled parameter specifies whether Exchange Client Access servers are allowed to authenticate clients that do not have direct access to AD RMS (for example, Outlook on the web, Exchange ActiveSync or remote Outlook Anywhere clients). Valid values are:
 
-- $true: IRM is enabled for Outlook on the web and Exchange ActiveSync. This is the default value. Note that enabling IRM in Outlook on the web requires additional configuration on AD RMS servers. For more information, see Information Rights Management in Outlook Web App (https://technet.microsoft.com/library/dd876891.aspx).
+- $true: Client Access servers are allowed to authenticate clients. This is the default value. Note that enabling IRM in Outlook on the web requires additional configuration on AD RMS servers. For more information, see Information Rights Management in Outlook Web App (https://technet.microsoft.com/library/dd876891.aspx).
 
-- $false: IRM is disabled for Outlook on the web and Exchange ActiveSync.
+- $false: Client Access servers aren't allowed to authenticate clients.
 
 ```yaml
 Type: $true | $false

exchange/exchange-ps/exchange/mail-flow/Start-HistoricalSearch.md

@@ -286,7 +286,7 @@ Required: False
 Position: Named
 Default value: None
 Accept pipeline input: False
-Accept wildcard characters: False
+Accept wildcard characters: True
 ```
 
 ### -SenderAddress

exchange/exchange-ps/exchange/mailbox-databases-and-servers/Move-DatabasePath.md

@@ -33,7 +33,7 @@ When you use the Move-DatabasePath cmdlet, consider the following:
 
 - If the specified database is mounted when this cmdlet is run, the database is automatically dismounted and then remounted, and is unavailable to users while it's dismounted.
 
-- This cmdlet normally can be run on the affected Mailbox server only. An exception is that this cmdlet can be run on an administrator's workstation when using the ConfigurationOnly parameter with a value of $true.
+- In Exchange 2013 or earlier, you can only run this cmdlet on the affected Mailbox server. If you include the ConfigurationOnly parameter with the value $true, you can run the cmdlet on an administrator's workstation. This does not apply to Exchange 2016 or later (you can run the cmdlet anywhere).
 
 - This cmdlet can't be run against replicated mailbox databases. To move the path of a replicated database, you must first remove all replicated copies, and then you can perform the move operation. After the move operation is complete, you can add copies of the mailbox database.
 

exchange/exchange-ps/exchange/mailboxes/Get-Mailbox.md

@@ -278,23 +278,6 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -Properties
-This parameter is available only in the cloud-based service.
-
-{{Fill Properties Description}}
-
-```yaml
-Type: String[]
-Parameter Sets: AsyncParameterSet
-Aliases:
-Applicable: Exchange Online
-Required: True
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
 ### -AuditLog
 This parameter is available only in on-premises Exchange.
 

exchange/exchange-ps/exchange/mailboxes/New-MailboxImportRequest.md

@@ -14,7 +14,7 @@ monikerRange: "exchserver-ps-2010 || exchserver-ps-2013 || exchserver-ps-2016 ||
 ## SYNOPSIS
 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 New-MailboxImportRequest cmdlet to begin the process of importing a .pst file to a mailbox or archive that's hosted in on-premises Exchange. Importing .pst files is not possible in Exchange Online.
+Use the New-MailboxImportRequest cmdlet to begin the process of importing a .pst file to a mailbox or archive.
 
 This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export role to a role group (for example, to the Organization Management role group). For more information, see the "Add a role to a role group" section in Manage role groups (https://technet.microsoft.com/library/jj657480.aspx).
 

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

@@ -73,6 +73,7 @@ Set-Mailbox [-Identity] <MailboxIdParameter>
  [-DefaultAuditSet <MultiValuedProperty>]
  [-DefaultPublicFolderMailbox <RecipientIdParameter>]
  [-DeliverToMailboxAndForward <$true | $false>]
+ [-DisableThrottling <$true | $false>]
  [-DisplayName <String>]
  [-DomainController <Fqdn>]
  [-DowngradeHighPriorityMessagesEnabled <$true | $false>]
@@ -100,6 +101,7 @@ Set-Mailbox [-Identity] <MailboxIdParameter>
  [-ForwardingSmtpAddress <ProxyAddress>]
  [-GMGen <$true | $false>]
  [-GrantSendOnBehalfTo <MultiValuedProperty>]
+ [-GroupMailbox <MailboxIdParameter>]
  [-HiddenFromAddressListsEnabled <$true | $false>]
  [-IgnoreDefaultScope]
  [-ImListMigrationCompleted <$true | $false>]
@@ -380,6 +382,7 @@ Set-Mailbox [-Identity] <MailboxIdParameter> [-RemoveDelayHoldApplied]
  [-ForwardingAddress <RecipientIdParameter>]
  [-ForwardingSmtpAddress <ProxyAddress>]
  [-GrantSendOnBehalfTo <MultiValuedProperty>]
+ [-GroupMailbox <MailboxIdParameter>]
  [-HiddenFromAddressListsEnabled <$true | $false>]
  [-ImListMigrationCompleted <$true | $false>]
  [-ImmutableId <String>]
@@ -1563,6 +1566,8 @@ The AuditEnabled parameter specifies whether to enable or disable mailbox audit
 
 - $false: Mailbox audit logging is disabled. This is the default value.
 
+**Note**: In Exchange Online, mailbox auditing on by default was enabled for all organizations in January, 2019. For more information, see [Manage mailbox auditing](https://docs.microsoft.com/office365/securitycompliance/enable-mailbox-auditing).
+
 ```yaml
 Type: $true | $false
 Parameter Sets: (All)
@@ -2210,6 +2215,27 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -DisableThrottling
+This parameter is available only in on-premises Exchange.
+
+The DisableThrottling parameter enables or disables sender rate throttling for the mailbox. Valid values are:
+
+- $true: Messages sent by this mailbox will not be throttled by Sender Rate Control. We only recommend this value for moderation mailboxes.
+
+- $false: Messages will be throttled after the threshold is exceeded. This is the default value.
+
+```yaml
+Type: $true | $false
+Parameter Sets: (All)
+Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
+Required: False
+Position: Named
+Default value: False
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -DisplayName
 The DisplayName parameter specifies the display name of the mailbox. The display name is visible in the Exchange admin center, in address lists, and in Outlook. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -2858,6 +2884,45 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -GroupMailbox
+This parameter is available only in the cloud-based service.
+
+The GroupMailbox switch is required to modify Group Mailboxes in Exchange Online. You don't need to specify a value with this switch.
+
+You can use any value that uniquely identifies the Group Mailbox. For example:
+
+- Name
+
+- Alias
+
+- Distinguished name (DN)
+
+- Canonical DN
+
+- \<domain name\>\\\<account name\>
+
+- Email address
+
+- GUID
+
+- LegacyExchangeDN
+
+- SamAccountName
+
+- User ID or user principal name (UPN)
+
+```yaml
+Type: MailboxIdParameter
+Parameter Sets: Identity, RemoveDelayHoldApplied
+Aliases:
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -HiddenFromAddressListsEnabled
 The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are:
 
@@ -4243,6 +4308,8 @@ The RemoveDelayHoldApplied switch specifies whether to remove delay holds from t
 
 The removal of a hold from a mailbox is temporarily delayed to prevent the accidental purge of content that's no longer affected by the hold. This temporary delay in the removal of the hold is known as a delay hold. To see the hold history on a mailbox, replace \<MailboxIdentity\> with the name, email address, or alias of the mailbox, and run this command: Export-MailboxDiagnosticLogs -Identity \<MailboxIdentity\> -ComponentName HoldTracking.
 
+You can use this switch with the GroupMailbox switch to remove delay holds from group mailboxes.
+
 ```yaml
 Type: SwitchParameter
 Parameter Sets: RemoveDelayHoldApplied

exchange/exchange-ps/exchange/mailboxes/Set-Place.md

@@ -29,11 +29,10 @@ Set-Place [-Identity] <RecipientIdParameter>
  [-Confirm]
  [-CountryOrRegion <CountryInfo>]
  [-DisplayDeviceName <String>]
- [-FloorNumber <System.Int32>]
+ [-Floor <System.Int32>]
  [-GeoCoordinates <GeoCoordinates>]
  [-IsWheelChairAccessible <$true | $false>]
  [-Label <String>]
- [-Nickname <String>]
  [-Phone <String>]
  [-PostalCode <String>]
  [-State <String>]
@@ -197,8 +196,8 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -FloorNumber
-The FloorNumber parameter specifies the floor number that the room is on. If the value contains spaces, enclose the value in quotation marks (").
+### -Floor
+The Floor parameter specifies the floor number that the room is on.
 
 ```yaml
 Type: System.Int32
@@ -265,21 +264,6 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -Nickname
-The Nickname parameter specifies a nickname for the room (for example, conf room). If the value contains spaces, enclose the value in quotation marks (").
-
-```yaml
-Type: String
-Parameter Sets: (All)
-Aliases:
-Applicable: Exchange Online
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
 ### -Phone
 The Phone parameter specifies the room's telephone number.