VOSS-4-UC Configuration and Sync

When using VOSS-4-UC with Microsoft (as a single or multiple vendor deployment scenario), you’ll need to pre-configure several settings in VOSS-4-UC before importing Microsoft users, licenses, policies, and dialplans.

The flowchart sets out the initial configuration of VOSS-4-UC for Microsoft services.

Prerequisites:

@startuml 'VOSS-4-UC Configuration and Sync Flowchart !include style.iuml start note right: Prerequisite is Microsoft configuration :[[../src/user/concepts-hierarchy.html Hierarchy setup]]; note right * Create customers for tenant setup * [[../src/user/concepts-site-defaults-doc-templates.html CUSTOMER_TEMPLATE SDD]] created end note :[[../src/user/concepts-global-settings.html Global Settings]]; note right * Enable Microsoft * Enforce HCS Dialplan Rules:No end note :[[../src/user/concepts-role-based-access.html Role Based Access Control]]; note right * [[../src/user/create-user.html Add MS admin users]] * [[../src/user/role-management.html Add MS roles]], [[../src/user/tasks-menu-layout.html menu layout]] end note :[[../src/user/concepts-SMTP-server.html SMTP server]]; note right: Allows emails to user in QAS :[[../src/user/tasks-configure-ms-tenant.html Tenant setup]]; note right * requires [[../src/user/tasks-ms-configuration-setup.html Microsoft Authentication Setup]] * Enter PowerShell proxy details * Enter MS Teams admin credentials * Enter MS 365 IDs, keys end note -> Tenant data syncs on save; :[[../src/user/concepts-network-device-list.html Network Device Lists (NDL)]]; note right: Add NDL with Tenant details if (Using Flow-through?) then (NO) :Sync; note left Creates default * Syncs * Schedules end note -> Customer level; fork :[[../src/user/ms-tenant-dialplan.html Tenant Dialplan]]; stop fork again :[[../src/user/ms-teams-policies.html Policies]]; stop fork again :[[../src/user/concepts-ms-licenses.html Licenses]]; stop fork again :MS Users; end fork else (YES) :[[../src/user/concepts-sync-with-flow-through-for-microsoft.html Go to Sync with Flow Through]]; stop endif :[[../src/user/concepts-user-move-for-microsoft.html Go to Microsoft User Move Configuration]]; @enduml

Workflow for the VOSS-4-UC and Microsoft Configuration and Sync

The high-level workflow for the steps in the flowchart are as follows:

  1. Log in to VOSS-4-UC as a provider admin.

  2. Add customers.

  3. Go to Customizations > Global Settings to enable Microsoft:

    • On the Enabled Services tab, enable Microsoft services.

    • If you have a Microsoft-only environment, on the Number Inventory tab, set the following to No (False): Enforce HCS Dialplan Rules

      Note

      HSC dialplan is relevant only when using Cisco (in a single vendor or multi vendor installation).

  4. Configure role-based access controls to apply to users on import:

    VOSS-4-UC allows an admin user to set up pre-defined role-based configuration, which will be applied to users on import. This allows users to be auto-provisioned on import, with the correct services, lines, policies, and licenses.

    When preparing for import, you’ll need to create the admin users, service profiles, user roles, and role-based menu layouts (to hide or display functionality for different categories of users. For example, you can assign a Microsoft-only Business Admin Portal profile and Microsoft-only FDP to user roles for the Business Admin Portal in a Microsoft-only scenario. See Business Admin Portal Profiles in the Core Feature Guide for details.

  5. Configure a tenant, one for each customer. See Configure Microsoft Tenant on VOSS-4-UC

    The tenant configuration defines how VOSS-4-UC connects to the Microsoft Cloud, to allow syncing of data between VOSS-4-UC and Microsoft Azure, Microsoft 365, and Microsoft Teams. Saving the tenant creates the default syncs and schedules.

  6. Configure the network device lists (NDLs), which are required creating the sites. See Add a Network Device List (NDL)

  7. Go to the Tenant and click Action > Sync All to run a full pull sync.

    The tenant dialplan, policies, licenses, and Microsoft users are synced to the customer level.

    Note

    If you’re using flow through provisioning for Microsoft users, additional steps are required before running the initial sync. See Sync with Flow Through

Next Steps