[Index]

Model: view/MultiVendorServiceUserMove_VIEW

Move User and Services

Full HTML Help

Tip

Use the Action search to navigate Automate

Overview

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.

Important

Webex users and their services cannot be moved. A banner on the Move User & Services page informs you that options for moving a user are hidden if you select a user enabled for Webex.

Prerequisites

Move scenarios

All of the Cisco move functionality is available, as well as extra workflows for the hybrid moves.

The following scenarios are supported:

Note

Related topics

the Cisco - Microsoft Hybrid Number Inventory topic under Number Management

Microsoft - Move user & services

Full HTML Help

Tip

Use the Action search to navigate Automate

Overview

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.

You can do this in two ways:

Number types supported for moving a Microsoft-only user site-to-site:

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.

Related topics

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:

Move the user:

  1. In the Admin Portal, go to Move User & Services.

  2. Select a username to populate the page with the user's details and existing services.

  3. Select an option at Move to Hierarchy. Existing services populate on the page.

  4. 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.

  5. 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.

  6. At Line Configuration:

  7. Save your changes to move the user with their new services and line.

Related topics

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.

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

  2. 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).

  3. Configure Global Settings.

  4. Sync in the user:

    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

Model Details: view/MultiVendorServiceUserMove_VIEW

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.
Username Name of individual Multi Vendor Service User who will be moved.
  • Field Name: username
  • Type: String
  • 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
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
  • Choices: [" "]
New Role The user role to use at the destination hierarchy
  • Field Name: move_to_role
  • Type: String
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
Inventory Filter
  • Field Name: lines.[n].line_filter
  • Type: String
Directory Number * Directory Number of line to assign.
  • Field Name: lines.[n].directory_number
  • Type: String
Label Label to use for this line.
  • Field Name: lines.[n].label
  • Type: String
Display Display to use for this line.
  • Field Name: lines.[n].display
  • Type: String
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
Calling Line Identity Calling Line Identity
  • Field Name: callingLineIdentity
  • Type: String
Tenant Dial Plan Tenant Dial Plan
  • Field Name: tenantDialplan
  • Type: String
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
Line URI
  • Field Name: line_uri
  • Type: String
Multivendor service line 1 class of service
  • Field Name: line1CoS
  • Type: String
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
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
Warning Optional Field discussing the reason for the readonly Move E164 to Destination Hierarchy field
  • Field Name: dissassociate_e164_message
  • Type: String
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
Android Profile Android profile to be applied.
  • Field Name: android_profile
  • Type: String
CSF Profile CSF profile to be applied.
  • Field Name: csf_profile
  • Type: String
Tablet Profile Tablet profile to be applied.
  • Field Name: tablet_profile
  • Type: String
iPhone Profile iPhone profile to be applied.
  • Field Name: iphone_profile
  • Type: String
Carrier Integrated Mobile Profile Carrier Integrated Mobile profile to be applied.
  • Field Name: cim_profile
  • Type: String
CTI Remote Device Profile CTI Remote Device profile to be applied.
  • Field Name: ctird_profile
  • Type: String
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
Phone Protocol
  • Field Name: new_phone_protocol
  • Type: String
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
Phone Configuration Source Copy configuration from associated phone
  • Field Name: new_phone_config_source
  • Type: String
Phone Type to Copy Configuration from
  • Field Name: new_phone_config_source_product
  • Type: String
Phone Configuration Mapping Phone Configuration Mapping
  • Field Name: phone_profile
  • Type: String
Device Profile Configuration Mapping Device Profile Configuration Mapping
  • Field Name: dp_profile
  • Type: String
Desk Phone Feature Template Optional Configuration Template name for phone parameter override
  • Field Name: new_phone_cft
  • Type: String
Phone Button Template
  • Field Name: new_phone_pbt
  • Type: String
Phone Security Profile
  • Field Name: new_phone_securityprofile
  • Type: String
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
Call Forward CSS Specify a specific CSS to be used at the destination hierarchy
  • Field Name: cfwd_css
  • Type: String
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
Subscriber Profile The profile to use for subscriber configuration.
  • Field Name: subscriber_profile
  • Type: String
Is CUCM User
  • Field Name: isCUCMUser
  • Type: String
Source CUCM
  • Field Name: guiSourceCucmBkey
  • Type: String
Target CUCM
  • Field Name: guiTargetCucmBkey
  • Type: String
Target CUCM PKID
  • Field Name: guiTargetCucmPkid
  • Type: String
Source CUC
  • Field Name: guiSourceCucBkey
  • Type: String
Target CUC
  • Field Name: guiTargetCucBkey
  • Type: String
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
New Cuc User Template
  • Field Name: newCucUserTemplate
  • Type: String
Phones
  • Field Name: existingPhones
  • Type: String
Extension Mobility
  • Field Name: existingDeviceProfiles
  • Type: String
Single Number Reach
  • Field Name: existingSnr
  • Type: String
Voicemail
  • Field Name: existingVoicemail
  • Type: String
Pexip Conferencing
  • Field Name: existingPexip
  • Type: String
Contact Center
  • Field Name: existingContactCenter
  • Type: String
Microsoft Office365 User
  • Field Name: existing_msol
  • Type: String
Microsoft Teams User
  • Field Name: existing_csol
  • Type: String
Microsoft Line
  • Field Name: existing_URILine
  • Type: String
Tenant Dial Plan
  • Field Name: existing_tenant_dp
  • Type: String
Calling Line Identity
  • Field Name: existing_calling_line_id
  • Type: String
Online Voice Routing Policy
  • Field Name: existing_online_voice_routing_policy
  • Type: String
Hybrid Status
  • Field Name: existing_hybrid
  • Type: String
Tenant Dial Plan
  • Field Name: new_tenant_dp
  • Type: String
Calling Line Identity
  • Field Name: new_calling_line_id
  • Type: String
Online Voice Routing Policy
  • Field Name: new_online_voice_routing_policy
  • Type: String
Phones
  • Field Name: newPhones
  • Type: String
Extension Mobility
  • Field Name: newDeviceProfiles
  • Type: String
Single Number Reach
  • Field Name: newSnr
  • Type: String
Voicemail
  • Field Name: newVoicemail
  • Type: String
Pexip Conferencing
  • Field Name: newPexip
  • Type: String
Contact Center
  • Field Name: newContactCenter
  • Type: String
Microsoft Office365 User
  • Field Name: new_msol
  • Type: String
Microsoft Teams User
  • Field Name: new_csol
  • Type: String
Microsoft Line
  • Field Name: new_URILine
  • Type: String
Hybrid Status
  • Field Name: new_hybrid
  • Type: String