Model: view/MicrosoftSubscriberQos

Microsoft Subscribers

To access the latest documentation, go to Documentation and Resources at: https://voss.portalshape.com

Overview

You will need to onboard Microsoft users to create Microsoft subscribers in VOSS Automate.

Onboarding a Microsoft user involves importing users and related data to the customer level from the Microsoft Cloud service, and then moving users to the correct sites as fully provisioned subscribers.

Automated workflows configure imported objects once changes are synced in, and apply the required configuration, policies, and licenses. This means administrators won't need to continually monitor the sync, or to perform additional steps to complete the process.

Once synced in (at the customer or site level), administrators can manage Microsoft users and subscribers via a single interface and login, from within the VOSS Automate Admin Portal. To maintain data integrity, to manage licenses, and to automate number auditing for synced in users, regular, targeted backend syncs poll for changes made at the device model layer.

To access the flowcharts, view the topic via Documentation and Resources at: https://voss.portalshape.com

Related Topics

Microsoft Overview in the Core Feature Guide

VOSS Automate Configuration and Sync in the Core Feature Guide

Sync with Flow Through in the Core Feature Guide

Microsoft Exchange in the Core Feature Guide

Onboarding Microsoft Users

VOSS Automate provides two onboarding options for Microsoft users:

Sync users to customer level, and then to sites

VOSS Automate Configuration and Sync

This option starts with an initial import of dial plans, policies, licenses, and Microsoft users, to the customer level (sync all to the tenant).

Then you will need to set up the configuration and user move criteria before moving users to the sites (set up model filter criteria, site defaults, quick add groups, subscriber profiles, and number inventory).

Finally, you have two options to move users to the sites as fully provisioned subscribers:

Run the overbuild to move multiple users to your sites at once.
Update single users via Quick Subscriber (for Microsoft users)

When moving users to site, the VOSS Automate automated workflow applies the required configuration, services, lines, policies, and licenses.

Sync users directly to sites

Sync with Flow Through

In this option, you run the initial sync together with flow through provisioning. In this case, you start by setting up the configuration and user move criteria before running the initial sync. That is, to set up the model filter criteria, site defaults, quick add groups, and subscriber profiles.

In addition, you will need to:

Configure flow through provisioning criteria
Enable flow through in the Global Settings

Once changes are synced in from the Microsoft Cloud, VOSS Automate automated workflows move the tenant dial plan, policies, and licenses to the customer level, and moves users directly to the appropriate sites as fully provisioned subscribers.

Note

VOSS Automate v21.2 introduced sync with flow through provisioning for Microsoft users. In 21.3, this feature extends the functionality to users synced in from LDAP and CUCM (Call Manager).
Only Add is supported for syncs with flow through provisioning. Update and delete are not supported since the requirements may differ depending on the customer scenario.
For details on the generic flow through provisioning feature (which includes Microsoft, LDAP, or CUCM users), see Flow Through Provisioning

Offboard a User

You can offboard a Microsoft subscriber by simply removing their Microsoft license, which removes all currently assigned services.

Note

In order to use this feature, you need to enable License Management in the Site Defaults Doc. Enable the setting Manage Licenses and Allow User Staging in your Site Defaults Doc.

If enabled, this setting will remove the license that is assigned to the user and will set the LineURI to null, i.e. disable MS Teams calling. If not set, then only the LineURI field is set to null and the user license is kept intact.

To offboard a user:

Log in to the Admin Portal.
Go to MS Subscriber Management > Subscribers.
Click on the relevant subscriber.
On the MS Licenses tab, delete the licenses.

View and Edit Microsoft Subscribers

This procedure displays and edits Microsoft subscribers.

View a summary list of all Microsoft subscribers

Log in to the VOSS Automate Admin Portal.
Choose the hierarchy.
Go to (default menus) Microsoft Subscriber Management > Subscribers.
On the Subscribers list, view a summary of Microsoft subscribers at the current hierarchy.

The Subscribers summary list view for Microsoft users provides details for the following, for each subscriber in the list:
- User principal name, first name, and last name
- Licenses
- Department
- City, country, phone number, location
- Associated device

View and update a single Microsoft subscriber

Log in to the VOSS Automate Admin Portal.
Choose the hierarchy.
Go to (default menus) Microsoft Subscriber Management > Subscribers.
On the Subscribers list, view a summary of Microsoft subscribers at the current hierarchy.
Click on a subscriber in the list to open the Subscribers[subscriber name] page.
Select one of the tabs on the page to view or update settings:

Tab	Description
MS 365	Microsoft user.
MS License	View, add, or delete this subscriber's Microsoft licenses.
MS Teams	The Microsoft subscriber's MS Teams details. The fields below are read-only: User status Interpreted User Type Country or Region Feature Types Line URI Line Type Licenses Summary
Exchange Mailbox	The subscriber's user mailbox settings. You can update the mailbox display name, assign mailbox and calendar permissions to another user. See Microsoft Exchange in the Core Guide for details around managing other Microsoft Exchange mailbox types, such as shared or room mailboxes, or distribution groups.
Local User	The user corresponding with this subscriber.

Save your changes.

Model Details: view/MicrosoftSubscriberQos

An asterisk * in the title indicates the field is mandatory.
If a field has a default value, it is shown in the Description column.
If the field type is an array, the Field Name has a .[n] suffix, where n is the array index placeholder.
Object and array field names are listed to provide context. If a field belongs to an object or an array, the full field name is shown in dot separated notation.

Title															Description																				Details
User Details															Group Assigned by FDP																				Field Name: User Details Type: Object
	Username *																																		Field Name: User Details.username Type: String