.. _overbuild-msft:

Overbuild for Microsoft
--------------------------


.. important::

   It is recommended that VOSS Automate training and/or VOSS Services are engaged
   during the initial use of the feature to help ensure optimized processes
   and guidance.

The Overbuild feature enables Provider and Reseller Administrators to
integrate existing, deployed Microsoft Tenants into VOSS Automate
without re-provisioning, unless required. 

In VOSS Automate, a Microsoft Tenant shows the combined and specific details
of a MS Office 365 and MS Teams tenant.

Overbuild provides tools to help the administrator
manage Microsoft Tenant data synced from existing configurations.

While a Microsoft Tenant does not contain such VOSS Automate components
as a hierarchy or a subscriber, the relationship with Microsoft Tenant components
makes it possible to, for example, create a VOSS Automate subscriber at a site hierarchy
during the Overbuild process. The necessary filters can be set up and
workflows, macros, and brownfield move processes are available for this purpose.

After overbuild is run for the first time, a schedule is created in VOSS Automate 
that can be set up to run at a selected interval.

The table describes overbuild logic for handling users and subscribers: 

.. tabularcolumns:: |p{4cm}|p{11cm}|

+-------------+------------------------------------------------------------+
| Component   | Description                                                |
+=============+============================================================+
| Users       | The synced in Microsoft Tenant user is moved to the site,  |
|             | based on the MS 365 model filter criteria selected for the |
|             | site in the site overbuild defaults. To allow this, ensure |
|             | you select **Include Site for Overbuild** and **Microsoft  |
|             | Users** (on the **Overbuild Defaults** tab in the site     |
|             | defaults).                                                 |
|             |                                                            |
|             | To view the number of Microsoft users at the hierarchy     |
|             | level (MS 365 users, MS Teams users, and MS Exchange       |
|             | users), go to **Overbuild > Overview Tool**.               |
+-------------+------------------------------------------------------------+
| Subscribers | A Microsoft tenant user can be set up with services using  |
|             | Quick Subscriber.                                          |
+-------------+------------------------------------------------------------+


.. rubric:: Related Topics 

* :ref:`qas-for-ms-users`.



Configure Overbuild Site Defaults for Microsoft
................................................

**Pre-requisite**:

* :ref:`user-move-for-microsoft`

.. note:: 
   
   * Ensure the NDLs are configured for the overbuild by adding tenant details, including 
     MS Exchange details if you wish to move mailboxes to the site in the overbuild. 
   * All Microsoft elements must be moved to customer level in a sync before running the overbuild, 
     which moves these elements to the sites. 


**To configure a site for overbuild**: 
  
1. In the VOSS Automate Admin Portal, go to (default menus) **Overbuild > Site Defaults**. 

.. note:: 

   Alternatively, go to (default menus) **Site Management > Defaults** and select the 
   **Overbuild Defaults** tab. 

2. Select the **Overbuild Defaults** tab. 
3. Configure the following: 
 
   * Enable **Include Site for Overbuild**
   * Enable **Microsoft Users**.  
   * From the **MS 365 User Model Filter Criteria** dropdown, select the relevant filter. For 
     more information about filters, see :ref:`model-filter-criteria`.


Run Overbuild
................

1. In the VOSS Automate Admin Portal, go to (default menus) **Overbuild > Run Overbuild**.
#. Choose the site.
#. In a Microsoft-only environment, select only **Microsoft Users** to include in the overbuild.
   
   .. note:: 

      This allows Microsoft users to move to the site. VOSS Automate looks at the MS user, and checks 
      whether it has MS Teams and MS Exchange, and moves these elements to the sites along with the 
      user.

#. Save your changes to run the overbuild.

.. note:: 

   The overbuild: 
   
   * Imports and provisions subscribers, including number assignment (INIs). 
   * Moves assigned numbers to the number inventory, flagged with the user's name, 
     location (customer or site), number status (**Used** when assigned, else, 
     **Available**), and the relevant vendor (Microsoft, in this case). 
 
   The number management step occurs on sync, overbuild, as well as in a number audit. You can 
   run a number audit anytime to verify that numbers are correctly flagged as used or 
   available (via **Number Management > Audit Number Inventory**) - see :ref:`run_the_directory_number_inventory_audit_tool`.



.. rubric:: Related Topics

* 
  .. raw:: latex

     Microsoft User Move Configuration in the Core Feature Guide

  .. raw:: html
  
     <a href="concepts-user-move-for-microsoft.html">Microsoft User Move Configuration</a> 

* 
  .. raw:: latex

     Model Filter Criteria in the Core Feature Guide

  .. raw:: html
  
     <a href="concepts-model-filter-criteria.html">Model Filter Criteria</a>

*
  .. raw:: latex

     Flow Through Provisioning in the Core Feature Guide

  .. raw:: html

     <a href="flow-through-provisioning.html">Flow Through Provisioning</a>