Skype On-Premises Users | Move User to Cloud Voice rule – Cayosoft Help Center

Rule description

Move a user account enabled for Skype for Business from an on-premises Skype for Business deployment to Office 365.

When to use this rule

Note: Before using this rule in Administrator Console please navigate to Home > Configuration > Connected Systems Extensions > Microsoft Office 365 and set Connect to Microsoft Teams (Skype for Business Online) to Yes.

Use this rule when you need to move a user account enabled for Skype for Business from an on-premises Skype for Business deployment to Office 365.

Rule Settings

Query Section

Setting name	Description
Limit scope to this domain or OU	This setting defines the search query scope. To improve query performance, limit the scope to specific OU. Important: To test rule configuration, limit the rule scope to an OU that contains test user accounts.
AD query criteria	Query criteria are sent with the query and may improve query performance. Tip: For different samples on the criteria builder, see KB20180410-1.
Filter AD query results	To hide unwanted data based on criteria set the filtering conditions here. Tip: For optimal performance, use Query criteria above to filter objects whenever possible.
Include only licensed users	Prerequisite for moving a user to cloud: user must be assigned a license for Skype for Business Online (Plan 2). If using Teams, a Teams license must also be assigned.
Map Settings from File
Note: If no data source file is specified, all settings in Map Settings from File section will be ignored. In this case, the rule will define which users that are in the rule scope and will try to move them to Cloud Voice.
Data source	Specifies the text file to be used. The […] button allows to browse for the file and the Create/Edit button allows the creation or editing of the existing file in the built-in Data Source editor.
Separator used in file	Specify separator used in the file: comma or semi-colon.
Data source anchor attribute	Defines the column in the Data Source that will be used to find existent users in Active Directory. This value is compared to the Active Directory Anchor Attribute.
Active Directory anchor attribute	Defines the attribute in the Active Directory to which the Data Source anchor attribute is to be compared.
Filter CSV data	The filter can be used to filter by the values in the CSV file columns like {$_.ColumnName -eq 'value'}
Users with anchor not found in the file	You can select what users should be moved: those whose anchor not found in the CSV file or only those whose anchor is found in the CSV file.
More Options
Returned Properties	To display additional properties for each object found by the query, add those properties to the list.
Sort by	Sort result objects list.
Exclude disabled AD users	Specify if disabled AD user accounts should be excluded.
Maximum number of users	By default, all objects that you have provisioned in Microsoft Office 365 are returned. Tip: It is possible to change the default value in Microsoft Skype Server extension settings.
Post filter	In this filter, you can use both Active Directory attributes and column names from the CSV file.
Initialization Script
Script	Usually, rules use query criteria to limit the query search scope. It improves the performance of the executed rule. Due to PowerShell limitations, it is not possible to use calculated expressions in query criteria. That is the point where the initialization script can help. You can initialize a global variable in this setting and then use it in query criteria. Important: To use a variable, declared in the initialization script, in the query scope, it must be global: $global:<variable name>. Example: Update AD users, created in the last ten days. Add this initialization script: {$global:DatePeriod = (Get-Date).AddDays(-10)} Use $DatePeriod variable in query criteria builder:

Action Section

Setting name	Description
Target	Must be set to the ProxyFQDN value of the hosting provider. In most cases this is sipfed.online.lync.com.
Move to Teams	If set to Yes, 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.
Keep contacts and meetings	If set to No, moves the user account without moving contacts or meetings. Contacts and meetings are not recoverable. Note: You may encounter this error after running this rule: Error=(506), Description=(User is not hosted on expected deployment. User appears already moved. Details: ValidateOcsUser: HostingProvider sipfed.online.lync.com should be sipfed.online.lync.com.) This means that user contacts and meetings cannot be migrated to Cloud Voice. In this case, set Keep contacts and meetings to No. See Force parameter description in Move-csUser cmdlet article.
Advanced settings
Bypass Phone System check	By default, if the on-premise user is configured for Enterprise Voice, moving the user to Office 365 will provision the user for Microsoft Phone System, for which 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 Yes.
Bypass Audio Conference check	By default, if the on-premise user is configured for dial-in conferencing, moving the user to Office 365 will provision the user for Microsoft Phone System, for which 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 Yes.
ProxyPool	This setting is deprecated by Microsoft. It should be empty for most cases.

Output Section

This section defines the output format of this rule.

To get more information about this section, please see the Output section article.

Enforce/Schedule section

This section defines the schedule for how often to run the rule.

To get more information about this section, please see the Enforce/Schedule section article.

Change History

Version	Notes
7.3.0	The rule is introduced in the product.

Articles in this section

Skype On-Premises Users | Move User to Cloud Voice rule