Merge pull request MicrosoftDocs#5885 from MicrosoftDocs/master

Merges Master to Live. See commits for details.

Author: kenwith

skype/skype-ps/skype/Move-CsUser.md

@@ -21,7 +21,13 @@ Moves one or more user accounts enabled for Skype for Business Server to a new R
 ### (Default)
 
 ```
-Move-CsUser [-Identity] <UserIdParameter> [-Target] <Fqdn> [-Credential <PSCredential>] [-MoveToTeams] [-HostedMigrationOverrideUrl <String>] [-UseOAuth] [-BypassEnterpriseVoiceCheck] [-BypassAudioConferencingCheck] [-TenantAdminUserName] [-ProxyPool <Fqdn>] [-MoveConferenceData] [-UserList <String>] [-Confirm] [-Force] [-PassThru] [-WhatIf]  [<CommonParameters>]
+Move-CsUser [-Identity] <UserIdParameter> [-Target] <Fqdn> [-Credential <PSCredential>] [-MoveToTeams] [-HostedMigrationOverrideUrl <String>] [-UseOAuth] [-BypassEnterpriseVoiceCheck] [-BypassAudioConferencingCheck] [-TenantAdminUserName] [-ProxyPool <Fqdn>] [-MoveConferenceData] [-Report <String>] [-Confirm] [-Force] [-PassThru] [-WhatIf]  [<CommonParameters>]
+```
+
+### UserList
+
+```
+Move-CsUser -UserList <String> [-Target] <Fqdn> [-Credential <PSCredential>] [-MoveToTeams] [-HostedMigrationOverrideUrl <String>] [-UseOAuth] [-BypassEnterpriseVoiceCheck] [-BypassAudioConferencingCheck] [-TenantAdminUserName] [-ProxyPool <Fqdn>] [-MoveConferenceData] [-Report <String>] [-Confirm] [-Force] [-PassThru] [-WhatIf]  [<CommonParameters>]
 ```
 
 ## DESCRIPTION
@@ -36,9 +42,9 @@ The Move-CsUser cmdlet affects only the user's Skype for Business Server account
 
 When moving a user to or from Office 365 (either Skype for Business Online or Teams):
 
