Use the Move User & Services page where there are existing Cisco UCM users at various sites, and then syncing in the Microsoft users at customer level. A check for mapping matches is carried out at site level to move the corresponding MS users down.

Hybrid and multi vendor move workflows have limited rollback support. When a multi vendor move fails, Cisco services roll back to the original site, but Microsoft services do not and remain at the destination site. Because the system does not retain the necessary prior configuration for Microsoft models (unlike Cisco CUCM-based services), Microsoft updates cannot be rolled back. Some move operations also do not generate rollback-supported steps, which prevents rollback from occurring. As a result, hybrid/multi vendor moves can leave the user split across sites if any part of the workflow fails.

Recent improvements increase rollback coverage in specific scenarios, but rollback is not guaranteed for all hybrid or multi vendor move operations.

All Cisco move functionality is available, including additional workflows for hybrid moves.

Automate allows you to move a non-hybrid, Microsoft-only user from one site to another site, with their services and a new line assigned.

The table describes how Automate processes various workflow elements in Microsoft-only user move:

Element	Description
Lines	The line can be moved along with the user, or assign a new line. If the number is shared, the "shared line policy" is removed prior to the move and re-assigned after the move.
Policies	Any policies previously assigned to the user that are not overwritten by the new site, remain unchanged.
Licensing	Licensing and usage location remain unchanged. If the user licenses don't match the supported new number type, a system message warns you that the user can't be moved.
Enterprise Voice	If Enterprise Voice is enabled at the source site and the target site is non-Enterprise Voice enabled, then Enterprise Voice is also disabled for the moved user at the target site.
Failure handling	If the target site does not support the move, the transaction fails with a descriptive error message.

Manually move a Microsoft user

This procedure manually moves a Microsoft user from one site to another site, with their existing or new services, and a new line.

Prerequisites:

Ensure you have available lines at the target site. In this case, available lines for Microsoft users.
To apply settings for the target site via a user profile, ensure the user profile is correctly configured for the services the user requires at the target site.

Move the user:

In the Admin Portal, go to Move User & Services.
Select a username to populate the page with the user's details and existing services.
Select an option at Move to Hierarchy. Existing services populate on the page.
Optionally, select a user profile. The read-only New Services fields update with the services assigned via the user profile.

Note

Values you select in the fields on the Move User & Services page override any settings updated by the user profile settings (if you selected a user profile).

Using a user profile to move the user allows you to apply the relevant Quick Add Group, policies, and configuration templates to update the user at their new location.

If you don't select a user profile, the user moves with their current settings, except for the line, since Automate either assigns the next available line at the new site, or you can choose a new line for the target site.
Optionally (valid for direct routing only), select a tenant dial plan, calling line identity, and an online voice routing policy.

Note

Values you select for these fields override values from the user profile for the new services.
At Line Configuration:
- Select New Line to create a new line at the target hierarchy, or leave the checkbox clear to use the existing line.
- To have the system find the next available line, select Use next available line, and optionally, select Inventory Filter so that the system can choose a line from a predefined pool of filtered numbers to be assigned, for example, only unused numbers with associated E164s, or unused numbers at the site only.
  
  Note
  
  By default, Automate selects the next line available at the current site (checks locally first). If no lines are available at the current site, the system looks up the hierarchy to the customer level and if an available line is found, the read-only Microsoft Line field populates with the selected line.
- Alternatively, manually select a line from the Line URI field, with or without a line inventory filter applied.
  
  Note
  
  The Line URI drop-down displays available lines for Microsoft users. No additional filtering is applied. The line you choose populates the New Line field at New Services.
Save your changes to move the user with their new services and line.

Move Microsoft user using flow-through provisioning

This procedure automatically moves an existing and already provisioned Microsoft user from one site to another site (the target site), with their existing or updated services (based on the user profile), and including a new number (line) at their new location.

Note

This scenario assumes the user's location (for example, their city or other geographic location) has been updated on the Microsoft Cloud portal (Microsoft 365 admin center) and you want to sync in this user to Automate and automatically update their location and services for the site they're moving to.

