Merge branch 'master' into CalendarProc-chrisda

Chris Davis · web-flow · commit b0a5ab8faeaf · 2020-11-05T14:33:15.000-08:00
diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSite.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSite.md
@@ -389,11 +389,13 @@ Accept wildcard characters: False
 
 ### -BlockDownloadLinksFileType
 
-The valid values are:  
+The valid values are:
 
 - WebPreviewableFiles
 - ServerRenderedFilesOnly
 
+**Note**: ServerRendered (Office Only) and WebPreviewable (All supported files).
+
 The site's value is compared with the tenant level setting and the stricter one wins. For example, if the tenant is set to ServerRenderedFilesOnly then that will be used even if the site is set to WebPreviewableFiles.
 
 ```yaml
diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenant.md b/sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenant.md
@@ -264,6 +264,8 @@ The valid values are:
 - WebPreviewableFiles
 - ServerRenderedFilesOnly
 
+**Note**: ServerRendered (Office Only) and WebPreviewable (All supported files). 
+
 ```yaml
 Type: BlockDownloadLinksFileTypes
 Parameter Sets: (All)
diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Start-SPOUnifiedGroupMove.md b/sharepoint/sharepoint-ps/sharepoint-online/Start-SPOUnifiedGroupMove.md
@@ -24,7 +24,7 @@ Start-SPOUnifiedGroupMove [-GroupAlias] <String> [-DestinationDataLocation] <Str
 
 ## DESCRIPTION
 
-Initiates the move of an Office 365 Group to a new geo location. The administrator may set a preferred start and end time for the move, however the preferred end time is not guaranteed. The customer tenant must be multi-geo enabled.
+Initiates the move of an Office 365 Group site to a new geo location. The administrator may set a preferred start and end time for the move, however the preferred end time is not guaranteed. The customer tenant must be Multi-Geo enabled to use these commandlets. 
 
 ## EXAMPLES
 
@@ -34,13 +34,13 @@ Initiates the move of an Office 365 Group to a new geo location. The administrat
 Start-SPOUnifiedGroupMove -GroupAlias EUTeam -DestinationDataLocation EUR
 ```
 
-Starts the move of Office 365 Group EUTeam to the Preferred Data Location EUR (Europe).
+Starts the move of an Office 365 Group site with an alias EUTeam to the Preferred Data Location EUR (Europe).
 
 ## PARAMETERS
 
 ### -DestinationDataLocation
 
-The destination location for the Office 365 Group move.
+The destination location for the Office 365 Group site move.
 
 ```yaml
 Type: String
@@ -56,7 +56,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-Force the cmdlet to run.
+Force the cmdlet to run. This ignores all warning blocks and validations. It is only recommended if the administrator only wishes to preserve data and is not interested in checks for applications, Business Connectivity Services, or other functionalities. 
 
 ```yaml
 Type: SwitchParameter
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -GroupAlias
 
-The alias of the Office 365 Group.
+The alias of the Office 365 Group attached to the site you want to move.
 
 ```yaml
 Type: String
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -SuppressBcsCheck
 
-Suppress checking of Business Connectivity Services used with the associated Office 365 Group Team site.
+Suppress checking for Business Connectivity Services used with the associated Office 365 Group site.
 
 ```yaml
 Type: SwitchParameter
@@ -168,7 +168,7 @@ Accept wildcard characters: False
 
 ### -SuppressMarketplaceAppCheck
 
-Suppress checking compatibility of marketplace SharePoint Add-ins deployed to the associated Office 365 Group Team site.
+Suppress checking compatibility of marketplace SharePoint Add-ins deployed to the associated Office 365 Group site.
 
 ```yaml
 Type: SwitchParameter
@@ -184,7 +184,7 @@ Accept wildcard characters: False
 
 ### -SuppressWorkflow2013Check
 
-Suppress checking compatibility of SharePoint 2013 Workflows deployed to the associated Office 365 Group Team site.
+Suppress checking compatibility of SharePoint 2013 Workflows deployed to the associated Office 365 Group site.
 
 ```yaml
 Type: SwitchParameter
diff --git a/sharepoint/sharepoint-ps/sharepoint-online/Start-SPOUserAndContentMove.md b/sharepoint/sharepoint-ps/sharepoint-online/Start-SPOUserAndContentMove.md
@@ -26,39 +26,39 @@ Start-SPOUserAndContentMove [-UserPrincipalName] <String> [-DestinationDataLocat
 
 ## DESCRIPTION
 
-In a multi-geo company, this cmdlet requires a multi-geo tenant to work, and enables the ability to move a user closer to their sites
+This cmdlet applies to Multi-Geo tenants and it is designed to move user profiles and their corresponding OneDrive personal sites across geo locations. These cmdlets may only be ran by a SharePoint or Global administrator, who is connected to the SharePoint administration center of the geo location where the user is currently hosted. 
 
 ## EXAMPLES
 
 ### EXAMPLE 1
 
 ```powershell
