Merge branch 'master' into live

Author: VesaJuvonen

.openpublishing.publish.config.json

@@ -88,9 +88,9 @@
       ]
     },
     {
-      "docset_name": "teams-ps",
-      "build_source_folder": "teams",
-      "build_output_subfolder": "teams-ps",
+      "docset_name": "staffhub-ps",
+      "build_source_folder": "staffhub",
+      "build_output_subfolder": "staffhub-ps",
       "locale": "en-us",
       "monikers": [],
       "moniker_ranges": [],
@@ -117,9 +117,9 @@
       ]
     },
     {
-      "docset_name": "staffhub-ps",
-      "build_source_folder": "staffhub",
-      "build_output_subfolder": "staffhub-ps",
+      "docset_name": "teams-ps",
+      "build_source_folder": "teams",
+      "build_output_subfolder": "teams-ps",
       "locale": "en-us",
       "monikers": [],
       "moniker_ranges": [],
@@ -173,11 +173,11 @@
     ]
   },
   "need_generate_pdf_url_template": true,
-  "Targets": {  
-    "Pdf": {  
-    "template_folder": "_themes.pdf"  
-    }  
-   },
+  "Targets": {
+    "Pdf": {
+      "template_folder": "_themes.pdf"
+    }
+  },
   "need_generate_pdf": false,
   "need_generate_intellisense": false,
   "dependent_packages": [

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

@@ -14,7 +14,8 @@ Sets properties on the SharePoint Online organization.
 ## SYNTAX
 
 ```
-Set-SPOTenant [-BccExternalSharingInvitations <Boolean>] [-BccExternalSharingInvitationsList <String>]
+Set-SPOTenant [-ApplyAppEnforcedRestrictionsToAdHocRecipients <Boolean>] 
+ [-BccExternalSharingInvitations <Boolean>] [-BccExternalSharingInvitationsList <String>] 
  [-DisplayStartASiteOption <Boolean>] [-ExternalServicesEnabled <Boolean>] [-MaxCompatibilityLevel <Int32>]
  [-MinCompatibilityLevel <Int32>] [-NoAccessRedirectUrl <String>] [-OfficeClientADALDisabled <Boolean>]
  [-ProvisionSharedWithEveryoneFolder <Boolean>] [-RequireAcceptingAccountMatchInvitedAccount <Boolean>]
@@ -81,6 +82,27 @@ This example enables the use of special persisted cookie for Open with Explorer.
 
 ## PARAMETERS
 
+### -ApplyAppEnforcedRestrictionsToAdHocRecipients
+When the feature is enabled, all guest users are subject to conditional access policy. By default guest users who are accessing SharePoint Online files with pass code are exempt from the conditional access policy.
+
+The valid values are:  
+False (default) - Guest access users are exempt from conditional access policy.  
+True - Conditional access policy is applieda also to guest users.
+
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases: 
+Applicable: SharePoint Online
+
+Required: False
+Position: Named
+Default value: False
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -BccExternalSharingInvitations
 When the feature is enabled, all external sharing invitations that are sent will blind copy the e-mail messages listed in the BccExternalSharingsInvitationList.
 

sharepoint/sharepoint-ps/sharepoint-server/Start-SPAssignment.md

@@ -28,7 +28,9 @@ You can also ensure that the objects remain as long as you need them, even throu
 There are three levels of assignment:
 
 -- No assignment -- The object is not assigned to a variable and is disposed of after each iteration of the command.
+
 -- Simple assignment -- All objects are assigned to the global assignment store. This is done by using the Global parameter. When using this level, all objects are assigned to a global store and are disposed of when the Stop-SPAssignment cmdlet is called.
+
 -- Advanced assignment -- Objects are assigned to named stores for disposal. You can dispose of objects by using the Identity parameter with the `Stop-SPAssignment` cmdlet.
 
 Regardless of the assignment level used, all objects are disposed of when the Windows PowerShell run space is closed.
@@ -39,13 +41,10 @@ For permissions and the most current information about Windows PowerShell for Sh
 
 ### ------------------EXAMPLE 1-----------------------
 ```
-C:\PS>Start-SPAssignment -global
-
-C:\PS>$w = Get-SPWeb http://MyWeb
-
-C:\PS>$w | Set-SPWeb -title "Accounting"
-
-C:\PS>Stop-SPAssignment -global
+PS C:\>Start-SPAssignment -global
+PS C:\>$w = Get-SPWeb http://MyWeb
+PS C:\>$w | Set-SPWeb -title "Accounting"
+PS C:\>Stop-SPAssignment -global
 ```
 
 This example uses simple assignment.
@@ -55,13 +54,10 @@ Ensure that you run `Stop-SPAssignment` before you attempt any iterations of mul
 
 ### ------------------EXAMPLE 2-----------------------
 ```
-C:\PS>$gc = Start-SPAssignment
-
-C:\PS>$web = $gc | Get-SPWeb http://MyWeb
-
-C:\PS>$web | Set-SPWeb -title "Accounting"
-
-C:\PS>Stop-SPAssignment -Identity $gc
+PS C:\>$gc = Start-SPAssignment
+PS C:\>$web = $gc | Get-SPWeb http://MyWeb
+PS C:\>$web | Set-SPWeb -title "Accounting"
+PS C:\>Stop-SPAssignment -Identity $gc
 ```
 
 This example sets the title of the SPWeb object in multiple lines and controls the rate of disposal.

sharepoint/sharepoint-ps/sharepoint-server/Start-SPDiagnosticsSession.md

@@ -29,9 +29,8 @@ For permissions and the most current information about Windows PowerShell for Sh
 
 ### -------------EXAMPLE-------
 ```
-C:\PS>$correlationId = [guid]::NewGuid()
-
-C:\PS>Start-SPDiagnosticsSession -CorrelationId $correlationId -Dashboard:$true -TraceLevel Verbose
+PS C:\>$correlationId = [guid]::NewGuid()
+PS C:\>Start-SPDiagnosticsSession -CorrelationId $correlationId -Dashboard:$true -TraceLevel Verbose
 ```
 
 This example starts a diagnostic session for a specified correlation ID with the trace level of verbose.

sharepoint/sharepoint-ps/sharepoint-server/Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance.md

@@ -28,8 +28,8 @@ For permissions and the most current information about Windows PowerShell for Sh
 
 ### ------------------EXAMPLE------------------
 ```
-C:\PS>$qssInstance = Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance -Local
-Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance -Identity $qssInstance
+PS C:\>$qssInstance = Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance -Local
+PS C:\>Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance -Identity $qssInstance
 ```
 
 This example starts the local query and site settings instance.

sharepoint/sharepoint-ps/sharepoint-server/Start-SPService.md

@@ -8,7 +8,7 @@ schema: 2.0.0
 # Start-SPService
 
 ## SYNOPSIS
-{{Fill in the Synopsis}}
+Enables a service in the farm.
 
 
 ## SYNTAX
@@ -19,23 +19,27 @@ Start-SPService [-Identity] <SPServicePipeBind> [-AssignmentCollection <SPAssign
 ```
 
 ## DESCRIPTION
-{{Fill in the Description}}
+The Start-SPService cmdlet enables a service in the farm. Service instances for this service will be started on the appropriate servers in the farm.
+
+This cmdlet only controls service instances on servers that are managed by MinRole. The behavior for the Custom server role has changed with the November 2016 Public Update (PU). Please see the IncludeCustomServerRole parameter for additional information.
 
 
 ## EXAMPLES
 
 ### ---------------EXAMPLE--------------
 ```
-PS C:\> {{ Add example code here }}
+PS C:\>Start-SPService -Identity "Microsoft SharePoint Foundation Sandboxed Code Service"
 ```
 
-{{ Add example description here }}
+This example enables the Microsoft SharePoint Foundation Sandboxed Code Service in the farm.
 
 
 ## PARAMETERS
 
 ### -AssignmentCollection
-{{Fill AssignmentCollection Description}}
+Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used.
+
+When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur.
 
 ```yaml
 Type: SPAssignmentCollection
@@ -67,7 +71,7 @@ Accept wildcard characters: False
 ```
 
 ### -Identity
-{{Fill Identity Description}}
+Specifies the name of the service to enable.
 
 ```yaml
 Type: SPServicePipeBind
@@ -83,7 +87,9 @@ Accept wildcard characters: False
 ```
 
 ### -IncludeCustomServerRole
-{{Fill IncludeCustomServerRole Description}}
+Creates a timer job that also starts service instances on servers that are assigned to the custom server role.
+
+This is a one-time Timer job. MinRole will make no further attempts to manage the service instances on servers assigned to the Custom server role.
 
 ```yaml
 Type: SwitchParameter

sharepoint/sharepoint-ps/sharepoint-server/Stop-SPContentTypeReplication.md

@@ -8,7 +8,7 @@ schema: 2.0.0
 # Stop-SPContentTypeReplication
 
 ## SYNOPSIS
-{{Fill in the Synopsis}}
+Stops Content Type replication job to SharePoint Online.
 
 ## SYNTAX
 
@@ -17,22 +17,22 @@ Stop-SPContentTypeReplication [-AssignmentCollection <SPAssignmentCollection>] [
 ```
 
 ## DESCRIPTION
-{{Fill in the Description}}
+Stops Content Type replication job to SharePoint Online and deletes the replication timer job.
 
 ## EXAMPLES
 
 ### -----------------EXAMPLE----------------
 ```
-PS C:\> {{ Add example code here }}
+PS C:\>Stop-SPContentTypeReplication
 ```
-
-{{ Add example description here }}
-
+Stops Content Type replication job to SharePoint Online.
 
 ## PARAMETERS
 
 ### -AssignmentCollection
-{{Fill AssignmentCollection Description}}
+Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used.
+
+When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur.
 
 ```yaml
 Type: SPAssignmentCollection

sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPSolution.md

@@ -43,7 +43,7 @@ For permissions and the most current information about Windows PowerShell for Sh
 
 ### ------------------EXAMPLE------------------
 ```
-C:\PS>Uninstall-SPUserSolution -Identity contoso_solution.wsp
+PS C:\>Uninstall-SPUserSolution -Identity contoso_solution.wsp
 ```
 
 This example retracts the deployed SharePoint solution contoso_solution.wsp.
@@ -142,14 +142,13 @@ Accept wildcard characters: False
 ```
 
 ### -CompatibilityLevel
-{{Fill CompatibilityLevel Description}}
-
+Specifies whether to uninstall the solution, from a specific version directory based on CompatibilityLevel. The default behavior if this parameter is not specified is to uninstall the solution only from the version directory based on the version tracked in the manifest of the solution's cab file.
 
 ```yaml
 Type: String
 Parameter Sets: (All)
 Aliases: 
-Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016
+Applicable: SharePoint Server 2013, SharePoint Server 2016
 
 Required: False
 Position: Named

sharepoint/sharepoint-ps/sharepoint-server/Update-SPHelp.md

@@ -1,14 +1,14 @@
 ---
 external help file: 
-applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016
+applicable: SharePoint Server 2013, SharePoint Server 2016
 title: Update-SPHelp
 schema: 2.0.0
 ---
 
 # Update-SPHelp
 
 ## SYNOPSIS
-{{Fill in the Synopsis}}
+Updates SharePoint cmdlet help.
 
 
 ## SYNTAX
@@ -18,17 +18,20 @@ Update-SPHelp [-AssignmentCollection <SPAssignmentCollection>] [-Force] [<Common
 ```
 
 ## DESCRIPTION
-{{Fill in the Description}}
+The Update-SPHelp cmdlet checks the Windows Download Center for updates for the SharePoint Management Shell help files against the version of the help files on the local computer. If there updates available, the cmdlet will download and install these updates. By default, the cmdlet will allow checking for updates only once every 24 hours. To override this check, use the Force parameter.
+
+The computer that the cmdlet is being run on must have an internet connection.
+
+Note: This cmdlet currently does not update cmdlet help.
 
 
 ## EXAMPLES
 
 ### --------------------EXAMPLE 1---------------------
 ```
-PS C:\> {{ Add example code here }}
+PS C:\>Update-SPHelp
 ```
-
-{{ Add example description here }}
+Updates SharePoint cmdlet help.
 
 ### --------------------EXAMPLE 2---------------------
 ```
@@ -47,13 +50,15 @@ This example checks for updates to the help files and provides detailed feedback
 ## PARAMETERS
 
 ### -AssignmentCollection
-{{Fill AssignmentCollection Description}}
+Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used.
+
+NOTE: When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur.
 
 ```yaml
 Type: SPAssignmentCollection
 Parameter Sets: (All)
 Aliases: 
-Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016
+Applicable: SharePoint Server 2013, SharePoint Server 2016
 
 Required: False
 Position: Named
@@ -63,13 +68,13 @@ Accept wildcard characters: False
 ```
 
 ### -Force
-{{Fill Force Description}}
+Over-rides the throttling logic and checks for updates to the help files even if a check was made in the last 24 hours.
 
 ```yaml
 Type: SwitchParameter
 Parameter Sets: (All)
 Aliases: 
-Applicable: SharePoint Server 2010, SharePoint Server 2013, SharePoint Server 2016
+Applicable: SharePoint Server 2013, SharePoint Server 2016
 
 Required: False
 Position: Named