Configure model filter criteria for the Msoluser (Microsoft online user) for the target geographic location move.
Configure the site defaults.

Go to Defaults for the site. Verify the required model filter criteria is selected in the Move Filter Criteria pane (at the MS 365 User Model Filter Criteria drop-down).
Configure Global Settings.
- Go to Global Settings, and select the Flow Through Provisioning tab/panel.
- Set Enable Move & Provisioning after Update Sync to Yes (enabled) to allow the user to be provisioned and moved following a data sync.
- Optionally, select an option at Flow Through Provisioning Criteria for the flow through provisioning criteria set up to move the user/users to their new location.
Sync in the user:
- Execute manual sync:
  
  In the Automate Admin Portal, go to the Microsoft Tenant list view, and open the configuration page for the relevant tenant. From the overflow menu, select Sync New Users.
- Wait for scheduled sync:
  
  You can sync in and move the user via the automatic, scheduled sync (and not manually via Sync New Users in the tenant settings).
When the sync runs (manual or scheduled sync), Automate syncs in the user, moves that user to the target site with their new services (line, policies) from the user profile. If the user profile is set up to send the user a welcome email, the user receives an email with their new location and service details.

Related topics

User profiles
Model Filter Criteria
Site Defaults
Global Settings

Model Details: view/MultiVendorServiceUserMove_VIEW

An asterisk * in the title indicates the field is mandatory.
If a field has a default value, it is shown in the Description column.
If the field type is an array, the Field Name has a .[n] suffix, where n is the array index placeholder.
Object and array field names are listed to provide context. If a field belongs to an object or an array, the full field name is shown in dot separated notation.

Title			Description	Details
			Note about the Multi Vendor Service User move operation Default: Please note: If a user is enabled for Webex, the Move User configuration panels will remain hidden, as Webex users cannot be moved at this time.	Field Name: notes Type: String Default: Please note: If a user is enabled for Webex, the Move User configuration panels will remain hidden, as Webex users cannot be moved at this time. MaxLength: 1024
Username			Name of individual Multi Vendor Service User who will be moved.	Field Name: username Type: String MaxLength: 1024 Choices: [" "]
Move From Hierarchy			The name of the hierarchy node from which the Multi Vendor Service User will be moved from if the conditions are satisfied.	Field Name: move_from_hn Type: String MaxLength: 1024
Move To Hierarchy			The name of the hierarchy node to which the Multi Vendor Service User will be moved to if the conditions are satisfied.	Field Name: move_to_hn Type: String MaxLength: 1024 Choices: [" "]
New Role			The user role to use at the destination hierarchy	Field Name: move_to_role Type: String MaxLength: 1024
Allow Move of Lines				Field Name: AllowLineMove Type: Boolean
	New Lines			Field Name: lines.[n] Type: Array
		Line Template	Line template to use for configuration settings.	Field Name: lines.[n].template_name Type: String MaxLength: 1024
		Inventory Filter		Field Name: lines.[n].line_filter Type: String MaxLength: 1024
		Directory Number *	Directory Number of line to assign.	Field Name: lines.[n].directory_number Type: String MaxLength: 1024
		Label	Label to use for this line.	Field Name: lines.[n].label Type: String MaxLength: 1024
		Display	Display to use for this line.	Field Name: lines.[n].display Type: String MaxLength: 1024
