Merge branch 'master' into patch-1

chrisda · web-flow · commit 7d00333c3b67 · 2020-10-06T09:09:51.000-07:00
diff --git a/exchange/docs-conceptual/app-only-auth-powershell-v2.md b/exchange/docs-conceptual/app-only-auth-powershell-v2.md
@@ -105,7 +105,7 @@ If you encounter problems, check the [required permssions](https://docs.microsof
 
    - **Name**: Enter something descriptive.
 
-   - **Supported account types**: Select **Accounts in this organizational directory only (Microsoft)**.
+   - **Supported account types**: Select **Accounts in this organizational directory only (\<YourOrganizationName\> only - Single tenant)**.
 
    - **Redirect URI (optional)**: In the first box, select **Web**. In the second box, enter the URI where the access token is sent.
 
@@ -133,11 +133,11 @@ You need to assign the API permission `Exchange.ManageAsApp` so the application
 
 5. In the **Select permissions** section that appears on the page, expand **Exchange** and select **Exchange.ManageAsApp**
 
-   ![Select Exchange API permssions](media/app-only-auth-exchange-manageasapp.png)
+   ![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.
+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.
 
diff --git a/exchange/docs-conceptual/connect-to-exchange-servers-using-remote-powershell.md b/exchange/docs-conceptual/connect-to-exchange-servers-using-remote-powershell.md
@@ -6,7 +6,7 @@ manager: dansimp
 ms.date:
 ms.audience: ITPro
 ms.topic: article
-ms.prod: exchange-server-it-pro
+ms.service: exchange-powershell
 localization_priority: Priority
 ms.collection: Strat_EX_Admin
 ms.custom:
diff --git a/exchange/docs-conceptual/connect-to-scc-powershell.md b/exchange/docs-conceptual/connect-to-scc-powershell.md
@@ -49,7 +49,7 @@ If your account uses multi-factor authentication, use the steps in this section.
 
    - _\<UPN\>_ is your account in user principal name format (for example, `navin@contoso.com`).
    - The required _ConnectionUri_ value depends on the nature of your Microsoft 365 organization. For more information, see the parameter description in [Connect-IPPSSession](https://docs.microsoft.com/powershell/module/exchange/connect-ippssession).
-   - When you use the _UserPrincipalName_ parameter, you don't need to use the 
+   - When you use the _UserPrincipalName_ parameter, you don't need to use the _AzureADAuthorizationEndpointUri_ parameter in environments that would otherwise require it.
 
    **This example connects to Security & Compliance Center PowerShell in a Microsoft 365 or Microsoft 365 GCC organization**.
 
diff --git a/exchange/docs-conceptual/control-remote-powershell-access-to-exchange-servers.md b/exchange/docs-conceptual/control-remote-powershell-access-to-exchange-servers.md
@@ -6,7 +6,7 @@ manager: dansimp
 ms.date:
 ms.audience: ITPro
 ms.topic: article
-ms.prod: exchange-server-it-pro
+ms.service: exchange-powershell
 localization_priority: Normal
 ms.assetid: 064e3bb0-38bf-495e-9994-784f823b88dd
 description: "Administrators can learn how to block or allow users' remote PowerShell access to Exchange servers."
diff --git a/exchange/docs-conceptual/exchange-management-shell.md b/exchange/docs-conceptual/exchange-management-shell.md
@@ -6,7 +6,7 @@ manager: dansimp
 ms.date:
 ms.audience: ITPro
 ms.topic: article
-ms.prod: exchange-server-it-pro
+ms.service: exchange-powershell
 localization_priority: Normal
 ms.assetid: 925ad66f-2f05-4269-9923-c353d9c19312
 description: "Learn about Exchange Server PowerShell, also known as the Exchange Management Shell. This topic describes how PowerShell works on Exchange servers, and provides links to other topics that can help you learn how to use the Exchange Management Shell."
@@ -42,8 +42,8 @@ A benefit of remote PowerShell is that you can use Windows PowerShell on a local
 
 For details, see the following topics:
 
-- [Exchange 2019 system requirements](https://docs.microsoft.com/Exchange/plan-and-deploy/system-requirements?view=exchserver-2019)
-- [Exchange 2016 system requirements](https://docs.microsoft.com/Exchange/plan-and-deploy/system-requirements?view=exchserver-2016)
+- [Exchange 2019 system requirements](https://docs.microsoft.com/Exchange/plan-and-deploy/system-requirements?view=exchserver-2019&preserve-view=true)
+- [Exchange 2016 system requirements](https://docs.microsoft.com/Exchange/plan-and-deploy/system-requirements?view=exchserver-2016&preserve-view=true)
 - [Exchange 2013 system requirements](https://docs.microsoft.com/exchange/exchange-2013-system-requirements-exchange-2013-help)
 - [Exchange 2010 system requirements](https://docs.microsoft.com/previous-versions/office/exchange-server-2010/aa996719(v=exchg.141))
 
diff --git a/exchange/docs-conceptual/open-the-exchange-management-shell.md b/exchange/docs-conceptual/open-the-exchange-management-shell.md
@@ -6,7 +6,7 @@ manager: dansimp
 ms.date:
 ms.audience: ITPro
 ms.topic: article
-ms.prod: exchange-server-it-pro
+ms.service: exchange-powershell
 localization_priority: Normal
 ms.assetid: 63976059-25f8-4b4f-b597-633e78b803c0
 description: "Find and open the shortcut for Exchange PowerShell (also known as the Exchange Management Shell) on Exchange servers or computers that have the Exchange management tools installed."
diff --git a/exchange/docs-conceptual/use-update-exchangehelp.md b/exchange/docs-conceptual/use-update-exchangehelp.md
@@ -6,7 +6,7 @@ manager: dansimp
 ms.date:
 ms.audience: ITPro
 ms.topic: article
-ms.prod: exchange-server-it-pro
+ms.service: exchange-powershell
 localization_priority: Normal
 ms.assetid: 219f78a3-f0e5-4dc6-9787-9a0b9756ee09
 description: "Administrators can learn how to use Update-ExchangeHelp to update Exchange cmdlet reference topics that are available in Exchange Management Shell in Exchange 2016"
diff --git a/exchange/exchange-ps/exchange/Get-EventsFromEmailConfiguration.md b/exchange/exchange-ps/exchange/Get-EventsFromEmailConfiguration.md
@@ -25,6 +25,8 @@ Get-EventsFromEmailConfiguration [-Identity] <RecipientIdParameter> [<CommonPara
 ```
 
 ## DESCRIPTION
+**Note**: The following output properties have been deprecated: EventReservationProcessingLevel, FoodEstablishmentReservationProcessingLevel, InvoiceProcessingLevel, and ServiceReservationProcessingLevel.
+
 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
diff --git a/exchange/exchange-ps/exchange/Set-EventsFromEmailConfiguration.md b/exchange/exchange-ps/exchange/Set-EventsFromEmailConfiguration.md
@@ -107,13 +107,7 @@ Accept wildcard characters: False
 ```
 
 ### -EventReservationProcessingLevel
-The EventReservationProcessingLevel parameter specifies whether event reservations are automatically discovered from messages, and whether these reservations are automatically added to the user's calendar. Valid values are:
-
-- Disabled: Do not discover event reservations from messages.
-
-- Email: Discover event reservations from messages, but don't automatically add them to the user's calendar.
-
-- Calendar: Discover event reservations from messages and automatically add them to the user's calendar. This is the default value.
+This parameter has been deprecated and is no longer used.
 
 ```yaml
 Type: String
@@ -151,13 +145,7 @@ Accept wildcard characters: False
 ```
 
 ### -FoodEstablishmentReservationProcessingLevel
-The FoodEstablishmentProcessingLevel parameter specifies whether dining reservations are automatically discovered from messages, and whether these reservations are automatically added to the user's calendar. Valid values are:
-
-- Disabled: Do not discover restaurant reservations from messages.
-
-- Email: Discover restaurant reservations from messages however do not automatically add these to the user's calendar.
-
-- Calendar: Discover restaurant reservations from messages and automatically add them to the user's calendar. This is the default value.
+This parameter has been deprecated and is no longer used.
 
 ```yaml
 Type: String
@@ -173,13 +161,7 @@ Accept wildcard characters: False
 ```
 
 ### -InvoiceProcessingLevel
-The InvoiceProcessingLevel parameter specifies whether invoices are automatically discovered from messages, and whether these reservations are automatically added to the user's calendar. Valid values are:
-
-- Disabled: Do not discover invoices from messages.
-
-- Email: Discover invoices from messages however do not automatically add these to the user's calendar.
-
-- Calendar: Discover invoices from messages and automatically add them to the user's calendar. This is the default value.
+This parameter has been deprecated and is no longer used.
 
 ```yaml
 Type: String
@@ -277,13 +259,7 @@ Accept wildcard characters: False
 ```
 
 ### -ServiceReservationProcessingLevel
-The ServiceReservationProcessingLevel parameter specifies whether service reservations are automatically discovered from messages, and whether these reservations are automatically added to the user's calendar. Valid values are:
-
-- Disabled: Do not discover service reservations from messages.
-
-- Email: Discover service reservations from messages, but don't automatically add them to the user's calendar.
-
-- Calendar: Discover service reservations from messages and automatically add them to the user's calendar. This is the default value.
+This parameter has been deprecated and is no longer used.
 
 ```yaml
 Type: String
diff --git a/exchange/exchange-ps/exchange/Set-OrganizationConfig.md b/exchange/exchange-ps/exchange/Set-OrganizationConfig.md
@@ -58,7 +58,6 @@ Set-OrganizationConfig
  [-DistributionGroupNamingPolicy <DistributionGroupNamingPolicy>]
  [-ElcProcessingDisabled <Boolean>]
  [-EndUserDLUpgradeFlowsDisabled <Boolean>]
- [-ExternalInOutlookEnabled <Boolean>]
  [-EwsAllowEntourage <Boolean>]
  [-EwsAllowList <MultiValuedProperty>]
  [-EwsAllowMacOutlook <Boolean>]
@@ -1462,17 +1461,6 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -ExternalInOutlookEnabled
-This parameter is available only in the cloud-based service.
-
-The ExternalInOutlookEnabled parameter specifies whether to add identifiers to messages from external senders in Outlook on the web (formerly known as Outlook Web App). Valid values are:
-
-- $true: External senders are identified as external in list view and the reading pane.
-
-- $false: External senders are not identified as external. This is the default value.
-
-Whether the sender's domain is considered internal or external is controlled by the Set-AcceptedDomain cmdlet.
-
 ```yaml
 Type: Boolean
 Parameter Sets: Default
diff --git a/exchange/exchange-ps/exchange/Set-UnifiedGroup.md b/exchange/exchange-ps/exchange/Set-UnifiedGroup.md
@@ -680,7 +680,7 @@ Accept wildcard characters: False
 ```
 
 ### -ExtensionCustomAttribute1
-This parameter specifies a value for the ExtensionCustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
+This parameter specifies a value for the ExtensionCustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
 To enter multiple values that overwrite any existing entries, use the following syntax: \<value1\>,\<value2\>,...\<valueN\>. If the values contain spaces or otherwise require quotation marks, you need to use the following syntax: "\<value1\>","\<value2\>",..."\<valueN\>".
 
diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOSiteDesign.md b/sharepoint/sharepoint-ps/sharepoint-online/Add-SPOSiteDesign.md
@@ -71,6 +71,7 @@ Accept wildcard characters: False
 ### -WebTemplate
 
 Identifies which base template to add the design to. Use the value **64** for the Team site template, and the value **68** for the Communication site template.
+For more information, visit [SharePoint site design and site script overview](https://docs.microsoft.com/sharepoint/dev/declarative-customization/site-design-overview).
 
 ```yaml
 Type: String
diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOAppErrors.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOAppErrors.md
@@ -48,6 +48,14 @@ Get-SPOAppErrors -ProductId ba51729b-e017-409d-681a-66f1dd18f0f4
 
 This example returns a collection of monitoring error message(s) for application whose GUID is ba51729b-e017-409d-681a-66f1dd18f0f4.
 
+### ------------ Example 2 --------------------
+
+```powershell
+Get-SPOAppErrors -ProductId ba51729b-e017-409d-681a-66f1dd18f0f4 -StartTimeInUtc (Get-Date).AddHours(-1).ToUniversalTime()
+```
+
+This example returns a collection of monitoring error message(s) for application whose GUID is ba51729b-e017-409d-681a-66f1dd18f0f4 in the last hour.
+
 ## PARAMETERS
 
 ### -EndTimeInUtc
@@ -86,7 +94,7 @@ Accept wildcard characters: False
 
 ### -StartTimeInUtc
 
-Specifies the start time in UTC to search for monitoring errors (for example, 01032011:12:00). If no start time is given, the default value 72 hours before the current time is used.
+Specifies the start time in UTC to search for monitoring errors. If no start time is given, the default value 72 hours before the current time is used.
 
 ```yaml
 Type: DateTime
diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOGeoAdministrator.md b/sharepoint/sharepoint-ps/sharepoint-online/Get-SPOGeoAdministrator.md
@@ -25,7 +25,7 @@ Get-SPOGeoAdministrator [<CommonParameters>]
 ## DESCRIPTION
 
 You may only use parameters from one parameter set and you may not combine parameters from different parameter sets.
-For more information about how to use parameter sets, see Cmdlet Parameter Sets [https://go.microsoft.com/fwlink/?LinkID=187810](https://go.microsoft.com/fwlink/?LinkID=187810).
+For more information about how to use parameter sets, see [Cmdlet parameter sets](https://docs.microsoft.com/powershell/scripting/developer/cmdlet/cmdlet-parameter-sets).
 
 The `Get-SPOGeoAdministrator` cmdlet has a single parameter set and matches a user or a list of users which has the ability to do changes globally in the geo location that you are connected to.
 
diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Invoke-SPOSiteSwap.md b/sharepoint/sharepoint-ps/sharepoint-online/Invoke-SPOSiteSwap.md
@@ -89,7 +89,7 @@ Archives the existing Search Center site at <https://contoso.sharepoint.com/sear
 
 URL of the source site. The site at this location must exist before performing the swap.
 
-If the target is the root site at <https://tenant-name.sharepoint.com> then the source site must be either a Team Site (STS#0), a Modern Team Site (STS#3), or a Communication Site (SITEPAGEPUBLISHING#0).
+If the target is the root site at <https://tenant-name.sharepoint.com> then the source site must be either a Modern Team Site (STS#3) or a Communication Site (SITEPAGEPUBLISHING#0).
 
 If the target is the search center site at <https://tenant-name.sharepoint.com/search> then the source site must be either a Search Center Site (SRCHCEN#0) or a Basic Search Center Site (SRCHCENTERLITE#0).
 
diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOHomeSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOHomeSite.md
@@ -34,7 +34,7 @@ Use this cmdlet to remove the current SharePoint Online Home Site setting.
 Remove-SPOHomeSite
 ```
 
-This example removes the current SharerPoint Online Home Site setting.
+This example removes the current SharePoint Online Home Site setting.
 
 ## PARAMETERS
 
diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Revoke-SPOHubSiteRights.md b/sharepoint/sharepoint-ps/sharepoint-online/Revoke-SPOHubSiteRights.md
@@ -61,7 +61,7 @@ Accept wildcard characters: False
 
 ### -Principals
 
-One or more principles to revoke the permissions for.
+One or more principals to revoke the permissions for.
 
 ```yaml
 Type: String[]
diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOBrowserIdleSignOut.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOBrowserIdleSignOut.md
@@ -14,7 +14,7 @@ ms.reviewer:
 
 ## SYNOPSIS
 
-.
+Sets the current configuration values for Idle session sign-out.
 
 ## SYNTAX
 
diff --git a/skype/skype-ps/skype/Grant-CsTeamsUpgradePolicy.md b/skype/skype-ps/skype/Grant-CsTeamsUpgradePolicy.md
@@ -41,6 +41,12 @@ Office 365 provides all relevant instances of TeamsUpgradePolicy via built-in, r
 |UpgradeToTeams|TeamsOnly|False|Use this mode to upgrade users to Teams and to prevent chat, calling, and meeting scheduling in Skype for Business.|
 |Global|Islands|False||
 
+
+>[!IMPORTANT]
+>TeamsUpgradePolicy can be assigned to any Teams user, whether that user hase an on-premises account in Skype for Business Server or not. However, **TeamsOnly mode can only be assigned to a user who is already homed in Skype for Business Online**. This is because interop with Skype for Business users and federation as well as Microsoft 365 Phone System functionality are only possible if the user is homed in Skype for Business Online. In addition, you cannot assign TeamsOnly mode as the tenant-wide default if you have any Skype for Business on-premises deployment (which is detected by presence of a lyncdiscover DNS record that points to a location other than Office 365. To make these users TeamsOnly you must first move these users individually to the cloud using `Move-CsUser`.  Once all users have been moved to the cloud, you can [disable hybrid to complete migration to the cloud](https://docs.microsoft.com/skypeforbusiness/hybrid/cloud-consolidation-disabling-hybrid) and then apply TeamsOnly mode at the tenant level to ensure future users are TeamsOnly by default.
+
+
+
 **NOTES:** 
 - TeamsUpgradePolicy is available in both Office 365 and in on-premises versions of Skype for Business Server, but there are differences: 
     - In Office 365, admins can specify both coexistence mode and whether to trigger notifications of pending upgrade.  
@@ -51,7 +57,7 @@ Office 365 provides all relevant instances of TeamsUpgradePolicy via built-in, r
 - In Office 365, all relevant instances of TeamsUpgradePolicy are built into the system, so there is no corresponding New cmdlet available. In contrast, Skype for Business Server does not contain built-in instances, so the New cmdlet is available on-premises.  Only NotifySfBUsers property is available in on-premises.
 - When granting a user a policy with mode=TeamsOnly or mode=SfBWithTeamsCollabAndMeetings, by default, meetings organized by that user will be migrated to Teams. For details, see [Using the Meeting Migration Service (MMS)](https://docs.microsoft.com/skypeforbusiness/audio-conferencing-in-office-365/setting-up-the-meeting-migration-service-mms).
 
-**IMPORTANT**
+
 When users are in any of the Skype for Business modes (SfBOnly, SfBWithTeamsCollab, SfBWithTeamsCollabAndMeetings), calling and chat functionality in the Teams app are disabled (but chat in the context of a Teams meeting is still allowed). Similarly, when users are in the SfBOnly or SfBWithTeamsCollab modes, meeting scheduling is disabled. For more details, see [Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://docs.microsoft.com/microsoftteams/migration-interop-guidance-for-teams-with-skype).
 
 The `Grant-CsTeamsUpgradePolicy` cmdlet checks the configuration of the corresponding settings in TeamsMessagingPolicy, TeamsCallingPolicy, and TeamsMeetingPolicy to determine if those settings would be superceded by TeamsUpgradePolicy and if so, an informational message is provided in PowerShell.  It is not necessary to set these other policy settings. This is for informational purposes only. Below is an example of what the PowerShell warning looks like:
diff --git a/skype/skype-ps/skype/Move-CsUser.md b/skype/skype-ps/skype/Move-CsUser.md
@@ -48,7 +48,7 @@ When moving a user to or from Office 365 (either Skype for Business Online or Te
 - Moving a user to Teams is achieved by specifying the MoveToTeams switch. This performs the same operations as a move to Skype for Business Online (without the specifying -MoveToTeams) and also performs the following actions:
 
     - TeamsUpgradePolicy with Mode=TeamsOnly is assigned to the online user account.
-    - Meeting migration is triggered to move meetings to Teams instead of Skype for Business Online. This functionality is currently available to TAP customers only. For customers not in TAP, meetings are always migrated to Skype for Business Online.
+    - Meeting migration is triggered to move meetings to Teams instead of Skype for Business Online.
 
 - Contacts are moved in all cases, unless -force is specified.
 
diff --git a/skype/skype-ps/skype/New-CsAutoAttendantCallableEntity.md b/skype/skype-ps/skype/New-CsAutoAttendantCallableEntity.md
@@ -46,10 +46,10 @@ This example creates a user callable entity.
 
 ### -------------------------- Example 2 --------------------------
 ```powershell
-$callableEntity = New-CsAutoAttendantCallableEntity -Identity "tel:+1234567890" -Type ApplicationEndpoint
+$callableEntity = New-CsAutoAttendantCallableEntity -Identity "tel:+1234567890" -Type ExternalPSTN
 ```
 
-This example creates an application endpoint callable entity.
+This example creates an ExternalPSTN callable entity.
 
 ### -------------------------- Example 3 --------------------------
 ```powershell
@@ -135,6 +135,8 @@ Accept wildcard characters: False
 ```
 
 ### -EnableTranscription
+Enables the email transcription of voicemail, this is only supported with shared voicemail callable entities.
+
 ```yaml
 Type: SwitchParameter
 Parameter Sets: (All)
diff --git a/skype/skype-ps/skype/Set-CsTeamsMessagingPolicy.md b/skype/skype-ps/skype/Set-CsTeamsMessagingPolicy.md
@@ -68,6 +68,7 @@ All other policy properties will be left as previously assigned.
 
 ### -AllowGiphy
 Determines whether a user is allowed to access and post Giphys. Set this to TRUE to allow. Set this FALSE to prohibit.
+Note: [Optional Connected Experiences](https://docs.microsoft.com/deployoffice/privacy/manage-privacy-controls#policy-setting-for-optional-connected-experiences) must be also enabled for Giphys to be allowed.
 
 ```yaml
 Type: Boolean
@@ -248,6 +249,7 @@ Accept wildcard characters: False
 
 ### -AllowUrlPreviews
 Use this setting to turn automatic URL previewing on or off in messages. Set this to TRUE to turn on. Set this to FALSE to turn off.
+Note: [Optional Connected Experiences](https://docs.microsoft.com/deployoffice/privacy/manage-privacy-controls#policy-setting-for-optional-connected-experiences) must be also enabled for URL previews to be allowed.
 
 ```yaml
 Type: Boolean