-Start-SPOUserAndContentMove -UserPrincipalName username@contoso.com -DestinationDataLocation EUR
+Start-SPOUserAndContentMove -UserPrincipalName username@contoso.onmicrosoft.com -DestinationDataLocation EUR
 ```
 
-This example moves the user username@contoso.com from the current location, to the European location (EUR).
+This example moves the user username@contoso.onmicrosoft.com from their current location, to the European location (EUR).
 
 ### EXAMPLE 2
 
 ```powershell
-Start-SPOUserAndContentMove -UserPrincipalName username@contoso.com -DestinationDataLocation JPN
+Start-SPOUserAndContentMove -UserPrincipalName username@contoso.onmicrosoft.com -DestinationDataLocation JPN
 ```
 
-This example moves the user username@contoso.com from the current location, to the Japanese location (JPN).
+This example moves the user username@contoso.onmicrosoft.com from their current location, to the Japanese location (JPN).
 
 ### EXAMPLE 3
 
 ```powershell
-Start-SPOUserAndContentMove -UserPrincipalName username@contoso.com -DestinationDataLocation EUR -PreferredMoveBeginDate ((Get-Date).AddHours(1)) -PreferredMoveEndDate ((Get-Date).AddHour(12))
+Start-SPOUserAndContentMove -UserPrincipalName username@contoso.onmicrosoft.com -DestinationDataLocation EUR -PreferredMoveBeginDate ((Get-Date).AddHours(1)) -PreferredMoveEndDate ((Get-Date).AddHour(12))
 ```
 
-This example moves the user username@contoso.com from the current location, to the European location (EUR), preferred to start 1 hour ahead from now, until 12 hours to that relative time.
+This example moves the user username@contoso.onmicrosoft.com from their current location, to the European location (EUR), with a preferred start move date. Doing so is recommended for administrators who wish to plan their user moves outside business hours and on weekends. 
 
 ## PARAMETERS
 
 ### -DestinationDataLocation
 
-Defines the new destination of the user that you want to move.
+Defines the destination location where you want to move the user. Note that you may only move a user to their preferred data location. Thus before moving a user, you must change their preferred data location. 
 
 ```yaml
 Type: String
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -Notify
 
-Makes a SPO notification that the user is being move
+Provides an SPO notification that the user is being moved.
 
 ```yaml
 Type: String
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -OverwriteOdb
 
-Switch parameter to Overwrite the information into the DB
+This parameter can be used to overrite a OneDrive in the destination location, if there is one present. This is only recommended in cases where an administrator wants to replace a OneDrive that already exists in the destination location, with the moved OneDrive. 
 
 ```yaml
 Type: SwitchParameter
@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 ### -PreferredMoveBeginDate
 
-Specifies what is the preferred Date and time to start the job
+Specifies what is the preferred date and time to begin the move. 
 
 ```yaml
 Type: DateTime
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -PreferredMoveEndDate
 
-Specifies what is the preferred Date and time to stop the job
+Specifies what is the preferred date and time to stop stop the move. Recommened when administrators are scripting large scale moves that they wish to complete within a timeframe. 
 
 ```yaml
 Type: DateTime
@@ -141,23 +141,6 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -Reserved
-
-This parameter will only check for reserved users to be moved near to their sites
-
-```yaml
-Type: String
-Parameter Sets: (All)
-Aliases:
-Applicable: SharePoint Online
-
-Required: False
-Position: 7
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
 ### -UserPrincipalName
 
 UserPrincipalName or UPN defined for the specific user on the SPO tenant
@@ -177,7 +160,7 @@ Accept wildcard characters: False
 
 ### -ValidationOnly
 
-Use this parameter to validate if the user is able to be moved.
+Use this parameter to validate if the user is able to be moved. This parameter is recommended for any user move. 
 
 ```yaml
 Type: SwitchParameter
diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWikiPageContent.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWikiPageContent.md
@@ -71,6 +71,10 @@ Accept pipeline input: False
 
 ### System.String
 
+### Notes
+
+Get-PnPWikiPageContent Cmdlet works with Modern Wiki Pages. It does not work with Wiki Pages created with classic site template like Enterprise Wiki Site Template.
+
 ## RELATED LINKS
 
-[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp)
+[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp)
diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTenantSite.md b/sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPTenantSite.md
@@ -229,4 +229,10 @@ Accept pipeline input: False
 
 ## RELATED LINKS
 