Move Microsoft Services			Tick to move Microsoft 0365, Teams and Exchange User's if present for this User	Field Name: move_ms_teams Type: Boolean
Online Voice Routing Policy			Online Voice Routing Policy	Field Name: onlineVoiceRoutingPolicy Type: String MaxLength: 1024
Calling Line Identity			Calling Line Identity	Field Name: callingLineIdentity Type: String MaxLength: 1024
Tenant Dial Plan			Tenant Dial Plan	Field Name: tenantDialplan Type: String MaxLength: 1024
Tenant DP Required			Tenant DP Required	Field Name: tenantDPRequired Type: Boolean
Use next available line			Use the next available line from the inventory at the destination hierarchy. Default: false	Field Name: automatic_line Type: Boolean Default: false
Inventory Filter			Specify the type of number to assign from inventory	Field Name: line_filter Type: String MaxLength: 1024
Line URI				Field Name: line_uri Type: String MaxLength: 1024
Multivendor service line 1 class of service				Field Name: line1CoS Type: String MaxLength: 1024
MSOL User Present				Field Name: isMSOLuserPresent Type: Boolean
Configuration Template for Multi Vendor Service User Update			Optional Template for Multi Vendor Service User update on CUCM	Field Name: new_user_cft Type: String MaxLength: 1024
Move Lines to Destination Hierarchy			Tick to move any lines associated with the user to the destination hierarchy. If lines are moved, they will remain on the devices. Lines that are not moved may be retained on devices, or may be replaced Default: false	Field Name: move_line Type: Boolean Default: false
	Directory Number at destination		If Move E164 to Destination Hierarchy field is selected, this dropdown is displayed and is a list of choices of dissassociated INI's	Field Name: ini_destination.[n] Type: Array
		Pattern		Field Name: ini_destination.[n].line Type: String MaxLength: 1024
