Model: view/MicrosoftSubscriberQos

Quick Offboard Subscriber

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

Note

If the Quick Offboard Subscriber configuration template (for target model view/MicrosoftSubscriberQas) includes a Quick Add Group entry associated with the configuration template for the MS Groups Remove Template, referenced MS group licenses associated with the user are also removed. See: Microsoft Licenses

To offboard a user:

Log in to the Admin Portal.
Go to MS Subscriber Management > Quick Offboard Subscriber.
Navigate to the relevant site.
At the Username drop-down, select the relevant user.

Note

This workflow is intended for Microsoft-only users. When choosing a hybrid user with Cisco-Microsoft services, you'll need to work with this user via the Hybrid multi vendor actions. The Hybrid Status Message field displays the user's hybrid status. See Cisco-Microsoft Hybrid Subscribers
Click Save. The user's license is removed.

Subscribers

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

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-4-UC 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.

Onboard Microsoft Users

VOSS-4-UC provides two onboarding options for Microsoft users:

Sync users to customer level, and then to sites

VOSS-4-UC 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.
Add single users via Quick Add Subscriber (QAS)

When moving users to site, the VOSS-4-UC 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-4-UC 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.

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

Offboard a User

This procedure offboards 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.

Related Topics

Microsoft Overview in the Core Feature Guide

VOSS-4-UC Configuration and Sync in the Core Feature Guide

Sync with Flow Through in the Core Feature Guide

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
	Hybrid Status Message		Field Name: User Details.mvs_hybrid_status_message Type: String