.. _sync-ms-users-to-sites:
Sync Microsoft users to sites
---------------------------------
.. _21.1|VOSS-847:
.. _24.1-PB1|EKB-21135:
Overview
...........
When setting up Automate for Microsoft, the final step involves syncing in Microsoft users.
.. note::
Syncing Microsoft users to sites is the final step for integrating Automate with Microsoft. For the
other steps, see :ref:`microsoft-quick-start`.
You can choose to either directly sync in the tenant dialplan, policies, licenses and Microsoft users to the customer,
or configure sync with flow through provisioning before syncing in Microsoft data and users:
.. note::
If you're syncing in users with a number that already exists at a site, by default, the system creates a duplicate
of the number. To prevent duplicate numbers in the number inventory, enable the following global settings:
:ref:`prevent-duplicate-numbers`.
* :ref:`sync-to-customer-then-site`
* :ref:`sync-to-site-with-flow-through`
The table compares the two sync types for Microsoft data and users.
.. tabularcolumns:: |p{7.5cm}|p{7.5cm}|
+--------------------------------------------------------+-------------------------------------------------------------------------------------+
| Sync to customer, then to site | Sync to site, with flow through provisioning |
+========================================================+=====================================================================================+
| Sync users to customer level, and then to sites | Configure Automate to sync in Microsoft users as fully provisioned, |
| schedules. | directly to the sites. |
| | |
| **Step 1**: Run a full pull sync to create default | |
| syncs and schedules, and move all of the following | **Step 1**: Configure the following: |
| to the customer level: | |
| | |
| * Tenant dialplan | |
| * Policies | * Model filter criteria |
| * Licenses | * Site defaults |
| * Microsoft users | * Quick Add Groups |
| | * User profile |
| **Step 2**: Configuration for moving users to sites: | * Configure the Microsoft tenant |
| | * Flow through provisioning criteria |
| | * Global settings (enable flow through) |
| * Configure model filter criteria (for overbuild) | |
| * Enable overbuild in the site defaults | **Step 2**: Run a sync to create default syncs and schedules. |
| * Configure Quick Add Groups | |
| * Configure user profile | * The sync creates default syncs and schedules, and syncs in the following to the |
| * If using Microsoft Enterprise Voice, configure | customer: |
| internal number inventory for sites | |
| | * Tenant dialplan |
| **Step 3**: Two options for moving users to sites: | * Policies |
| | * Licenses |
| * Run overbuild to move two or more users (batch) | |
| * Else, run Quick User to move a single user | * Syncs in Microsoft users as fully provisioned users, to the sites. |
| to a site | |
+--------------------------------------------------------+-------------------------------------------------------------------------------------+
.. note::
See :ref:`onboard-user-ms` for details around setting up Automate for managing licenses via a
configuration template and Quick Add Groups or User from Profile or field display policies (FDPs).
.. _sync-to-customer-then-site:
Sync to customer, then to site
...................................
This section provides a worfklow overview for moving Microsoft users to the sites once the
Microsoft tenant has been added and a full pull sync has been performed. The sync imports the tenant dialplan, policies, licenses, and Microsoft users to the customer level.
Now users must be provisioned and moved to the appropriate sites.
.. note::
Use these steps if you chose not to sync users directly to sites (in a sync with flow through after
setting up the NDLs).
.. rubric:: Prerequisites:
*
.. raw:: latex
Configure Automate for Microsoft services in the User Guide
.. raw:: html
Configure Automate for Microsoft services
.. rubric:: Workflow to sync to customer then to site
The flowchart sets out the steps to move Microsoft users to the sites after an initial sync to move users to
the customer level:
.. index:: Flowchart;Microsoft User Move Configuration
.. include:: microsoft-user-move-configuration.uml
.. rubric:: Related Topics
* :ref:`microsoft-overview`
* :ref:`sync-to-site-with-flow-through`
.. _sync-to-site-with-flow-through:
Sync to site with flow through provisioning
.................................................
When using sync with flow through provisioning for Microsoft users, you'll need to configure several
settings in Automate (including flow through provisioning criteria) before the initial sync from the
Microsoft Cloud. This allows Automate to apply the correct configuration, licenses, policies, and
services to imported users, and to move users to sites.
Once you run the sync, the tenant dialplans, policies, and licenses are imported
to the customer level, while users are imported, provisioned, licensed, and moved to the
correct sites.
.. rubric:: Prerequisites:
*
.. raw:: latex
Microsoft UC Application Setup in the Core Feature Guide
.. raw:: html
Microsoft UC Application Setup
*
.. raw:: latex
Configure Automate for Microsoft Services in the Core Feature Guide
.. raw:: html
Configure Automate for Microsoft Services
.. rubric:: Workflow to sync to site with flow through provisioning
The flowchart sets out the sync with flow through of Microsoft user and services:
.. include:: sync-with-flow-through-ms.uml
.. rubric:: Related Topics
*
.. raw:: latex
Microsoft Quick Start in the Core Feature Guide
.. raw:: html
Microsoft Quick Start
*
.. raw:: latex
Flow Through Provisioning in the Core Feature Guide
.. raw:: html
Flow Through Provisioning