Merge branch 'master' into patch-290

Author: Kateyanne

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

@@ -121,25 +121,27 @@ If you encounter problems, check the [required permssions](https://docs.microsof
 
 You need to assign the API permission `Exchange.ManageAsApp` so the application can manage Exchange Online. API permissions are required because they have consent flow enabled, which allows auditing (directory roles don't have consent flow).
 
-1. Select **API permissions**.
+1. Select **Manifest** in the left-hand navigation under **Manage**.
 
-2. In the **Configured permissions** page that appears, click **Add permission**.
+2. Locate the `requiredResourceAccess` property in the manifest, and add the following inside the square brackets (`[]`):
 
-3. In the flyout that appears, select **Exchange**.
+   ```json
+   {
+       "resourceAppId": "00000002-0000-0ff1-ce00-000000000000",
+       "resourceAccess": [
+           {
+               "id": "dc50a0fb-09a3-484d-be87-e023b12c6440",
+               "type": "Role"
+           }
+       ]
+   }
+   ```
 
-   ![Select Exchange API permssions](media/app-only-auth-exchange-api-perms.png)
+3. Select **Save**.
 
-4. In the flyout that appears, click **Application permissions**.
+4. Select **API permissions** under **Manage**. Confirm that the **Exchange.ManageAsApp** permission is listed.
 
-5. In the **Select permissions** section that appears on the page, expand **Exchange** and select **Exchange.ManageAsApp**
-
-   ![Select Exchange.ManageAsApp permssions](media/app-only-auth-exchange-manageasapp.png)
-
-   When you're finished, click **Add permissions**.
-
-6. Back on the **Configured permissions** page that appears, click **Grant admin consent for \<tenant name\>**, and select **Yes** in the dialog that appears.
-
-7. Close the flyout when you're finished.
+5. Select **Grant admin consent for org** and accept the consent dialog.
 
 ## Step 3: Generate a self-signed certificate
 

exchange/exchange-ps/exchange/New-Mailbox.md

@@ -1693,7 +1693,11 @@ Accept wildcard characters: False
 ### -MailboxRegion
 This parameter is available only in the cloud-based service.
 
-This parameter is reserved for internal Microsoft use.
+The MailboxRegion parameter specifies the geo location for the mailbox in multi-geo environments.
+
+To see the list of configured geo locations in Microsoft 365 Multi-Geo, run the following command: `Get-OrganizationConfig | Select -ExpandProperty AllowedMailboxRegions | Format-Table`. To view your central geo location, run the following command: `Get-OrganizationConfig | Select DefaultMailboxRegion`.
+
+ For more information, see [Administering Exchange Online mailboxes in a multi-geo environment](https://docs.microsoft.com/microsoft-365/enterprise/administering-exchange-online-multi-geo).
 
 ```yaml
 Type: String

exchange/exchange-ps/exchange/New-UnifiedGroup.md

@@ -128,7 +128,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 
 ### Example 1
 ```powershell
-New-UnifiedGroup -DisplayName "Engineering Department" -Alias engineering
+New-UnifiedGroup -DisplayName "Engineering Department" -Alias "engineering"
 ```
 
 This example creates a new Microsoft 365 Group named Engineering Department.

exchange/exchange-ps/exchange/Search-UnifiedAuditLog.md

@@ -47,6 +47,10 @@ If you want to programmatically download data from the Microsoft 365 audit log,
 
 This cmdlet is available in Office 365 operated by 21Vianet, but it won't return any results.
 
+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`
+
 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://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
@@ -58,7 +62,7 @@ Search-UnifiedAuditLog -StartDate 5/1/2018 -EndDate 5/2/2018
 
 This example searches the unified audit log for all events from May 1, 201812:00AM to May 2, 2018 12:00AM.
 
-Note: If you don't include a timestamp in the value for the StartDate or EndDate parameters, the default timestamp 12:00 AM (midnight) is used.
+**Note**: If you don't include a timestamp in the value for the StartDate or EndDate parameters, the default timestamp 12:00 AM (midnight) is used.
 
 ### Example 2
 ```powershell
@@ -67,8 +71,7 @@ Search-UnifiedAuditLog -StartDate "6/1/2018 8:00 AM" -EndDate "6/1/2018 6:00 PM"
 
 This example searches the unified audit log for all Exchange admin events from 8:00 AM to 6:00 PM on June 1, 2018.
 
->[!NOTE]
-> If you use the same date for the StartDate and EndDate parameters, you have to include a timestamp; otherwise, no results will be returned because the date and time for the start and end dates will be the same.
+**Note** If you use the same date for the StartDate and EndDate parameters, you need to include a timestamp; otherwise, no results will be returned because the date and time for the start and end dates will be the same.
 
 ### Example 3
 ```powershell
@@ -77,9 +80,7 @@ Search-UnifiedAuditLog -StartDate 5/1/2018 -EndDate 5/8/2018 -SessionId "Unified
 
 This example searches the unified audit log for all events from May 1, 2018 to May 8, 2018. If you don't include a time stamp in the StartDate or EndDate parameters, The data is returned in pages as the command is rerun sequentially while using the same SessionId value.
 
->
- [!NOTE]
-> If you use the SessionCommand value ReturnLargeSet, and then you use the value ReturnNextPreviewPage for the same session ID, the results are limited to 10,000 records (not 50,000).
+**Note**: Always use the same SessionCommand value for a given SessionId value. Don't switch between ReturnLargeSet and ReturnNextPreviewPage for the same session ID. Otherwise, the output is limited to 10,000 results.
 
 ### Example 4
 ```powershell
@@ -269,7 +270,7 @@ The SessionCommand parameter specifies how much information is returned and how
 - ReturnNextPreviewPage: This value causes the cmdlet to return data sorted on date. The maximum number of records returned through use of either paging or the ResultSize parameter is 5,000 records.
 - ReturnLargeSet: This value causes the cmdlet to return unsorted data. By using paging, you can access a maximum of 50,000 results.
 
-**Note**: Always use the same SessionCommand value for a given SessionId value. Don't switch between ReturnLargeSet and ReturnNextPreviewPage for the same session ID.
+**Note**: Always use the same SessionCommand value for a given SessionId value. Don't switch between ReturnLargeSet and ReturnNextPreviewPage for the same session ID. Otherwise, the output is limited to 10,000 results.
 
 ```yaml
 Type: UnifiedAuditSessionCommand
@@ -348,9 +349,6 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 ## OUTPUTS
 
 ###  
-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
 
 ## NOTES
 

exchange/exchange-ps/exchange/Set-ActiveSyncOrganizationSettings.md

@@ -101,6 +101,8 @@ Accept wildcard characters: False
 ```
 
 ### -AllowRMSSupportForUnenlightenedApps
+This parameter is available or functional only in the cloud-based service.
+
 The AllowRMSSupportForUnenlightenedApps parameter specifies whether to allow Rights Management Services (RMS) protected messages for ActiveSync clients that don't support RMS. Valid values are:
 
 - $true

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

@@ -3422,7 +3422,11 @@ Accept wildcard characters: False
 ### -MailboxRegion
 This parameter is available only in the cloud-based service.
 
-This parameter is reserved for internal Microsoft use.
+The MailboxRegion parameter specifies the geo location for the mailbox in multi-geo environments.
+
+To see the list of configured geo locations in Microsoft 365 Multi-Geo, run the following command: `Get-OrganizationConfig | Select -ExpandProperty AllowedMailboxRegions | Format-Table`. To view your central geo location, run the following command: `Get-OrganizationConfig | Select DefaultMailboxRegion`.
+
+ For more information, see [Administering Exchange Online mailboxes in a multi-geo environment](https://docs.microsoft.com/microsoft-365/enterprise/administering-exchange-online-multi-geo).
 
 ```yaml
 Type: String

officewebapps/docs-conceptual/index.md

@@ -1,9 +1,12 @@
 ---
-title: Office Online Server cmdlet reference
+title: Office Online Server cmdlet help reference
+description: "Learn about the Office Online Server PowerShell cmdlet help 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.
+# Office Online Server cmdlet help reference
 
-Here you will find all of the Office Online Server PowerShell help topics. These topics are 'open source' and open for contributions. If you are interested in contributing to this content head over to the source GitHub repo and look through the README.
-The repo is located here: https://github.com/microsoftdocs/office-docs-powershell and you can find the README displayed at the bottom of the page.
+Welcome to the Office Online Server PowerShell cmdlet **Help** reference. The Office Online Server cmdlets provide the command line interface for administration and management.
+
+Here, you will find all of the Office Online Server PowerShell **Help** topics. These topics are 'open source' and open for contributions. If you are interested in contributing to this content, go to the source GitHub repo and look through the README.
+
+The repo is located here: <https://github.com/microsoftdocs/office-docs-powershell> and you can find the README displayed at the bottom of the page.

sharepoint/sharepoint-ps/sharepoint-online/New-SPOSdnProvider.md

@@ -57,7 +57,7 @@ Accept wildcard characters: False
 
 ### -Identity
 
-PARAMVALUE: String
+Identity of the provider.
 
 ```yaml
 Type: String
@@ -74,7 +74,7 @@ Accept wildcard characters: False
 
 ### -License
 
-PARAMVALUE: String
+License key provided by the provider.
 
 ```yaml
 Type: String

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSite.md

@@ -35,7 +35,8 @@ Set-SPOSite [-Identity] <SpoSitePipeBind> [-AllowSelfServiceUpgrade <Boolean>] [
  [-SharingBlockedDomainList <String>] [-SharingDomainRestrictionMode <SharingDomainRestrictionModes>]
  [-ShowPeoplePickerSuggestionsForGuestUsers <Boolean>] [-StorageQuotaReset]
  [-DefaultSharingLinkType] [-DefaultLinkPermission] [-DefaultLinkToExistingAccess]
- [-ConditionalAccessPolicy <SPOConditionalAccessPolicyType>] [-LimitedAccessFileType <SPOLimitedAccessFileType>] [-AllowEditing <Boolean>] [-AnonymousLinkExpirationInDays <Int32>] [-OverrideTenantAnonymousLinkExpirationPolicy <Boolean>] [-SensitivityLabel <String>][<CommonParameters>]
+ [-ConditionalAccessPolicy <SPOConditionalAccessPolicyType>] [-LimitedAccessFileType <SPOLimitedAccessFileType>] [-AllowEditing <Boolean>] [-AnonymousLinkExpirationInDays <Int32>] [-OverrideTenantAnonymousLinkExpirationPolicy <Boolean>] [-SensitivityLabel <String>]
+ [-RemoveLabel] [<CommonParameters>]
 ```
 
 ### ParamSet2
@@ -897,6 +898,20 @@ Position: Named
 Default value: None
 ```
 
+### -RemoveLabel
+This parameter allows you to remove the assigned sensitivity label on a site.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: ParamSet5
+Aliases:
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### CommonParameters
 
 This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).

skype/docs-conceptual/index.md

@@ -1,15 +1,16 @@
 ---
 localization_priority: Normal
-title: Skype for Business cmdlet reference
+title: Skype for Business cmdlet help reference
+description: "Learn about the Skype for Business PowerShell cmdlet help reference."
 ---
 
-# Skype for Business cmdlet reference
+# Skype for Business cmdlet help reference
 
-Welcome to the Skype for Business PowerShell cmdlet help references. The Skype for Business cmdlets provide the command line interface for server and service administration and management.
+Welcome to the Skype for Business PowerShell cmdlet **Help** reference. The Skype for Business cmdlets provide the command line interface for server and service administration and management.
 
 > [!IMPORTANT]
-> As you migrate to Microsoft Teams you will find that some of the cmdlets in the Skype for Business Online module are also used for Microsoft Teams. To learn more about this, see: [Teams PowerShell Overview](https://docs.microsoft.com/MicrosoftTeams/teams-powershell-overview).
+> As you migrate to Microsoft Teams, you will find that some of the cmdlets in the Skype for Business Online module are also used for Microsoft Teams. To learn more about this, see: [Teams PowerShell Overview](https://docs.microsoft.com/MicrosoftTeams/teams-powershell-overview).
 
-Here you will find all of the Skype for Business and relevant Microsoft Teams PowerShell help topics. These topics are 'open source' and open for contributions. If you are interested in contributing to this content head over to the source GitHub repo and look through the README. 
+Here, you will find all of the Skype for Business and relevant Microsoft Teams PowerShell **Help** topics. These topics are 'open source' and open for contributions. If you are interested in contributing to this content, go to the source GitHub repo and look through the README.
 
-The repo is located here: https://github.com/microsoftdocs/office-docs-powershell and you can find the README displayed at the bottom of the page.
+The repo is located here: <https://github.com/microsoftdocs/office-docs-powershell> and you can find the README displayed at the bottom of the page.

spmt/docs-conceptual/index.md

@@ -1,12 +1,13 @@
 ---
 localization_priority: Normal
-title: Microsoft SharePoint Migration Tool cmdlet reference
+title: Microsoft SharePoint Migration Tool cmdlet help reference
+description: "Learn about the Microsoft SharePoint Migration Tool PowerShell cmdlet help reference."
 ---
 
-# Microsoft SharePoint Migration Tool cmdlet reference
+# Microsoft SharePoint Migration Tool cmdlet help reference
 
-Welcome to the Microsoft SharePoint Migration Tool PowerShell cmdlet help references. The Microsoft SharePoint Migration Tool cmdlets provide the command line interface for service administration and management.
+Welcome to the Microsoft SharePoint Migration Tool PowerShell cmdlet **Help** reference. The Microsoft SharePoint Migration Tool cmdlets provide the command line interface for service administration and management.
 
-Here you will find all of the Microsoft SharePoint Migration Tool PowerShell help topics. These topics are 'open source' and open for contributions. If you are interested in contributing to this content head over to the source GitHub repo and look through the README. 
+Here, you will find all of the Microsoft SharePoint Migration Tool PowerShell **Help** topics. These topics are 'open source' and open for contributions. If you are interested in contributing to this content, go to the source GitHub repo and look through the README.
 
-The repo is located here: https://github.com/microsoftdocs/office-docs-powershell and you can find the README displayed at the bottom of the page.
+The repo is located here: <https://github.com/microsoftdocs/office-docs-powershell> and you can find the README displayed at the bottom of the page.

staffhub/docs-conceptual/index.md

@@ -1,15 +1,16 @@
 ---
-title: Microsoft StaffHub cmdlet reference
+title: Microsoft StaffHub cmdlet help reference
+description: "Learn about the Microsoft StaffHub PowerShell cmdlet help reference."
 ---
 
-# Microsoft StaffHub cmdlet reference
+# Microsoft StaffHub cmdlet help reference
 
-Welcome to the Microsoft StaffHub cmdlet help references. The Microsoft StaffHub cmdlets provide the command line interface for service administration and management.
+Welcome to the Microsoft StaffHub cmdlet **Help** reference. The Microsoft StaffHub cmdlets provide the command line interface for service administration and management.
 
-Here you will find all of the Microsoft StaffHub PowerShell help topics. The reference documentation can be found here: https://docs.microsoft.com/powershell/module/staffhub/?view=staffhub-ps
+Here, you will find all of the Microsoft StaffHub PowerShell **Help** topics. The reference documentation can be found here: <https://docs.microsoft.com/powershell/module/staffhub>
 
-Instructions on installing the StaffHub cmdlet module can be found here: https://www.powershellgallery.com/packages/MicrosoftStaffHub/1.0.0-alpha
+Instructions on installing the StaffHub cmdlet module can be found here: <https://www.powershellgallery.com/packages/MicrosoftStaffHub/1.0.0-alpha>.
 
-These topics are 'open source' and open for contributions. If you are interested in contributing to this content head over to the source GitHub repo and look through the README. 
+These **Help** topics are 'open source' and open for contributions. If you are interested in contributing to this content, go to the source GitHub repo and look through the README.
 
-The repo is located here: https://github.com/MicrosoftDocs/office-docs-powershell and you can find the README displayed at the bottom of the page.
+The repo is located here: <https://github.com/MicrosoftDocs/office-docs-powershell> and you can find the README displayed at the bottom of the page.

teams/docs-conceptual/index.md

@@ -1,14 +1,15 @@
 ---
 localization_priority: Normal
-title: Microsoft Teams cmdlet reference
+title: Microsoft Teams cmdlet help reference
+description: "Learn about the Microsoft Teams PowerShell cmdlet help reference."
 ---
 
-# Microsoft Teams cmdlet reference
+# Microsoft Teams cmdlet help reference
 
-Welcome to the Microsoft Teams PowerShell cmdlet help references. Cmdlets for managing Microsoft Teams service are split between two powershell modules: the Skype for Business Online module and the Microsoft Teams module.
+Welcome to the Microsoft Teams PowerShell cmdlet **Help** reference. Cmdlets for managing Microsoft Teams service are split between two powershell modules: the Skype for Business Online and the Microsoft Teams.
 
-This powershell module is used for provisioning and management of teams and their backing groups themselves.  The module can be installed here: https://www.powershellgallery.com/packages/MicrosoftTeams/ .  To manage the policies and configurations that apply to the Microsoft Teams service, please see the reference docs for the Skype for Business module: https://docs.microsoft.com/powershell/module/skype/?view=skype-ps 
+This PowerShell module is used for provisioning and management of teams and their backing groups themselves. The module can be installed here: <https://www.powershellgallery.com/packages/MicrosoftTeams/>. To manage the policies and configurations that apply to the Microsoft Teams service, please see the reference documents for the Skype for Business module: <https://docs.microsoft.com/powershell/module/skype>.
 
-Here you will find all of the Microsoft Teams PowerShell help topics. These topics are 'open source' and open for contributions. If you are interested in contributing to this content head over to the source GitHub repo and look through the README. 
+Here, you will find all of the Microsoft Teams PowerShell **Help** topics. These topics are 'open source' and open for contributions. If you are interested in contributing to this content, go to the source GitHub repo and look through the README.
 
-The repo is located here: https://github.com/microsoftdocs/office-docs-powershell and you can find the README displayed at the bottom of the page.
+The repo is located here: <https://github.com/microsoftdocs/office-docs-powershell> and you can find the README displayed at the bottom of the page.