Warning			Optional Field discussing the reason for the readonly Move E164 to Destination Hierarchy field	Field Name: dissassociate_e164_message Type: String MaxLength: 1024
New Line			Create new line at the destination hierarchy. Use existing line if not ticked, even if line is not moved to the new hierarchy ( i.e shared line ). This applies to line 1 only. Subsequent lines must be modified if required after the move is complete. Default: false	Field Name: new_line Type: Boolean Default: false
Line Configuration Mapping			Line Configuration Mapping	Field Name: line_profile Type: String MaxLength: 1024
Android Profile			Android profile to be applied.	Field Name: android_profile Type: String MaxLength: 1024
CSF Profile			CSF profile to be applied.	Field Name: csf_profile Type: String MaxLength: 1024
Tablet Profile			Tablet profile to be applied.	Field Name: tablet_profile Type: String MaxLength: 1024
iPhone Profile			iPhone profile to be applied.	Field Name: iphone_profile Type: String MaxLength: 1024
Carrier Integrated Mobile Profile			Carrier Integrated Mobile profile to be applied.	Field Name: cim_profile Type: String MaxLength: 1024
CTI Remote Device Profile			CTI Remote Device profile to be applied.	Field Name: ctird_profile Type: String MaxLength: 1024
Move Desk Phones			Tick to move any desk phones(SEP prefix) associated with the user to the new hierarchy. Disassociate Subscriber from existing desk phones if not checked. Jabber/Soft Clients etc (non SEP prefix devices) are always moved. Default: true	Field Name: move_phone Type: Boolean Default: true
Create New Phone			Create New Phone at Destination Hierarchy	Field Name: new_phone Type: Boolean
Use Existing Phone Configuration			Toggle to select an existing Phone for configuration. Default: false	Field Name: new_phone_from_source Type: Boolean Default: false
Desk Phone Profile			Select the required Desk Phone Profile specified in Phone Configuration Mapping	Field Name: phone_type Type: String MaxLength: 1024
Phone Protocol				Field Name: new_phone_protocol Type: String MaxLength: 1024
Phone Name			e.g. SEP123412341234. Leave blank for auto generated MAC if you use phone based registration, select from list of free phones or provide a new phone name	Field Name: name Type: String MaxLength: 1024
Phone Configuration Source			Copy configuration from associated phone	Field Name: new_phone_config_source Type: String MaxLength: 1024
Phone Type to Copy Configuration from				Field Name: new_phone_config_source_product Type: String MaxLength: 1024
Phone Configuration Mapping			Phone Configuration Mapping	Field Name: phone_profile Type: String MaxLength: 1024
Device Profile Configuration Mapping			Device Profile Configuration Mapping	Field Name: dp_profile Type: String MaxLength: 1024
Desk Phone Feature Template			Optional Configuration Template name for phone parameter override	Field Name: new_phone_cft Type: String MaxLength: 1024
Phone Button Template				Field Name: new_phone_pbt Type: String MaxLength: 1024
Phone Security Profile				Field Name: new_phone_securityprofile Type: String MaxLength: 1024
Use Default CSS			Use the CSS defined as the site default at the destination hierarchy	Field Name: default_css Type: Boolean
Line CSS			Specify a specific CSS to be used at the destination hierarchy	Field Name: line_css Type: String MaxLength: 1024
Call Forward CSS			Specify a specific CSS to be used at the destination hierarchy	Field Name: cfwd_css Type: String MaxLength: 1024
Use Default Device Pool			Use the Default Device Pool defined as the site default at the destination hierarchy Default: true	Field Name: default_dp Type: Boolean Default: true
Device Pool			Specify a specific device pool to be used at the destination hierarchy	Field Name: device_pool Type: String MaxLength: 1024
Subscriber Profile			The profile to use for subscriber configuration.	Field Name: subscriber_profile Type: String MaxLength: 1024
Is CUCM User				Field Name: isCUCMUser Type: String MaxLength: 1024
Source CUCM				Field Name: guiSourceCucmBkey Type: String MaxLength: 1024
Target CUCM				Field Name: guiTargetCucmBkey Type: String MaxLength: 1024
Target CUCM PKID				Field Name: guiTargetCucmPkid Type: String MaxLength: 1024
Source CUC				Field Name: guiSourceCucBkey Type: String MaxLength: 1024
Target CUC				Field Name: guiTargetCucBkey Type: String MaxLength: 1024
CUCM changes				Field Name: guiNewCucm Type: Boolean
CUC Changes				Field Name: guiNewCuc Type: Boolean
Is E164 associated				Field Name: guiDisassociateE164 Type: Boolean
Caution				Field Name: CrossClusterMessage Type: String MaxLength: 1024
New Cuc User Template				Field Name: newCucUserTemplate Type: String MaxLength: 1024
Phones				Field Name: existingPhones Type: String MaxLength: 1024
Extension Mobility				Field Name: existingDeviceProfiles Type: String MaxLength: 1024
Single Number Reach				Field Name: existingSnr Type: String MaxLength: 1024
Voicemail				Field Name: existingVoicemail Type: String MaxLength: 1024
Pexip Conferencing				Field Name: existingPexip Type: String MaxLength: 1024
Contact Center				Field Name: existingContactCenter Type: String MaxLength: 1024
Microsoft Office365 User				Field Name: existing_msol Type: String MaxLength: 1024
Microsoft Teams User				Field Name: existing_csol Type: String MaxLength: 1024
Microsoft Line				Field Name: existing_URILine Type: String MaxLength: 1024
Tenant Dial Plan				Field Name: existing_tenant_dp Type: String MaxLength: 1024
Calling Line Identity				Field Name: existing_calling_line_id Type: String MaxLength: 1024
Online Voice Routing Policy				Field Name: existing_online_voice_routing_policy Type: String MaxLength: 1024
Hybrid Status				Field Name: existing_hybrid Type: String MaxLength: 1024
Tenant Dial Plan				Field Name: new_tenant_dp Type: String MaxLength: 1024
Calling Line Identity				Field Name: new_calling_line_id Type: String MaxLength: 1024
Online Voice Routing Policy				Field Name: new_online_voice_routing_policy Type: String MaxLength: 1024
Phones				Field Name: newPhones Type: String MaxLength: 1024
Extension Mobility				Field Name: newDeviceProfiles Type: String MaxLength: 1024
Single Number Reach				Field Name: newSnr Type: String MaxLength: 1024
Voicemail				Field Name: newVoicemail Type: String MaxLength: 1024
Pexip Conferencing				Field Name: newPexip Type: String MaxLength: 1024
Contact Center				Field Name: newContactCenter Type: String MaxLength: 1024
Microsoft Office365 User				Field Name: new_msol Type: String MaxLength: 1024
Microsoft Teams User				Field Name: new_csol Type: String MaxLength: 1024
Microsoft Line				Field Name: new_URILine Type: String MaxLength: 1024
Hybrid Status				Field Name: new_hybrid Type: String MaxLength: 1024

Model: view/MultiVendorServiceUserMove_VIEW

Move User and Services

Manually move a Microsoft user

Move Microsoft user using flow-through provisioning

Model Details: view/MultiVendorServiceUserMove_VIEW