Overbuild for Microsoft#
Overview#
The Overbuild feature enables Provider and Reseller administrators to integrate existing, deployed Microsoft tenants into VOSS Automate without re-provisioning, unless required.
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.
In 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 an 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 Automate that can be set up to run at a selected interval.
The table describes overbuild logic for handling users and subscribers:
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. |
Note
Guest users (Msol users external to the tenant) are synced in, but their group details (information about which groups they’re associated with) won’t be included in the sync.
Related Topics
Configure Overbuild Site Defaults for Microsoft#
Pre-requisite:
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:
In the 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. You can also fill out the search term, Site Defaults, in the Automate Admin Portal Search field to locate Site Defaults.
In the Site Defaults list view, click on a site to open its site default settings.
On the Overbuild Defaults tab, configure the following:
Enable Include Site for Overbuild
At Overbuild Device Control, choose Limit Moved Devices.
Select Microsoft Users to enable Microsoft users.
On the Move Filter Criteria tab, configure the following:
At MS 365 User Model Filter Criteria, select the relevant filter.
Note
For more information about filters, see Model Filter Criteria.
If required, select Move by Number.
Note
User data is moved to a site using Move by Number only if the synced in Microsoft Teams user’s LineURI matches a pre-loaded internal number at that site.
If you’ve selected a filter for MS 365 Model Filter Criteria and you’ve enabled Move by Number, the overbuild first processes MS 365 Model Filter Criteria, and then processes Move by Number.
For more information about options on the Move Filter Criteria tab, see Site Defaults in the Core Feature Guide.
Related Topics
Run Overbuild#
In the 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. 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 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 Audit Number Inventory.
Related Topics