Merge branch 'master' into maesfaha/UpdateSetAndRemove

Author: kenwith

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/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

@@ -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/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/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>]
@@ -2212,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 (").
 
@@ -2860,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:
 
@@ -4245,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/organization/New-ApplicationAccessPolicy.md

@@ -59,7 +59,7 @@ This example creates a new application access policy with the following settings
 
 ### -------------------------- Example 2 --------------------------
 ```
-New-ApplicationAccessPolicy -AccessRight RestrictAccess -AppId e7e4dbfc-046f-4074-9b3b-2ae8f144f59b -PolicyScopeGroupId [email protected] -Description "Restrict this app to members of distribution group EvenUsers." 
+New-ApplicationAccessPolicy -AccessRight RestrictAccess -AppId e7e4dbfc-046f-4074-9b3b-2ae8f144f59b -PolicyScopeGroupId [email protected] -Description "Restrict this app to members of security group EvenUsers." 
 ```
 
 This example creates a new application access policy with the following settings:
@@ -70,13 +70,13 @@ This example creates a new application access policy with the following settings
 
 - PolicyScopeGroupId: [email protected]
 
-- Description: Restrict this app to members of distribution group EvenUsers.
+- Description: Restrict this app to members of security group EvenUsers.
 
 
 
 ### -------------------------- Example 3 --------------------------
 ```
-New-ApplicationAccessPolicy -AccessRight DenyAccess -AppId e7e4dbfc-046f-4074-9b3b-2ae8f144f59b -PolicyScopeGroupId [email protected] -Description "Deny this app access to members of distribution group OddUsers." 
+New-ApplicationAccessPolicy -AccessRight DenyAccess -AppId e7e4dbfc-046f-4074-9b3b-2ae8f144f59b -PolicyScopeGroupId [email protected] -Description "Deny this app access to members of security group OddUsers." 
 ```
 
 This example creates a new application access policy with the following settings:
@@ -87,7 +87,7 @@ This example creates a new application access policy with the following settings
 
 - PolicyScopeGroupId: [email protected]
 
-- Description: Deny this app access to members of distribution group OddUsers.
+- Description: Deny this app access to members of security group OddUsers.
 
 ## PARAMETERS
 
@@ -128,7 +128,7 @@ Accept wildcard characters: False
 ```
 
 ### -PolicyScopeGroupID
-The PolicyScopeGroupID parameter specifies the recipient to define in the policy. You can use any value that uniquely identifies the recipient. You can also specify a mail enabled security group or a distribution group or a dynamic distribution group to restrict/deny access to a large number of user mailboxes. 
+The PolicyScopeGroupID parameter specifies the recipient to define in the policy. You can use any value that uniquely identifies the recipient. You can also specify a mail enabled security group to restrict/deny access to a large number of user mailboxes. 
 For example:
 
 - Name

exchange/exchange-ps/exchange/policy-and-compliance-content-search/New-ComplianceSearchAction.md

@@ -91,6 +91,8 @@ In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By
 
 You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not 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://technet.microsoft.com/library/mt432940.aspx).
 
+In Office 365, the account that you use to run this cmdlet must have a valid Office 365 license assigned.
+
 You need to be assigned permissions in the Office 365 Security & Compliance Center before you can use this cmdlet. For more information, see Permissions in Office 365 Security & Compliance Center (https://go.microsoft.com/fwlink/p/?LinkId=511920).
 
 ## EXAMPLES

exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpComplianceRule.md

@@ -457,6 +457,8 @@ The IncidentReportContent parameter specifies the content to include in the repo
 
 - Default
 
+- DetectionDetails
+
 - Detections
 
 - DocumentAuthor
@@ -465,6 +467,8 @@ The IncidentReportContent parameter specifies the content to include in the repo
 
 - MatchedItem
 
+- OriginalContent
+
 - RulesMatched
 
 - Service

officewebapps/docs-conceptual/index.md

@@ -1,3 +1,7 @@
+---
+title: Office Online Server cmdlet reference
+---
+
 # Office Online Server cmdlet reference
 Welcome to the Office Online Server PowerShell cmdlet help references. The Office Online Server cmdlets provide the command line interface for administration and management.
 

officewebapps/docs-conceptual/intro.md

@@ -1,3 +1,7 @@
+---
+title: Office Online Server cmdlet reference
+---
+
 # Office Online Server cmdlet reference
 Welcome to the Office Online Server PowerShell cmdlet help references. The Office Online Server cmdlets provide the command line interface for administration and management.
 

sharepoint/docs-conceptual/sharepoint-online/connect-sharepoint-online.md

@@ -1,3 +1,7 @@
+---
+title: Getting started with SharePoint Online Management Shell
+---
+
 # Getting started with SharePoint Online Management Shell #
 
 Before you get started using PowerShell to manage SharePoint Online, make sure that the SharePoint Online Management Shell is installed and you have connected to SharePoint Online.

sharepoint/docs-conceptual/sharepoint-online/introduction-sharepoint-online-management-shell.md

@@ -1,3 +1,7 @@
+---
+title: What is the SharePoint Online Management Shell
+---
+
 # What is the SharePoint Online Management Shell?
 
 The SharePoint Online Management Shell is a Windows PowerShell module that you can use to manage SharePoint Online users, sites, and site collections. Command-line operations in Windows PowerShell are composed of a series of commands. Each command uses a cmdlet and a set of settings known as parameters. For example, you use the **New-SPOSite** cmdlet for a command that creates a new SharePoint Online site collection with a specified title, URL, owner, storage quota, and template (the parameters).

sharepoint/sharepoint-ps/sharepoint-server/Set-SPSiteSubscriptionConfig.md

@@ -32,10 +32,10 @@ For permissions and the most current information about Windows PowerShell for Sh
 
 ### --------------------EXAMPLE---------------------
 ```
-Set-SPSiteSubscription https://contoso.com -FeatureSet 12345678-90ab-cdef-1234-567890abcdef
+Set-SPSiteSubscriptionConfig https://contoso.com -FeaturePack 12345678-90ab-cdef-1234-567890abcdef
 ```
 
-This example sets the Feature set of the entire site subscription that contains https://contoso.com with a Feature set GUID.
+This example sets the Feature set of the entire site subscription that contains https://contoso.com with a Feature pack GUID.
 
 
 ## PARAMETERS

skype/docs-conceptual/index.md

@@ -1,5 +1,6 @@
 ---
 localization_priority: Normal
+title: Skype for Business cmdlet reference
 ---
 
 # Skype for Business cmdlet reference

skype/docs-conceptual/intro.md

@@ -1,5 +1,6 @@
 ---
 localization_priority: Normal
+title: Skype for Business cmdlet reference
 ---
 
 # Skype for Business cmdlet reference

skype/skype-ps/skype/Move-CsUser.md

@@ -20,7 +20,7 @@ Moves one or more user accounts enabled for Skype for Business Server to a new R
 ### (Default)
 
 ```
-Move-CsUser [-Identity] <UserIdParameter> [-Target] <Fqdn> [-Credential <PSCredential>] [-MoveToTeams] [-HostedMigrationOverrideUrl <String>] [-BypassEnterpriseVoiceCheck] [-BypassAudioConferencingCheck] [-TenantAdminUserName] [-MoveConferenceData] [-Confirm] [-Force] [-PassThru] [-WhatIf]  [<CommonParameters>]
+Move-CsUser [-Identity] <UserIdParameter> [-Target] <Fqdn> [-Credential <PSCredential>] [-MoveToTeams] [-HostedMigrationOverrideUrl <String>] [-UseOAuth] [-BypassEnterpriseVoiceCheck] [-BypassAudioConferencingCheck] [-TenantAdminUserName] [-MoveConferenceData] [-Confirm] [-Force] [-PassThru] [-WhatIf]  [<CommonParameters>]
 ```
 
 ## DESCRIPTION
@@ -46,7 +46,10 @@ When moving a user to or from Office 365 (either Skype for Business Online or Te
 - Contacts are moved in all cases, unless -force is specified.
 
 > [!NOTE]
-> The MoveToTeams switch is only available on Skype for Business Server 2019 and CU8 for Skype for Business Server 2015. Organizations using other versions of Skype for Business Server must first move the user to Skype for Business Online, and then apply TeamsUpgradePolicy.
+> <ul><li>The MoveToTeams switch is only available on Skype for Business Server 2019 and CU8 for Skype for Business Server 2015. Organizations using other versions of Skype for Business Server must first move the user to Skype for Business Online, and then apply TeamsUpgradePolicy.</li><li>If you are using Skype for Business Server 2015 with CU8 or later, we recommend you pass the `-UseOAuth` switch, which ensures the on-premises code authenticates using OAuth, instead of Legacy LiveID authentication. In Skype for Business Server 2019 and later versions, OAuth is always used hence the switch is not relevant on those versions.</li></ul>
+
+
+
 
 ## EXAMPLES
 
@@ -178,6 +181,22 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -UseOAuth
+
+If specified, authentication between on-premises and the host migration service is based on OAuth protocol. Otherwise, authentication is based on legacy LiveID authentication.  This parameter is only available with Skype for Business Server 2015 with CU8 or later. In Skype for Business Server 2019 and later versions, OAuth is always used hence the switch is not relevant on those versions.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases:
+Applicable: Skype for Business Server 2015
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -BypassAudioConferencingCheck
 
 By default, if the on-premise user is configured for dial in conferencing, moving the user to Office 365 will provision the user for Audio Conferencing, for an additional license is required.  If you want to move such a user to Office 365 but do not want to configure them for Audio Conferencing, specify this switch to by-pass the license check. This parameter is only available with Skype for Business Server 2019 and CU8 for Skype for Business Server 2015.

skype/skype-ps/skype/New-CsHybridApplicationEndpoint.md

@@ -42,7 +42,11 @@ This example creates a hybrid application endpoint named NewBot1 in Skype for Bu
 ## PARAMETERS
 
 ### -ApplicationId
-The ApplicationId for the application endpoint that is being created.
+The ApplicationId or Client Id for which the endpoint is being created.
+
+There are predefined values if you are creating an on-premises resource account for Skype for Business hybrid deployments:
+* Auto Attendant: ce933385-9390-45d1-9512-c8d228074e07
+* Call Queue: 11cd3e2e-fccb-42ad-ad00-878b93575e07
 
 ```yaml
 Type: Guid