.. _hybrid-cisco-microsoft-conversion:
Hybrid Cisco-Microsoft Conversion
-----------------------------------------------
.. _21.3|VOSS-891:
.. _25.4|EKB-20034:
.. tip::
:ref:`use-action-search-to-navigate-automate`
Overview
............
The flowchart outlines a Cisco-Microsoft hybrid set up in Automate.
.. index:: Flowchart;Microsoft-Cisco Hybrid Overview
.. include:: microsoft-cisco-hybrid-user-provisioning.uml
.. _cisco-ms-hybrid-subscribers:
Provision and manage hybrid Cisco-Microsoft users
.......................................................
Use the **Hybrid Cisco-Microsoft Conversion** page to provision
and manage subscribers with Cisco and Microsoft devices and services.
.. rubric:: Related topics
* :ref:`user-profiles`
* :ref:`ms-cisco-hybrid-service-definitions`
* :ref:`global-settings`
*
.. raw:: html
Number Inventory Updates for Hybrid Support
.. raw:: latex
Number Inventory Updates for Hybrid Support topic under Number Management
Provisioning workflow
''''''''''''''''''''''''''
.. index:: Flowchart;Hybrid Cisco-Microsoft User Provisioning
.. include:: microsoft-cisco-hybrid-user-provisioning.uml
.. rubric:: Prerequisites
* Enable the following Global Setting **Enable Cisco / Microsoft Hybrid**.
See: **Enabled Services** at :ref:`global-settings`.
* To add new hybrid users, sync in the MS Teams users at the customer level.
For the management of Microsoft users, see: :ref:`microsoft-quick-start`.
.. rubric:: Workflow steps
.. note::
For a user selected on the **Users** page, these hybrid user management
tasks can also be carried out on the **Hybrid Status** tab of the user by selecting the
**Update Hybrid Status** link.
1. Log in to the Admin Portal as a provider admin.
#. Go to **Hybrid Cisco-Microsoft Conversion**
#. Choose the relevant site.
#. Configure settings:
* In the **Username** field, select the user. MS Teams users should be synced in.
The user's **CUCM User Identity / AD UserPrincipalName** should match **MS Teams UserPrincipalName**
* To include users higher in the hierarchy in the **Username** drop-down, select **Include users at higher hierarchy**.
#. When managing a user with existing Cisco or Microsoft services, these services display
in the list of fields on the **Existing Services** - **User Status & Existing Services** form.
#. Select the required **Hybrid Service** type from the drop-down.
The **Entitlement Profile** and **Quick Add Group** are hidden as these are associated with the service type.
#. The **Directory Number** drop-down list is available to select a number after selecting a service type.
.. note::
If the "Cisco-MS-Hybrid" service type is selected, the choice of Directory Number (Internal or E164)
will determine the provisioning.
For details on all the service types, see: :ref:`ms-cisco-hybrid-service-definitions`.
Automatic Move of Microsoft Elements on Hybrid User Delete
............................................................
When deleting a hybrid (Cisco/Microsoft) multi-vendor user from a site and that user has
Microsoft (Teams/365) accounts, the system automatically moves the user's Microsoft-related models from
the site to the customer level.
The following models are moved:
* ``data/User``
* ``device/msteamsonline/CsOnlineUser``
* ``device/msgraph/MsolUser``
* ``device/msexchangeonline/UserMailbox``
This behavior is implemented by a post-delete workflow, *HybridMVS_RelationMoveAfterUserDeleteCleanupPWF*,
which runs *only* for hybrid MVS users and applies *only* to Microsoft elements. The models are moved, not purged.
Because the Microsoft artifacts are moved to the customer, you can re-add the user at another site without
manually relocating leftover Microsoft models.
If the user still exists in the Microsoft cloud portal, they will sync back into the system at the customer
level on the next Microsoft sync.
.. _ms-cisco-hybrid-service-definitions:
Hybrid service definitions
...............................
.. _21.3-PB1|EKB-12708:
.. note::
Consult with VOSS to customize the configuration of Hybrid Service Definitions
as well as dialplan additions.
A hybrid service refers to a particular multi-vendor configuration in VOSS Automate
and is characterized by a collection of settings, templates,
and workflows that apply to the management of a user to whom it is assigned.
This collection then determines a particular set of vendor services,
entitlement profiles, dial plan additions
for the user as well as workflows to run during user management.
.. note::
Hybrid services require:
* Configuration of the relevant multi-vendor devices on VOSS
* Vendor device user sync into VOSS
When selecting the **Hybrid** option in a **User Profile**,
a **Hybrid Service** can be selected and associated with the profile.
This service in the profile is associated with a service definition.
Hybrid user management allows for devices and services to be added to
*or removed* from a user in accordance with the current and newly selected
hybrid service for a user. The workflows in the current hybrid
service run to remove elements prior to the execution of workflows in
the new hybrid service to add elements.
For example:
* If a user has service type **MS-Only-Hybrid** and is
subsequently updated to have no Microsoft service type,
the user is updated to service type **No-Hybrid-Service**
and associated entitlement profile.
* If a user has service type **Cisco-MS-Hybrid** and is
subsequently updated to service type **Cisco-Only**, MS Teams devices are
removed from the user, preferred voicemail is updated to be "Cisco"
instead of "MS-Teams" and all multi-vendor entitlement profiles are
updated accordingly.
The following hybrid services are defined, with default attributes indicated:
* **Cisco-MS-Hybrid**
User has both Cisco Devices and a Teams Device with an associated E164 number.
Cisco Unified CM dial plan configuration allows incoming and outgoing calls.
* **Quick Add Group**: "System Quick Add Group Hybrid Enable User" - contains MS Teams User Template to enable MS Teams
* **Class of Service** and **Entitlement Profile**: by default empty.
Select a **Class of Service** to apply to MS Teams users and their calling rights.
The service type offers automatic configuration of services according to the selected **Directory Number**
in the Admin GUI: disabling **Use next available line** and then the selected **Line**.
This is carried out by a workflow selecting the appropriate dialplan template addition.
.. important::
Automate provides standard template additions to the standard Cisco HCS dialplan.
Contact VOSS if you wish to use alternative dial plan additions.
* Both Cisco Devices and a MS Teams Device have an associated E164 number.
The E164 Number is shared across all devices, for example:
* INI entry = 3334567, mapped to E164 = +15553334567.
* The number +15553334567 is set up in Microsoft as the line.
Calls from colleagues with Cisco phones to the user's Cisco phone will *simultaneously* dial this phone
and the MS Teams client. A SNR profile is used on the Cisco User to fork calls to the Teams Client.
* Internal number selected
User has both Cisco Devices and a MS Teams Device with no associated E164 number.
An E164 number is generated by adding a prefix (\+88800) to the internal number
for setup in Microsoft, for example:
* INI = 3334567
* The number \+1888003334567 is generated for use in MS Teams for that user.
The MS Teams user can dial:
* internal MS Teams users
* internal Cisco users
* external PSTN number (off-net via CUCM)
* **Cisco-No-Services**
All Cisco and Teams devices, multi-vendor services will be removed from the user.
* **Quick Add Group**: "System Quick Add Group Hybrid Disable User" - contains MS Teams User Template to disable MS Teams
* **Class of Service** and **Entitlement Profile**: by default empty
Select a **Class of Service** to apply to MS Teams users and their calling rights.
* **Cisco-Only_MV_SD**
User has only Cisco devices with an associated E164 Number. Multi-vendor, MS Teams services
removed if present.
* **Quick Add Group**: "System Quick Add Group Hybrid Disable User" - contains MS Teams User Template to disable MS Teams
* **Class of Service** and **Entitlement Profile**: by default empty
* **MS-Only-Entvoice_MV_SD**
User has only a MS Teams Device and selected Directory Number. MS Teams Dialplan.
* **Quick Add Group**: "System Quick Add Group Hybrid Enable User" - contains MS Teams User Template to enable MS Teams
* **Class of Service** and **Entitlement Profile**: by default empty
Select a **Class of Service** to apply to MS Teams users and their calling rights.
* **MS-Only-Hybrid_MV_SD**
User has only a MS Teams Device and selected Directory Number. Cisco Unified CM dial plan
configuration allows incoming and outgoing calls. Cisco user services are removed if present.
* **Quick Add Group**: "System Quick Add Group Hybrid Enable User" - contains MS Teams User Template to enable MS Teams
* **Class of Service** and **Entitlement Profile**: by default empty
Select a **Class of Service** to apply to MS Teams users and their calling rights.
* **MS-Only-No-Entvoice_MV_SD**
User has only a MS Teams Device and no Directory Number. No MS Teams Dialplan.
* **Quick Add Group**: "System Quick Add Group Hybrid Disable User" - contains MS Teams User Template to disable MS Teams
* **Class of Service** and **Entitlement Profile**: by default empty
Select a **Class of Service** to apply to MS Teams users and their calling rights.
* **No-Hybrid-Service_MV_SD**
User has no Cisco or MS Teams Devices.
* **Quick Add Group**: "VOSS-QAG_ExecUser - 88XX SIP"
* **Class of Service** and **Entitlement Profile**: by default empty
.. note::
When managing the hybrid services of administrator users by means of bulk loader sheets:
* Values for the ``mvs_hybrid_status`` field needs to be one of the service names as listed above.
* To unset this value in a bulk load sheet, leave the cell value for the ``mvs_hybrid_status`` field empty.
.. rubric:: Related topics
* :ref:`cisco-ms-hybrid-subscribers`
* :ref:`user-profiles`
*
.. raw:: html
Microsoft Hybrid Number Inventory
.. raw:: latex
Cisco - Microsoft Hybrid Number Inventory topic under Number Management