-- Skype for Business hybrid must be configured. For more information, see [Deploy hybrid connectivity between Skype for Business Server and Skype for Business Online](https://docs.microsoft.com/en-us/SkypeForBusiness/skype-for-business-hybrid-solutions/deploy-hybrid-connectivity/deploy-hybrid-connectivity).
-- To move a user to Office 365, specify the ProxyFqdn of the hosting provider as the Target. In most cases, this is "sipfed.online.lync.com" but in specialized environments there will be variants of this address. For more details, see [Move users between on-premises and cloud](https://docs.microsoft.com/en-us/skypeforbusiness/hybrid/move-users-between-on-premises-and-cloud).
-- When migrating from on-premises to the cloud, meetings are migrated from Skype for Business Server to online. If the `MoveToTeams` switch is specified, the meetings will be migrated to Teams meetings. Otherwise, meetings are migrated to Skype for Business Online. Teams-only users can still join meetings hosted in Skype for Business. For details see [Using the Meeting Migration Service (MMS)](https://docs.microsoft.com/en-us/skypeforbusiness/audio-conferencing-in-office-365/setting-up-the-meeting-migration-service-mms).
+- Skype for Business hybrid must be configured. For more information, see [Deploy hybrid connectivity between Skype for Business Server and Skype for Business Online](https://docs.microsoft.com/SkypeForBusiness/skype-for-business-hybrid-solutions/deploy-hybrid-connectivity/deploy-hybrid-connectivity).
+- To move a user to Office 365, specify the ProxyFqdn of the hosting provider as the Target. In most cases, this is "sipfed.online.lync.com" but in specialized environments there will be variants of this address. For more details, see [Move users between on-premises and cloud](https://docs.microsoft.com/skypeforbusiness/hybrid/move-users-between-on-premises-and-cloud).
+- When migrating from on-premises to the cloud, meetings are migrated from Skype for Business Server to online. If the `MoveToTeams` switch is specified, the meetings will be migrated to Teams meetings. Otherwise, meetings are migrated to Skype for Business Online. Teams-only users can still join meetings hosted in Skype for Business. 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).
 - 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.
@@ -49,9 +55,6 @@ When moving a user to or from Office 365 (either Skype for Business Online or Te
 > [!NOTE]
 > <ul><li>The MoveToTeams switch is only available on Skype for Business Server 2019 and CU8 for Skype for Business Server 2015. Organizations using other versions of Skype for Business Server must first move the user to Skype for Business Online, and then apply TeamsUpgradePolicy.</li><li>If you are using Skype for Business Server 2015 with CU8 or later, we recommend you pass the `-UseOAuth` switch, which ensures the on-premises code authenticates using OAuth, instead of Legacy LiveID authentication. In Skype for Business Server 2019 and later versions, OAuth is always used hence the switch is not relevant on those versions.</li></ul>
 
-
-
-
 ## EXAMPLES
 
 ### ------- EXAMPLE 1: Move a user to Teams-----------------------
@@ -89,6 +92,15 @@ Get-CsUser -OU "ou=Finance,dc=litwareinc,dc=com" | Move-CsUser -Target "atl-cs-0
 In Example 4, all the user accounts in the Finance organizational unit (OU) are moved to the Registrar pool atl-cs-001.litwareinc.com.
 To carry out this task, the command first uses the Get-CsUser cmdlet and the OU parameter to retrieve a collection of all the user accounts in the Finance OU. After the data has been retrieved, the information is piped to the Move-CsUser cmdlet, which moves each account in the collection to the Registrar pool atl-cs-001.litwareinc.com.
 
+### --------- EXAMPLE 5: Move multiple users listed in a file ---------------------------
+
+```powershell
+Move-CsUser -UserList C:\Folder1\Folder2\file1.txt -Target "atl-cs-001.litwareinc.com" -Report C:\Folder1\Folder2\out.csv
+```
+
+In Example 5, all the users listed in file1.txt are moved to the the Registrar pool atl-cs-001.litwareinc.com.
+Also, a detailed report is created in the out.csv file.
+
 ## PARAMETERS
 
 ### -Identity
@@ -298,7 +310,6 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-
 ### -Confirm
 
 Enables you to bypass the confirmation prompt that would otherwise appear when you attempt to move a user.
@@ -325,7 +336,7 @@ Accept wildcard characters: False
 
 ### -Report
 
-PARAMVALUE: String
+A CSV file to be created with detailed information about the move. You can supply the file name if you want to create the file in the current folder, or an absolute path.
 
 ```yaml
 Type: String
@@ -342,7 +353,7 @@ Accept wildcard characters: False
 
 ### -UserList
 
-A List of users to be moved, in the following format example: "sip:[email protected],sip:[email protected],sip:[email protected]".
+A text file with a list of users to be moved, in the following format example: "sip:[email protected],sip:[email protected],sip:[email protected]". You can supply the file name if it's located in the current folder, or the absolute path to the file.
 
 ```yaml
 Type: String

skype/skype-ps/skype/New-CsTeamsMeetingPolicy.md

@@ -26,8 +26,8 @@ New-CsTeamsMeetingPolicy [-Tenant <Guid>] [-Description <String>]
  [-AllowSharedNotes <Boolean>] [-AllowWhiteboard <Boolean>] [-AllowTranscription <Boolean>]
  [-MediaBitRateKb <UInt32>] [-ScreenSharingMode <String>] [-PreferredMeetingProviderForIslandsMode <String>]
  [-VideoFiltersMode <String>] [-Identity] <XdsIdentity> [-AllowEngagementReport <String>]
- [-AllowNDIStreaming <Boolean>] [-DesignatedPresenterRoleMode <String>] [-InMemory] [-Force] [-WhatIf] 
- [-Confirm] [<CommonParameters>]
+ [-AllowNDIStreaming <Boolean>] [-DesignatedPresenterRoleMode <String>] [-AllowPSTNUsersToBypassLobby <Boolean>]
+ [-InMemory] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>]
 ```
 
 ## DESCRIPTION
@@ -516,6 +516,21 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -AllowPSTNUsersToBypassLobby
+Determines whether a PSTN user joining the meeting is allowed or not to bypass the lobby. If you set this parameter to True, PSTN users are allowed to bypass the lobby as long as an authenticated user is joined to the meeting.
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ## INPUTS
 
 ### None

skype/skype-ps/skype/Set-CsUserCallForwardingSettings.md

@@ -53,10 +53,31 @@ Server auto-discovery needs to be enabled. There are no additional licensing req
 
 ### Example 1
 ```powershell
-PS C:\> {{ Add example code here }}
+PS C:\> Set-CsUserCallForwardingSettings -User [email protected] -DisableForwarding
 ```
 
-{{ Add example description here }}
+This example disables the user’s call forwarding settings.
+
+### Example 2
+```powershell
+PS C:\> Set-CsUserCallForwardingSettings -User [email protected] -EnableForwarding +4721956666
+```
+
+This example modifies the user’s call forwarding settings, activating call forwarding to a specific phone number.
+
+### Example 3
+```powershell
+PS C:\> Set-CsUserCallForwardingSettings -User [email protected] -EnableSimulRing Team -Team [email protected],[email protected] -TeamDelegateRingWaitTime 5
+```
+
+This example modifies the SimulRing settings, activating simultaneous ring for the users listed in the Team parameter.
+
+### Example 4
+```powershell
+PS C:\> Set-CsUserCallForwardingSettings -User [email protected] -DisableForwarding -UnansweredToVoicemail -UnansweredWaitTime 30
+```
+
+This example sends unanswered calls to voicemail after 30 seconds.
 
 ## PARAMETERS
 
@@ -77,8 +98,7 @@ Accept wildcard characters: False
 ```
 
 ### -DelegateRingWaitTime
-Specifies the time, in seconds, to wait before ringing delegates.
-Acceptable inputs: 0, 5, 10
+Specifies the time, in seconds, to wait before ringing delegates. Acceptable inputs: 0, 5, 10.
 
 
 ```yaml
@@ -95,7 +115,7 @@ Accept wildcard characters: False
 ```
 
 ### -Delegates
-Specifies list of delegates that calls will be forwarded to. This parameter can only be used with EnableForwarding and EnableSimulRing parameters.
+Specifies the list of delegates that calls will be forwarded to. This parameter can only be used with EnableForwarding and EnableSimulRing parameters.
 
 ```yaml
 Type: System.Management.Automation.PSListModifier`1[System.String]
@@ -143,9 +163,7 @@ Accept wildcard characters: False
 ```
 
 ### -EnableSimulRing
-This is a switch parameter that enables forwarding to the specified destination. Cannot be used along with the DisableForwarding and EnableForwarding parameters.
-oSimulRingDestination can be a phone number, delegates, or team call group.
-	Acceptable input formats: "<phone number>", Team, Delegates
+This is a switch parameter that enables forwarding to the specified destination. Cannot be used along with the DisableForwarding and EnableForwarding parameters. SimulRingDestination can be a phone number, delegates, or team call group. Acceptable input formats: "<phone number>", Team, Delegates.
 
 
 ```yaml
@@ -178,9 +196,7 @@ Accept wildcard characters: False
 ```
 
 ### -Team
-Specifies list of team members that calls will be forwarded to. The add and remove switches will add and remove specified users from the Team Members list. The replace parameter will set the list to the specified list, wiping out the previous list. Add and remove can be used together, but neither of them can be used along with replace.
-o	Acceptable input formats for add/remove/replace list: The inputs can be a single user address (in one of the below formats), or a comma separated list of user addresses, in the 4 standard formats that Identity parameter accepts.
-
+Specifies list of team members that calls will be forwarded to. The add and remove switches will add and remove specified users from the Team Members list. The replace parameter will set the list to the specified list, wiping out the previous list. Add and remove can be used together, but neither of them can be used along with replace. Acceptable input formats for add/remove/replace list: The inputs can be a single user address (in one of the below formats), or a comma separated list of user addresses, in the 4 standard formats that Identity parameter accepts.
 
 ```yaml
 Type: System.Management.Automation.PSListModifier`1[System.String]
@@ -196,7 +212,7 @@ Accept wildcard characters: False
 ```
 
 ### -TeamDelegateRingWaitTime
-{{ Fill TeamDelegateRingWaitTime Description }}
+Specifies the time, in seconds, to wait before ringing team members.
 
 ```yaml
 Type: Int32
@@ -212,7 +228,7 @@ Accept wildcard characters: False
 ```
 
 ### -UnansweredToOther
-{{ Fill UnansweredToOther Description }}
+Specifies that unanswered calls will be send to other user or phone number.
 
 ```yaml
 Type: String
@@ -228,7 +244,7 @@ Accept wildcard characters: False
 ```
 
 ### -UnansweredToVoicemail
-{{ Fill UnansweredToVoicemail Description }}
+Specifies that unanswered calls will be send to voicemail.
 
 ```yaml
 Type: SwitchParameter
@@ -244,7 +260,7 @@ Accept wildcard characters: False
 ```
 
 ### -UnansweredWaitTime
-{{ Fill UnansweredWaitTime Description }}
+Specifies the time, in seconds, to wait before send unanswered calls to voicemail.
 
 ```yaml
 Type: Int32
@@ -260,7 +276,7 @@ Accept wildcard characters: False
 ```
 
 ### -User
-{{ Fill User Description }}
+Specifies the SIP address of the user whose call forwarding settings will be modified.
 
 ```yaml
 Type: String

teams/teams-ps/teams/Get-CsBatchPolicyAssignmentOperation.md

@@ -132,7 +132,13 @@ Contains the status for each user in the batch.
 
 **Id:** The ID of the user as specified when the batch was submitted.  Either the user object ID (guid) or UPN/SIP/email.
 
-**result:** The result of the assignment operation for the user: Success or an error.
+**result:** The result of the assignment operation for the user: Success or an error. Some common errors include:
+- User not found. Check the ID or SIP address of the user to confirm it is correct. If the UPN or email address was used, but it does not match the SIP address, then the user will not be found.
+- Multiple users found with a given SIP address. This is typically a result of on-prem to cloud sync.  Check your directory and update the affected users.
+- User invalid. If you are syncing users from on-prem to the cloud, some users might not have been synced properly and are in an invalid state. Check the sync status for the user.
+- User ineligible for the policy or missing a necessary license.  Check the documentation for the specific policy type being assigned to understand the requirements and update the user accordingly.
+- The policy settings are incorrect.  Check the documentation for the specific policy type being assigned to understand the requirements and update the policy accordingly.
+- Unknown errors. In rare cases, there can be transient system errors that failed on all initial retry attempts during batch process.  Resubmit these users in a separate batch.
 
 **state:** The status for the user: NotStarted, InProgress, Completed
 

whiteboard/whiteboard-ps/whiteboard/whiteboard.md

@@ -8,7 +8,7 @@ title: Microsoft Whiteboard
 
 ## Description
 
-The following cmdlet references are for Microsoft Whiteboard. See [Overview](../../../whiteboard/docs-conceptual/overview.md) for details on installing the module. The module can only be run by a global tenant admin.
+The following cmdlet references are for Microsoft Whiteboard. See [Overview](../../docs-conceptual/overview.md) for details on installing the module. The module can only be run by a global tenant admin.
 
 ### [Get-Whiteboard](Get-Whiteboard.md)