Merge branch 'master' into typo-paramater

Author: kenwith

skype/skype-ps/skype/Grant-CsTeamsCallParkPolicy.md

@@ -11,7 +11,7 @@ schema: 2.0.0
 
 The TeamsCallParkPolicy controls whether or not users are able to leverage the call park feature in Microsoft Teams.  Call park allows enterprise voice customers to place a call on hold and then perform a number of actions on that call: transfer to another department, retrieve via the same phone, or retrieve via a different Teams phone.  The Grant-CsTeamsCallParkPolicy cmdlet lets you assign a custom policy to a specific user.
 
-NOTE: the call park feature currently only available in desktop and web clients.  Call Park functionality is currently completely disabled in mobile clients.  Supported with TeamsOnly mode
+NOTE: the call park feature currently only available in desktop, web clients and mobile clients.  Call Park functionality is currently on the roadmap for Teams IP Phones.  Supported with TeamsOnly mode for users with the Phone Sytem license
 
 ## SYNTAX
 

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

@@ -22,7 +22,7 @@ TeamsUpgradePolicy allows administrators to manage the transition from Skype for
 
 This cmdlet enables admins to apply TeamsUpgradePolicy to either individual users or to set the default for the entire organization. 
 
-IMPORTANT:  TeamsUpgradePolicy has replaced TeamsInteropPolicy. Components that previously honored TeamsInteropPolicy have been fully updated to honor TeamsUpgradePolicy instead. TeamsInteropPolicy is not honored and has been deprecated. Organizations with users in Legacy mode must update their configurations to use a different mode.
+**IMPORTANT:**  TeamsUpgradePolicy has replaced TeamsInteropPolicy, which is no longer honored. Components that previously honored TeamsInteropPolicy have been fully updated to honor TeamsUpgradePolicy instead. Both TeamsInteropPolicy and Legacy mode have been retired. 
 
 
 
@@ -201,21 +201,21 @@ Accept wildcard characters: False
 
 ## NOTES
 
-Legacy mode in TeamsUpgradePolicy has been deprecated and it is no longer possible to grant legacy mode. Customers using Legacy mode must update their configuration of TeamsUpgradePolicy to use one of the other modes.
-
-TeamsInteropPolicy has been replaced by TeamsUpgradePolicy. All components that previously honored TeamsInteropPolicy have been updated to honor TeamsUpgradePolicy instead. TeamsInteropPolicy is no longer honored and should not be used for routing.
+Legacy mode in TeamsUpgradePolicy has been deprecated and it is no longer possible to grant legacy mode. Both Legacy mode and TeamsInteropPolicy have been retired.
 
 
 
 
 ## RELATED LINKS
 
