.. _multi-vendor-move: Move user & services --------------------------- .. _21.3|VOSS-891: .. _21.4-PB4|EKB-14772: .. _25.4|EKB-17551: .. _25.4|EKB-26529: .. _25.4|EKB-27817: .. view/MultiVendorServiceUserMove_VIEW .. tip:: :ref:`use-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 can't be moved so options for moving a user are hidden on the page if you've selected a user enabled for Webex. .. rubric:: Prerequisites * Set the following Global Setting (:ref:`global-settings`) to True (enabled): **Enable Cisco / Microsoft Hybrid** .. note:: The **Move User & Services** view (``view/MultiVendorServiceUserMove_VIEW``) supports execution from **Provider** or **Reseller** hierarchy levels. This enables multi-vendor and hybrid move workflows (including QAS-driven moves) to successfully move CUCM users imported at Provider or Reseller level down to a target site, without encountering hierarchy rule violations. Rollback limitations for Hybrid / Multi Vendor Moves ......................................................... 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. Move scenarios .............. All Cisco move functionality is available, including additional workflows for hybrid moves. Supported scenarios are: * Scenario 1 * Move MS Teams, MS 0365 * Set tenantDialplan (optional), onlineVoiceRoutingPolicy (optional) * Move INI and E164 association (if it is in a 1-to-1 association) and create at new site with new country if different * Delete SNR at home site and Add SNR at new site * Set the INI at new site according to Service Type * Scenario 2 * Move MS Teams, MS 0365 * Set tenantDialplan (optional), onlineVoiceRoutingPolicy (optional) * Move INI * Delete SNR at home site and Add SNR at new site * Set the INI at new site according to Service Type * Scenario 3 * Move MS Teams, MS 0365 * Set tenantDialplan (optional), onlineVoiceRoutingPolicy (optional) * new INI at new site * Delete SNR at home site and Add SNR at new site * Set the INI at new site according to Service Type * Scenario 4 * Move MS Teams, MS 0365 * Set tenantDialplan (optional), onlineVoiceRoutingPolicy (optional) * new INI/E164 association at new site * Delete SNR at home site and Add SNR at new site * Set the INI at new site according to Service Type * Scenario 5 * Move MS Teams, MS 0365 * Set tenantDialplan (optional), onlineVoiceRoutingPolicy (optional) * *Do nothing* with lines, do not select anything in **Lines** tab - the assumption is that there was a bulk pre-move of lines to the new site: INI and/or INI/E164 numbers. * Delete SNR at home site and Add SNR at new site * Set the INI at new site according to Service Type * Scenario 6 * If INI is associated to a range of E164s and there is an attempted move line, then this fails with workflow validation. .. note:: * From release 24.1, the **Line Template** drop-down under **Line Configuration** is not used by this feature. Any customizations (for example Field Display Policies) that referenced this field, should be updated to remove references to it. * If the user has any other Cisco services that were not added by the hybrid feature, such as Phone, EM, RDP, VM etc., these will be moved by the Cisco user move workflows during the Hybrid-Multivendor-Move calls. If a Cisco CUCM user exists at the Customer level while the associated ``data/User`` already exists at the destination site, VOSS automatically determines the correct source hierarchy and moves the CUCM user to the site as part of the Move User & Services operation. * In **Multi Vendor Service User Configuration**, the **New Role** list of available roles will include those where the **Hierarchies Allowed** list of the role contains the target hierarchy selected in the **Move To Hierarchy** list. See: :ref:`role-management`. * When moving a user that has Microsoft services, and the destination (move to) hierarchy has MS Teams site defaults (SDD) values set up for *Online Voice Routing Policy* or *Tenant Dial Plan*, these values are populated from the site defaults provided you're not setting different values for *Online Voice Routing Policy* or *Tenant Dial Plan* in the *Move user* GUI. Values you set for these items in the *Move user* GUI thus take precedence over values set up in the site defaults when moving a user. .. rubric:: Related topics * :ref:`global-settings` * :ref:`cisco-ms-hybrid-subscribers` * :ref:`ms-cisco-hybrid-service-definitions` * :ref:`user-profiles` * .. raw:: html Microsoft Hybrid Number Inventory .. raw:: latex Cisco - Microsoft Hybrid Number Inventory .. _move-ms-subscriber: Microsoft - Move user & services ................................. .. _25.1|VOSS-1251: .. _25.3|VOSS-1590: .. Model Details: view/MultiVendorServiceUserMove_VIEW .. tip:: :ref:`use-action-search-to-navigate-automate` 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: * Use the **Move User & Services** page in the Admin Portal * Use :ref:`flow-through-provisioning` along with a manual or scheduled sync to update a user in Automate that has been updated on the Microsoft cloud. Number types supported for moving a Microsoft-only user site-to-site: * Direct routing * Operator Connect * Calling plan * Teams Phone Mobile The table describes how Automate processes various workflow elements in Microsoft-only user move: .. tabularcolumns:: |p{5cm}|p{10cm}| +-----------------------+---------------------------------------------------------------------------------------+ | 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. | +-----------------------+---------------------------------------------------------------------------------------+ .. image:: /src/images/ms-move-users-and-services-new-line-unchecked.png .. rubric:: Related topics * :ref:`onboard-offboard-to-move-ms-user-between-sites` * :ref:`flow-through-provisioning` 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**: 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**: * Select **New Line** to create a new line at the target hierarchy, or leave the checkbox clear to use the existing line. .. image:: /src/images/ms-move-users-and-services-new-line-checked.png * 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**. 7. Save your changes to move the user with their new services and line. .. rubric:: Related topics * :ref:`user-profiles` 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. * 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. 4. 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. .. rubric:: Related topics * :ref:`user-profiles` * :ref:`model-filter-criteria` * :ref:`site-defaults` * :ref:`global-settings`