-[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp)[Locale IDs](https://github.com/pnp/PnP-PowerShell/wiki/Supported-LCIDs-by-SharePoint)[Resource Usage Limits on Sandboxed Solutions in SharePoint 2010](https://docs.microsoft.com/previous-versions/office/developer/sharepoint-2010/gg615462(v=office.14))[Creating on-premises site collections using CSOM](http://blogs.msdn.com/b/vesku/archive/2014/06/09/provisioning-site-collections-using-sp-app-model-in-on-premises-with-just-csom.aspx)
+[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp)
+
+[Locale IDs](https://github.com/pnp/PnP-PowerShell/wiki/Supported-LCIDs-by-SharePoint)
+
+[Resource Usage Limits on Sandboxed Solutions in SharePoint 2010](https://docs.microsoft.com/previous-versions/office/developer/sharepoint-2010/gg615462(v=office.14))
+
+[Provisioning site collections using SP App model in on-premises with just CSOM](https://docs.microsoft.com/archive/blogs/vesku/provisioning-site-collections-using-sp-app-model-in-on-premises-with-just-csom)
diff --git a/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPList.md b/sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPList.md
@@ -39,7 +39,7 @@ Removes the list named 'Announcements' without asking for confirmation.
 
 ### ------------------EXAMPLE 3------------------
 ```powershell
-Remove-PnPList -Title Announcements -Recycle
+Remove-PnPList -Identity Announcements -Recycle
 ```
 
 Removes the list named 'Announcements' and saves to the Recycle Bin
@@ -108,4 +108,4 @@ Accept pipeline input: False
 
 ## RELATED LINKS
 
-[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp)
+[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp)
diff --git a/skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md b/skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
@@ -295,7 +295,7 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 ### -MusicOnHoldEnabledType
-Settings this parameter allows you to turn on or turn off music on hold when a PSTN caller is placed on hold. It is turned on by default. Valid options are: Enabled, Disabled, UserOverride. For now setting the value to UserOverride is the same as Enabled. This setting does not apply to call park and SLA boss delegate features. 
+Setting this parameter allows you to turn on or turn off the music on hold when a PSTN caller is placed on hold. It is turned on by default. Valid options are Enabled, Disabled, and UserOverride. For now, setting the value to UserOverride is the same as Enabled. This setting does not apply to call park and SLA boss delegate features.
 
 ```yaml
 Type: Enum
@@ -310,6 +310,8 @@ Accept wildcard characters: False
 ```
 
 ### -SafeTransferEnabled
+Teams users will be able to transfer a call safely, between Teams and Skype For Business. If the target user does not answer the call, it will ring back to the transferrer. The person transferring the call must be a Teams user. The person the call is being transferred to must be either a Teams or Skype for Business user in the same tenant or in a federated tenant.
+
 Possible values
 - Enabled
 - Disabled
diff --git a/teams/teams-ps/teams/New-CsGroupPolicyAssignment.md b/teams/teams-ps/teams/New-CsGroupPolicyAssignment.md
@@ -32,7 +32,7 @@ Group policy assignment allows you to easily manage policies across different su
 Group policy assignments are only propagated to users that are direct members of the group; the assignments are not propagated to members of nested groups.
 
 Group policy assignment is currently limited to the following policy types:
-CallingLineIdentity (Caller ID policies), OnlineVoiceRoutingPolicy (Voice Routing policies), TeamsAppSetupPolicy (App Setup policies), TeamsCallingPolicy (Calling policies), TeamsCallParkPolicy (Call park policies), TeamsChannelsPolicy, TeamsComplianceRecordingPolicy, TenantDialPlan, TeamsEducationAssignmentsAppPolicy, TeamsMeetingBroadcastPolicy (Live Events policies), TeamsMeetingPolicy (Meeting policies), TeamsMessagingPolicy (Messaging policies), TeamsUpdateManagementPolicy.
+CallingLineIdentity (Caller ID policies), OnlineVoiceRoutingPolicy (Voice Routing policies), TeamsAppSetupPolicy (App Setup policies), TeamsCallingPolicy (Calling policies), TeamsCallParkPolicy (Call park policies), TeamsChannelsPolicy, TeamsComplianceRecordingPolicy, TenantDialPlan, TeamsEducationAssignmentsAppPolicy, TeamsMeetingBroadcastPolicy (Live Events policies), TeamsMeetingPolicy (Meeting policies), TeamsMessagingPolicy (Messaging policies), TeamsShiftsPolicy, TeamsUpdateManagementPolicy.
 
 ## EXAMPLES
 