+[Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://docs.microsoft.com/en-us/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype)
+
+[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)
+
+[Coexistence with Skype for Business](https://docs.microsoft.com/en-us/microsoftteams/coexistence-chat-calls-presence)
+
 [Get-CsTeamsUpgradeConfiguration](Get-CsTeamsUpgradeConfiguration.md)
 
 [Set-CsTeamsUpgradeConfiguration](Set-CsTeamsUpgradeConfiguration.md)
 
 [Get-CsTeamsUpgradePolicy](Get-CsTeamsUpgradePolicy.md)
-
-[Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://docs.microsoft.com/en-us/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype)
-
-[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/skype-ps/skype/Move-CsUser.md

@@ -32,11 +32,17 @@ The Move-CsUser cmdlet enables you to move a user account enabled for Skype for
 The Move-CsUser cmdlet affects only the user's Skype for Business Server account location; it does not move the user's Active Directory account to a new organizational unit (OU) or other new location.  
 
 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 https://docs.microsoft.com/en-us/SkypeForBusiness/skype-for-business-hybrid-solutions/deploy-hybrid-connectivity/deploy-hybrid-connectivity
+ - 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, meeetings 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).
+- 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. 
  - Contacts are moved in all cases, unless -force is specified.
- - Meetings are migrated from Skype for Business Server to Skype for Business Online for any move from Skype for Business Server. Teams- only users can still join meetings hosted in Skype for Business.
- - 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.
- - 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 and also applies TeamsUpgradePolicy and TeamsInteropPolicy to the online user account.
+
+ 
+> [!NOTE]
+> 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.
 
 
 
@@ -52,8 +58,6 @@ Move-CsUser -Identity "[email protected]" -Target "sipfed.online.lync.com" -Mov
 
 In Example 1, the Move-CsUser cmdlet is used to move the user account with sip address [email protected] to Teams.  This user will now be a Teams only user. If -Credential parameter is not specified, the admin will be prompted for credentials.
 
-NOTE: The MoveToTeams switch is only available on Skype for Business Server 2019. Organizations using other versions of Skype for Business Server must first move the user to Skype for Business Online, and then apply TeamsUpgradePolicy.
-
 ### ------- EXAMPLE 2: Move a user to Skype for Business Online ---- 
 ```
 $cred=get-credential
@@ -128,7 +132,7 @@ Accept wildcard characters: False
 
 
 ### -MoveToTeams
-If specified, the user will be moved to Office 365 as a Teams-only user. This will ensure  incoming chats and calls land in the user's Teams client. This parameter is only available with the upcoming releases of Skype for Business Server 2019 and CU8 for Skype for Business Server 2015.
+If specified, the user will be moved to Office 365 as a Teams-only user. This will ensure incoming chats and calls land in the user's Teams client. This parameter is only available with Skype for Business Server 2019 and CU8 for Skype for Business Server 2015.
 
 ```yaml
 Type: SwitchParameter
@@ -164,7 +168,7 @@ Accept wildcard characters: False
 
 ### -HostedMigrationOverrideUrl
 
-The hosted migration service is the service in Office 365 that performs user moves. By default, there is no need to specify a value for this parameter, as long as the hosting provider has its AutoDiscover URL properly configured. However, a specific URL can be specified if required. 
+The hosted migration service is the service in Office 365 that performs user moves. By default, there is no need to specify a value for this parameter, as long as the hosting provider has its AutoDiscover URL properly configured and you are using an admin account the ends in .onmicrosoft.com. If you are using a user account from on-premises that synchronized to the cloud, you must specify this parameter.  See [Required administrative credentials](https://docs.microsoft.com/en-us/skypeforbusiness/hybrid/move-users-between-on-premises-and-cloud#required-administrative-credentials).
 
 
 
@@ -182,7 +186,7 @@ Accept wildcard characters: False
 ```
 
 ### -BypassAudioConferencingCheck
-By default, if the on-premise user is configured for dial in conferencing, moving the user to Office 365 will provision the user for Audio Conferencing, for an additional license is required.  If you want to move such a user to Office 365 but do not want to configure them for Audio Conferencing, specify this switch to by-pass the license check. This parameter is only available with the upcoming releases of Skype for Business Server 2019 and CU8 for Skype for Business Server 2015.
+By default, if the on-premise user is configured for dial in conferencing, moving the user to Office 365 will provision the user for Audio Conferencing, for an additional license is required.  If you want to move such a user to Office 365 but do not want to configure them for Audio Conferencing, specify this switch to by-pass the license check. This parameter is only available with Skype for Business Server 2019 and CU8 for Skype for Business Server 2015.
 
 ```yaml
 Type: SwitchParameter
@@ -196,7 +200,7 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 ### -BypassEnterpriseVoiceCheck
-By default, if the on-premise user is configured for Enteprise Voice, moving the user to Office 365 will provision the user for Microsoft Phone System, for an additional license is required.  If you want to move such a user to Office 365 but do not want to configure them for Phone System, specify this switch to by-pass the license check. This parameter is only available with the upcoming releases of Skype for Business Server 2019 and CU8 for Skype for Business Server 2015.
+By default, if the on-premise user is configured for Enteprise Voice, moving the user to Office 365 will provision the user for Microsoft Phone System, for an additional license is required.  If you want to move such a user to Office 365 but do not want to configure them for Phone System, specify this switch to by-pass the license check. This parameter is only available with Skype for Business Server 2019 and CU8 for Skype for Business Server 2015.
 
 ```yaml
 Type: SwitchParameter
@@ -211,7 +215,7 @@ Accept wildcard characters: False
 ```
 
 ### -TenantAdminUserName
-This is an optional parameter that if, specified, pre-populates the username of the tenant admin when moving users to or from Office 365. This can be useful for scenarios involving smart card authentication or 2 factor auth. This parameter is only available with the upcoming releases of Skype for Business Server 2019 and CU8 for Skype for Business Server 2015.
+This is an optional parameter that if, specified, pre-populates the username of the tenant admin when moving users to or from Office 365. This can be useful for scenarios involving smart card authentication or 2 factor auth. This parameter is only available with Skype for Business Server 2019 and CU8 for Skype for Business Server 2015.
 
 
 ```yaml
@@ -339,9 +343,11 @@ Instead, the cmdlet modifies instances of the Microsoft.Rtc.Management.ADConnect
 
 ## RELATED LINKS
 
-[Get-CsUser](Get-CsUser.md)
+[Move users between on-premises and cloud](https://docs.microsoft.com/en-us/skypeforbusiness/hybrid/move-users-between-on-premises-and-cloud)
 
 [Skype for Business Hybrid Solutions](https://docs.microsoft.com/en-us/SkypeForBusiness/skype-for-business-hybrid-solutions/skype-for-business-hybrid-solutions)
 
 [Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://docs.microsoft.com/en-us/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype)
 
+[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/skype-ps/skype/Set-CsMobilityPolicy.md

@@ -403,6 +403,9 @@ Accept wildcard characters: False
 When set to True (the default value) users will be allowed to save credentials information (such as passwords) on their mobile device.
 This information can then be applied to auto-logon scenarios.
 
+Note: If a user has AllowSaveCredentials set to False in the CsMobility policy, the Skype for Business App for iOS may sign out automatically when bringing it from the background to the foreground. This is due to the password not being saved anywhere but in the iOS process memory. Once the process is killed by the iOS system, the password will no longer be available, so the user will need to enter it again. However, there is no impact if modern authenticaion is implemented.
+
+
 
 ```yaml
 Type: Boolean

tools/office-cmdlet-updater/README.md

@@ -2,7 +2,7 @@
 
 ## Usage:
 1. Clone repo at: https://github.com/microsoftdocs/office-docs-powershell
-2. Configure your email address in tools/.local/config/default.json to receive emailed logs. (OPTIONAL)
+2. Configure your email address in tools/.local/default.json to receive emailed logs. (OPTIONAL)
 3. Confirm you have NodeJS installed.
     Open PowerShell or GitBash and type `npm --version`.
     If not, install from [https://nodejs.org/en/download/](https://nodejs.org/en/download/).
@@ -14,23 +14,20 @@
        - execute into console `winrm quickconfig`
     - Microsoft Teams:
        - https://www.powershellgallery.com/packages/MicrosoftTeams
+       - alternatively, it could be installed by the tool, check Notes section below
     - SharePoint Online:
        - https://www.microsoft.com/en-us/download/details.aspx?id=35588
-    - Exchange Online cmdlets could be imported using [this guide](https://docs.microsoft.com/en-us/powershell/exchange/exchange-online/connect-to-exchange-online-powershell/connect-to-exchange-online-powershell)
+    - Exchange Online:
+       - cmdlets could be imported using [this guide](https://docs.microsoft.com/en-us/powershell/exchange/exchange-online/connect-to-exchange-online-powershell/connect-to-exchange-online-powershell)
     - Whiteboard:
        - https://www.powershellgallery.com/packages/WhiteboardAdmin
-    - StaffHub:
-       - https://www.powershellgallery.com/packages/MicrosoftStaffHub
-    - Office Online Server cmdlets are not distributed separately
-    - SharePoint Migration Tool (SPMT):
-       - https://docs.microsoft.com/en-us/powershell/module/spmt
-7. Run the app, type `npm start` and press Enter.
+       - alternatively, it could be installed by the tool, check Notes section below
+7. Run the app, type `node index` and press Enter in order to get info for all modules
+8. Run the app for a certain module, type `node index -m <TypeModuleNameHere>`, with one of the following options - teams, skype, sharepoint, whiteboard, exchange. For example, you should run `node index -m teams` to run the tool for Microsoft Teams
+9. Run `node index -help` to get help information for all available commands
 
 ## Notes
-1. The modules are installed from the PowerShell Gallery (PSGallery).
-    This gallery contains user submitted code.
-    If you would rather not install modules from the PSGallery then you can install the modules manually prior to running the tool.
-    If you need to add PSGallery as a trusted source, you can do so with the following command:
-    `Set-PSRepository -Name "PSGallery" -InstallationPolicy Trusted`
+1. Some modules could be installed from the PowerShell Gallery (PSGallery). This gallery contains user submitted code. If you would rather not install modules from the PSGallery then you can install the modules manually prior to running the tool. If you need to add PSGallery as a trusted source, you can do so with the following command: `Set-PSRepository -Name "PSGallery" -InstallationPolicy Trusted`
+2. Run the tool from PowerShell x64 as an Administrator user
 
 ## Sample Run