Merge pull request MicrosoftDocs#2238 from MicrosoftDocs/master

Merges Master to Live. See commits for details.

Author: kenwith

exchange/exchange-ps/exchange/mailboxes/Remove-CalendarEvents.md

@@ -23,7 +23,7 @@ Remove-CalendarEvents [-Identity] <MailboxIdParameter> [-CancelOrganizedMeetings
 ```
 
 ## DESCRIPTION
-This cmdlet cancels meetings in the specified mailbox where the mailbox is the meeting organizer, and the meeting has one or more attendees or resources. It doesn't cancel appointments or meetings without attendees or resources.
+This cmdlet cancels meetings in the specified mailbox where the mailbox is the meeting organizer, and the meeting has one or more attendees or resources. It doesn't cancel appointments or meetings without attendees or resources. Because meeting cancellations must be sent out, the mailbox must still be enabled to send mail.
 
 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).
 

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

@@ -20,7 +20,7 @@ Remove-SPOSite [-Confirm] -Identity <SpoSitePipeBind> [-NoWait] [-WhatIf] [<Comm
 ## DESCRIPTION
 The `Remove-SPOSite` cmdlet does not delete a site collection from the site collections list permanently.
 Instead, the removed site collection is moved to the Recycle Bin.
-You can use the `Restore-SPODeletedSitecmdlet` to restore a site collection from the Recycle Bin.
+You can use the `Restore-SPODeletedSite`cmdlet to restore a site collection from the Recycle Bin.
 To delete a site collection permanently, first move the site collection to the Recycle Bin by using the `Remove-SPOSite` cmdlet and then delete it from the Recycle Bin by using the `Remove-SPODeletedSite` cmdlet.
 
 You must be a SharePoint Online global administrator and a site collection administrator to run the cmdlet.

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

@@ -17,6 +17,8 @@ Set-SPOHubSite [-Identity] <SpoHubSitePipeBind>
   [-Title <string>]
   [-LogoUrl <string>]
   [-Description <string>]
+  [-SiteDesignId <guid>]
+  [-RequiresJoinApproval <bool>]
   [<CommonParameters>]
 ```
 
@@ -107,3 +109,37 @@ Default value: None
 Accept pipeline input: False
 Accept wildcard characters: False
 ```
+
+### -SiteDesignId
+
+A description of the hub site.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases: 
+Applicable: SharePoint Online
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -RequiresJoinApproval
+
+A description of the hub site.
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases: 
+Applicable: SharePoint Online
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```

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

@@ -210,7 +210,7 @@ Accept wildcard characters: False
 ```
 
 ### -DisabledWebpartIds
-This parameter is used for eanbling disabled web parts that use third-party service (Amazon Kindle, YouTube, Twitter).  The GUIDs that can be used are 46698648-fcd5-41fc-9526-c7f7b2ace919 (Amazon Kindle), 544dd15b-cf3c-441b-96da-004d5a8cea1d (YouTube), f6fdf4f8-4a24-437b-a127-32e66a5dd9b4 (Twitter).
+This parameter is used for enabling disabled web parts that use third-party service (Amazon Kindle, YouTube, Twitter).  The GUIDs that can be used are 46698648-fcd5-41fc-9526-c7f7b2ace919 (Amazon Kindle), 544dd15b-cf3c-441b-96da-004d5a8cea1d (YouTube), f6fdf4f8-4a24-437b-a127-32e66a5dd9b4 (Twitter).
 
 The Set-SPOTenant cmdlet is used for disabling these web parts with third-party services. 
 

sharepoint/sharepoint-ps/sharepoint-server/New-SPSubscriptionSettingsServiceApplication.md

@@ -34,6 +34,7 @@ For permissions and the most current information about Windows PowerShell for Sh
 ```
 
 PS C:\>$sa = New-SPSubscriptionSettingsServiceApplication -ApplicationPool 'SharePoint Web Services Default' -Name 'Subscriptions Settings Service Application' -DatabaseName 'Subscription'
+PS C:\>New-SPSubscriptionSettingsServiceApplicationProxy -ServiceApplication $sa
 
 ```
 

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

@@ -28,14 +28,21 @@ For permissions and the most current information about Windows PowerShell for Sh
 
 ## EXAMPLES
 
-### ------------------EXAMPLE-----------------------
+### ------------------EXAMPLE 1-----------------------
 ```
-PS C:\>Set-SPUser -Identity 'Contoso\jdow' -Web http:// test -AddPermissionLevel "Contributor"
+PS C:\>Set-SPUser -Identity 'Contoso\jdoe' -Web https://intranet.contoso.com -AddPermissionLevel "Contributor"
 ```
 
-This example sets a user (Contoso\jdow) to be a contributor on http://test.
+This example sets a user (Contoso\jdoe) to be a contributor on https://intranet.contoso.com.
 
 
+### ------------------EXAMPLE 2-----------------------
+```
+PS C:\>Set-SPUser -Identity 'Contoso\jdoe' -Web https://intranet.contoso.com -SyncFromAD
+```
+
+This updates the User Information List for the user 'contoso\jdoe' with the current `displayName` and `mail` attribute values from the user's Active Directory account.
+
 ## PARAMETERS
 
 ### -Identity
@@ -250,7 +257,7 @@ Accept wildcard characters: False
 ```
 
 ### -SyncFromAD
-If provided, specifies that user information will be synchronized from the user directory store.
+If provided, specifies that user information will be synchronized from the user directory store. This switch only retrieves the `displayName` and `mail` value from the directory store. It supports Active Directory (Classic or Windows authentication), Forms-based Authentication, and SAML. FBA and SAML providers must support resolving from their directory store for this switch to work. The switch only supports SharePoint User objects.
 
 ```yaml
 Type: SwitchParameter

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

@@ -51,15 +51,27 @@ PS C:\>$proxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq 'User Profile
 PS C:\>Update-SPRepopulateMicroblogFeedCache -ProfileServiceApplicationProxy $proxy -AccountName contoso\userName
 ```
 
-This example refreshes the feeds for a specific user by using the AccountName parameter.
+This example refreshes the feed for a specific user by using the AccountName parameter.
 
 ### ------------EXAMPLE 2------------
 ```
+PS C:\>$site = (Get-SPWebApplication -IncludeCentralAdministration | ?{$_.IsAdministrationWebApplication -eq $true}).Sites[0]
+PS C:\>$context = Get-SPServiceContext $site
+PS C:\>$upm = New-Object Microsoft.Office.Server.UserProfiles.UserProfileManager($context)
+PS C:\>$profiles = $upm.GetEnumerator()
 PS C:\>$proxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq 'User Profile Service Application Proxy'}
-PS C:\>Update-SPRepopulateMicroblogFeedCache -ProfileServiceApplicationProxy $proxy -AccountName contoso\userName -SiteSubscription 0C37852B-34D0-418e-91C6-2AC25AF4BE5B
+PS C:\>while($profiles.MoveNext()) {
+    $profile = $profiles.Current
+	   Update-SPRepopulateMicroblogFeedCache -ProfileServiceApplicationProxy $proxy -AccountName $profile.AccountName }
 ```
 
-This example refreshes the feeds for a specific user by using the AccountName parameter.
+This example refreshes the feeds for all users in the User Profile Service Application.
+
+### ------------EXAMPLE 3------------
+```
+PS C:\>Update-SPRepopulateMicroblogFeedCache -ProfileServiceApplicationProxy $proxy -SiteUrl https://sharepoint.contoso.com
+```
+This example refreshes the feed on the site https://sharepoint.contoso.com.
 
 ## PARAMETERS
 

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md

@@ -28,7 +28,7 @@ Grant-CsTeamsCallingPolicy [-PolicyName] <String> [-Tenant <Guid>] [-DomainContr
 ```
 
 ## DESCRIPTION
-The Teams Calling Policies designate which users are able to use calling functionality within teams and determine the interopability state with Skype for Business.  This cmdlet allows admins to grant user level policies to individual users.
+The Teams Calling Policies designate which users are able to use calling functionality within teams and determine the interoperability state with Skype for Business.  This cmdlet allows admins to grant user level policies to individual users.
 
 ## EXAMPLES
 

skype/skype-ps/skype/Grant-CsTeamsInteropPolicy.md

@@ -23,15 +23,13 @@ Grant-CsTeamsInteropPolicy [-PassThru] [-Confirm] [[-PolicyName] <Object>] [[-Id
 
 ## DESCRIPTION
 
-IMPORTANT: TeamsInteropPolicy has been replaced by TeamsUpgradePolicy. It is no longer honored by the system, except if TeamsUpgradePolicy has mode=Lgeacy.  Legacy mode is being deprecated. Customers that are still using Legacy mode should update their configurations to use a mode other than Legacy.  Granting mode=Legacy is now blocked by default, although admins can override this using -Force for the time being. Eventually, the -Force switch will be removed and granting mode=Legacy will not be possible.
+IMPORTANT: TeamsInteropPolicy has been replaced by TeamsUpgradePolicy. It is no longer honored by the system, except if TeamsUpgradePolicy has mode=Legacy.  Legacy mode is being deprecated. Customers that are still using Legacy mode should update their configurations to use a mode other than Legacy.  Granting mode=Legacy is now blocked by default, although admins can override this using -Force for the time being. Eventually, the -Force switch will be removed and granting mode=Legacy will not be possible.
 
 Any customers still using Legacy mode must ensure the following:
- - The global policy must have CallingDefaultClient=ChatDefaultClient, and AllowEndUserClientOverride must be false.  If you customized the built-in global policy, undo this by running `Remove-CsTeamsInteropPolicy`. This will remove the tenant-specific global policy and revert back to the system-wide built-in policy (which cannot be removed). Use the following syntax:
- 
-Remove-CsTeamsInteropPolicy -Identity Global
 
- - If TeamsInteropPolicy is explicitly assigned to any users, one of these three built-in instances for which CallingDefaultClient = ChatDefaultClient, and for which AllowEndUserClientOverride = false. The other instances are no longer valid configurations, are  not supported, and will soon be removed from the system.  The valid instances are:
+ - The global policy must have CallingDefaultClient=ChatDefaultClient, and AllowEndUserClientOverride must be false.  If you customized the built-in global policy, undo this by running `Remove-CsTeamsInteropPolicy`. This will remove the tenant-specific global policy and revert back to the system-wide built-in policy (which cannot be removed). Use the following syntax: `Remove-CsTeamsInteropPolicy -Identity Global`.
 
+ - If TeamsInteropPolicy is explicitly assigned to any users, one of these three built-in instances for which CallingDefaultClient = ChatDefaultClient, and for which AllowEndUserClientOverride = false. The other instances are no longer valid configurations, are not supported, and will soon be removed from the system.  The valid instances are:
 
 **Identity: DisallowOverrideCallingDefaultChatDefault**   
 **AllowEndUserClientOverride: False**   
@@ -48,10 +46,7 @@ Remove-CsTeamsInteropPolicy -Identity Global
 **CallingDefaultClient: Teams**     
 **ChatDefaultClient: Teams**
 
-
-Use the following cmdlet syntax, where $policy is one of the above values of identity:
-`Grant-CsTeamsInteropPolicy -PolicyName $policy -Identity $SipAddress`
-
+Use the following cmdlet syntax, where $policy is one of the above values of identity: `Grant-CsTeamsInteropPolicy -PolicyName $policy -Identity $SipAddress`.
 
 For comprehensive documentation on this policy and its settings, see [Microsoft Teams and Skype for Business Interoperability](https://docs.microsoft.com/MicrosoftTeams/teams-and-skypeforbusiness-interoperability).
 
@@ -112,7 +107,7 @@ Accept wildcard characters: False
 ```
 
 ### -Identity
-For this cmdlet, the full UserPrincipleName/SIP address is required. If you don't provide the full UPN/SIP and instead provide an Alias, the cmdlet can throw an "Object reference not set to an instance of an object" error.
+For this cmdlet, the full UserPrincipalName/SIP address is required. If you don't provide the full UPN/SIP and instead provide an Alias, the cmdlet can throw an "Object reference not set to an instance of an object" error.
 
 ```yaml
 Type: Object
@@ -217,7 +212,7 @@ Accept wildcard characters: False
 ### System.Object
 
 ## NOTES
-This policy has been deprecated. Customters should use TeamsUpgradePolicy to control interop and routing.
+This policy has been deprecated. Customers should use TeamsUpgradePolicy to control interop and routing.
 
 ## RELATED LINKS
 

skype/skype-ps/skype/Grant-CsTeamsUpgradePolicy.md

@@ -52,13 +52,13 @@ Office 365 provides all relevant instances of TeamsUpgradePolicy via built-in, r
 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.  
-    - In on-premises with Skype for Business Server, the only availble option is to trigger notifications. 
+    - In on-premises with Skype for Business Server, the only available option is to trigger notifications. 
 - TeamsUpgradePolicy in Office 365 can be granted to users homed on-premises in hybrid deployments of Skype for Business as follows:
     - Coexistence mode is honored by users homed on-premises, however on-premises users cannot be granted the UpgradeToTeams instance (mode=TeamsOnly) of TeamsUpgradePolicy.  Users must be either homed in Skype for Business Online or have no Skype account anywhere to be upgraded to TeamsOnly mode.    
-    - The NotifySfBUsers setting of Office 365 TeamsUpgradePolicy is not honored by users homed on-premises. Instead, the on-premise version of TeamsUpgradePolicy must be used. 
-- In Office 365, all relevant instances of TeamsUpgradePolicy are built into the system, so there is no corresponding New cmdlet avaiable. 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.
+    - The NotifySfBUsers setting of Office 365 TeamsUpgradePolicy is not honored by users homed on-premises. Instead, the on-premises version of TeamsUpgradePolicy must be used. 
+- 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.
 - Instances with mode set to SfBWithTeamsCollab are not yet functional. From a routing perspective, this will behave like SfBOnly mode.
-- The Action property is redundnant with the combination of NotifySfBUsers and Mode. It will eventually be removed. 
+- The Action property is redundant with the combination of NotifySfBUsers and Mode. It will eventually be removed. 
 
 
 ## EXAMPLES
@@ -68,14 +68,14 @@ NOTES:
 PS C:\> Grant-CsTeamsUpgradePolicy -PolicyName UpgradeToTeams -Identity [email protected]
 ```
 
-The above cmdlet assigns the "UpgradeToTeams" policy to user [email protected].  This effectively upgrades the user to Teams only mode. This command will only succeed if the user does not have on-premises Skype for Business account. 
+The above cmdlet assigns the "UpgradeToTeams" policy to user [email protected].  This effectively upgrades the user to Teams only mode. This command will only succeed if the user does not have an on-premises Skype for Business account. 
 
 ### Example 2: Grant Policy to the entire tenant 
 ```
 PS C:\> Grant-CsTeamsUpgradePolicy -PolicyName SfBOnly 
 ```
 
-To grant a policy to all users in the org (except any that have an explicit policy assinged), omit the identity parameter.
+To grant a policy to all users in the org (except any that have an explicit policy assigned), omit the identity parameter.
 
 ## PARAMETERS
 

skype/skype-ps/skype/Grant-CsTeamsVideoInteropServicePolicy.md

@@ -29,13 +29,13 @@ Grant-CsTeamsVideoInteropServicePolicy [-PolicyName] <String> [-Tenant <System.G
 ## DESCRIPTION
 Cloud Video Interop for Teams enables 3rd party VTC devices to be able to join Teams meetings.  You can use the TeamsVideoInteropServicePolicy cmdlets to enable Cloud Video Interop for particular users or for your entire organization.  Microsoft provides pre-constructed policies for each of our supported partners that allow you to designate which of the partners to use for cloud video interop.  
 
-The Grant-CsTeamsVideoInteropServicePolicy cmdlet allows you to assign a pre-constructed policies for use in your organization or assign the policy to specific users.
+The Grant-CsTeamsVideoInteropServicePolicy cmdlet allows you to assign a pre-constructed policy across your whole organization or only  to specific users.
 
 ## EXAMPLES
 
 ### Example 1
 ```powershell
-PS C:\> Grant-CsTeamsVideoInteropServicePolicy  -PolicyName ServiceProviderDisabled
+PS C:\> Grant-CsTeamsVideoInteropServicePolicy -PolicyName ServiceProviderDisabled
 ```
 
 In this example, Cloud Video Interop has been disabled for the entire tenant, except for those users that have an explicit policy assigned to them.
@@ -125,7 +125,7 @@ Accept wildcard characters: False
 ```
 
 ### -PolicyName
-Specify the pre-constructed policy that you would like to assign to your tenant or a particular user.  You can get the policies available for your organization using the cmdlet Get-CsTeamsVideoInteropServicePolicy
+Specify the pre-constructed policy that you would like to assign to your tenant or a particular user.  You can get the policies available for your organization using the cmdlet Get-CsTeamsVideoInteropServicePolicy.
 
 ```yaml
 Type: String

skype/skype-ps/skype/Grant-CsTenantDialPlan.md

@@ -26,12 +26,14 @@ A tenant dial plan determines such things as how normalization rules are applied
 You can check whether a user has been granted a per-user tenant dial plan by calling a command in this format: `Get-CsOnlineUser "\<user name\>" | Select-Object TenantDialPlan.`
 ## EXAMPLES
 
-### -------------------------- Example 1 -------------------------- (Skype for Business Online)
+### -------------------------- Example 1 --------------------------
+
+(Skype for Business Online)
 ```
 Grant-CsTenantDialPlan -PolicyName Vt1tenantDialPlan9 -Identity (Get-CsOnlineUser Vt1_User1).SipAddress
 ```
 
-This example grants the Vt1tenantDialPlan 9 dial plan to Vt1_User1.
+This example grants the Vt1tenantDialPlan9 dial plan to Vt1_User1.
 
 
 ## PARAMETERS
@@ -102,7 +104,6 @@ Accept wildcard characters: False
 ```
 
 ### -PassThru
-PARAMVALUE: SwitchParameter
 
 ```yaml
 Type: SwitchParameter
@@ -136,8 +137,7 @@ Accept wildcard characters: False
 ```
 
 ### -WhatIf
-The WhatIf switch causes the command to simulate its results.
-By using this switch, you can view what changes would occur without having to commit those changes.
+Shows what would happen if the cmdlet runs. The cmdlet is not run.
 
 ```yaml
 Type: SwitchParameter

skype/skype-ps/skype/Grant-CsThirdPartyVideoSystemPolicy.md

@@ -27,7 +27,7 @@ One key management task related to VTC devices is to enable (or disable) the abi
 By default, VTC devices are allowed to send low-resolution video.
 However, administrators can create third-party video system policies that disable the use of low-resolution video.
 This might be useful for devices located in conference rooms or other areas where low-resolution video is not considered acceptable.
-The Grant-CsThirdPartyVideoSystem cmdlet provides a way for administrators to assign (or unassign) third-party video system policies created at the per-user scope.
+The Grant-CsThirdPartyVideoSystemPolicy cmdlet provides a way for administrators to assign (or unassign) third-party video system policies created at the per-user scope.
 
 Note that this cmdlet can only be used to assign per-user policies; that's because policies at the global or the site scope do not need to be assigned.
 If you want a VTC device to be managed by the global policy or (if available) the device site policy, simply unassign any per-user policy previously assigned to the device.
@@ -48,7 +48,7 @@ This device is then piped to the Grant-CsThirdPartyVideoSystemPolicy cmdlet, whi
 ### -------------------------- Example 2 -------------------------- 
 ```
 
-Get-CsThirdPartyVideoSystem -Filter {DisplayName -eq "Redmond Video Contact"} | Grant-CsThirdPartyVideoSystemPolicy -PolicyName $Null
+Get-CsThirdPartyVideoSystem -Filter {DisplayName -eq "Redmond Video Device"} | Grant-CsThirdPartyVideoSystemPolicy -PolicyName $Null
 ```
 
 The command shown in Example 2 is effectively the inverse of the command shown in Example 1: in this case, any per-user policy previously assigned to Redmond Video Device is removed.