[Index]
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 the release documentation at: https://documentation.voss-solutions.com/automate.html
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:
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:
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
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:
View and update a single Microsoft subscriber
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
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:
On this tab you can also enable or disable Enterprise Voice for this user.
|
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. |
Manage a Subscriber's MS Teams Policies
This procedure displays and updates the policies of individual subscribers via the Subscriber edit functionality:
Note
Some policies support full CRUD (create, update, delete) operations within VOSS Automate.
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
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:
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:
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.
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
Microsoft Subscriber Relation
Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
MS 365 | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Display Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
First Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Last Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
User Principal Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Title |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Phone Number |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Mobile Phone |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Usage Location | Country code, eg. US |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Department |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Office |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Street Address |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Postal Code |
|
||||||||||||||||||||||||||||||||||||||||||||||||
City |
|
||||||||||||||||||||||||||||||||||||||||||||||||
State |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Country |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Groups | List of groups a user belongs to in Microsoft |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Guicontrol |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Groups | List of groups a user belongs to in Microsoft |
|
|||||||||||||||||||||||||||||||||||||||||||||||
MS Licenses | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
License type | User License type (Group or Direct) |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Guicontrol |
|
||||||||||||||||||||||||||||||||||||||||||||||||
License type | User License type (Group or Direct) |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Licenses |
|
||||||||||||||||||||||||||||||||||||||||||||||||
SKU Part Number |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Service Plans |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Service Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enabled |
|
||||||||||||||||||||||||||||||||||||||||||||||||
MS Teams | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
User status | Status shows whether the user is licensed and provisioned for Teams, pending provisioning (in the event that the user is in staging and waiting for the MS cloud to sync in the User's Teams account) or only as a MS 365 User |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Guicontrol |
|
||||||||||||||||||||||||||||||||||||||||||||||||
User status | Status shows whether the user is licensed and provisioned for Teams, pending provisioning (in the event that the user is in staging and waiting for the MS cloud to sync in the User's Teams account) or only as a MS 365 User |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Enterprise Voice Enabled |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Ms Teams |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enterprise Voice Enabled |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Feature Types | MS Teams Feature Types |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Account Enabled | Account Enabled |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Is SIP Enabled | Is SIP Enabled |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Line URI |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Line Type |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Line URI TEL portion | The tel value of the caller ID field is shown here, and is selectable from a drop-down list of available Internal numbers |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Line URI EXT portion | If an ext value exists in the caller ID field, it will be shown here for information purposes |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Dial Plan | A dial plan is a set of rules that translate a phone number that a user dials into a standard E.164 number for call authorization and routing |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Meeting Policy | Meeting policies in Microsoft Teams are used to control the features that are available to meeting participants for meetings that are scheduled by users in your organization |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Messaging Policy | Messaging policies are used to control which chat and channel messaging features are available to users (owners and members) in Microsoft Teams |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Live Events Policy | Live events policies are used to control who in your organization can hold live events and the features that are available in the events they create |
|
|||||||||||||||||||||||||||||||||||||||||||||||
App Permission Policy | App permission policies control what apps you want to make available to Teams users in your organization |
|
|||||||||||||||||||||||||||||||||||||||||||||||
App Setup Policy | App setup policies control how apps are made available to a user with the Teams app |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Call Park Policy | Call park lets people put a call on hold and transfer it to other people within your organization. Call park policies let you control which users are call park enabled and make other call park setting changes for them |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Calling Policy | Calling policies control which calling and call forwarding features are available to users. Calling policies determine whether a user can make private calls, use call forwarding or simultaneous ringing to other users or external phone numbers, route calls to voicemail, send calls to call groups, use delegation for inbound and outbound calls, and so on. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Caller ID Policy | Caller ID policies are used to change or block the Caller ID (also called a Calling Line ID) for users. By default, the user's phone number is displayed when a call is made to a PSTN phone number such as a landline or mobile phone |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Teams Policy | Teams policies are used to control what settings or features are available to users when they are using teams and channels |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Update Policy | Update policies are used to manage Teams and Office preview users that will see pre-release or preview features in the Teams app |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Emergency Calling Policy | Emergency calling policies are used to control how users in your organization can use dynamic emergency calling features. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Emergency Call Routing Policy | Emergency call routing policies are used to set up emergency numbers for Direct Routing and then specify how those emergency calls are routed |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Enhanced Encryption Policy | Enhanced encryption policies are used to control if users in your organization can use enhanced encryption settings in Teams |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Voice Routing Policy | A voice routing policy for Direct Routing will be linked to a voice route using PSTN usage records. You can add existing PSTN usage records, change the order in which the usages will be processed, and assign the voice routing policy to users |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Voicemail Policy | Voicemail policies control the available features for the voicemail service in Teams |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Templates Policy | Teams templates policies let you create and set up policies that control what templates people in your organization can see |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Audio Conferencing Policy | Audio Conferencing policies control phone numbers and features available to users with audio conferencing |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Interpreted User Type | Internal diagnostic property |
|
|||||||||||||||||||||||||||||||||||||||||||||||
City |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Country |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Feature Types | MS Teams Feature Types |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Account Enabled | Account Enabled |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Is SIP Enabled | Is SIP Enabled |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Line URI |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Line Type |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Line URI TEL portion | The tel value of the caller ID field is shown here, and is selectable from a drop-down list of available Internal numbers |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Line URI EXT portion | If an ext value exists in the caller ID field, it will be shown here for information purposes |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Dial Plan | A dial plan is a set of rules that translate a phone number that a user dials into a standard E.164 number for call authorization and routing |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Meeting Policy | Meeting policies in Microsoft Teams are used to control the features that are available to meeting participants for meetings that are scheduled by users in your organization |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Messaging Policy | Messaging policies are used to control which chat and channel messaging features are available to users (owners and members) in Microsoft Teams |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Live Events Policy | Live events policies are used to control who in your organization can hold live events and the features that are available in the events they create |
|
|||||||||||||||||||||||||||||||||||||||||||||||
App Permission Policy | App permission policies control what apps you want to make available to Teams users in your organization |
|
|||||||||||||||||||||||||||||||||||||||||||||||
App Setup Policy | App setup policies control how apps are made available to a user with the Teams app |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Call Park Policy | Call park lets people put a call on hold and transfer it to other people within your organization. Call park policies let you control which users are call park enabled and make other call park setting changes for them |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Calling Policy | Calling policies control which calling and call forwarding features are available to users. Calling policies determine whether a user can make private calls, use call forwarding or simultaneous ringing to other users or external phone numbers, route calls to voicemail, send calls to call groups, use delegation for inbound and outbound calls, and so on. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Caller ID Policy | Caller ID policies are used to change or block the Caller ID (also called a Calling Line ID) for users. By default, the user's phone number is displayed when a call is made to a PSTN phone number such as a landline or mobile phone |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Teams Policy | Teams policies are used to control what settings or features are available to users when they are using teams and channels |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Update Policy | Update policies are used to manage Teams and Office preview users that will see pre-release or preview features in the Teams app |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Emergency Calling Policy | Emergency calling policies are used to control how users in your organization can use dynamic emergency calling features. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Emergency Call Routing Policy | Emergency call routing policies are used to set up emergency numbers for Direct Routing and then specify how those emergency calls are routed |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Enhanced Encryption Policy | Enhanced encryption policies are used to control if users in your organization can use enhanced encryption settings in Teams |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Voice Routing Policy | A voice routing policy for Direct Routing will be linked to a voice route using PSTN usage records. You can add existing PSTN usage records, change the order in which the usages will be processed, and assign the voice routing policy to users |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Voicemail Policy | Voicemail policies control the available features for the voicemail service in Teams |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Templates Policy | Teams templates policies let you create and set up policies that control what templates people in your organization can see |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Audio Conferencing Policy | Audio Conferencing policies control phone numbers and features available to users with audio conferencing |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Interpreted User Type | Internal diagnostic property |
|
|||||||||||||||||||||||||||||||||||||||||||||||
City |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Country |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Exchange Mailbox | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Display Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
User Mailbox |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Display Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Permissions | Please note that any update in MS Exchange can take up to 5 minutes to be reflected. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
User |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Access Rights |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Calendar Permissions | Please note that any update in MS Exchange can take up to 5 minutes to be reflected. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
User |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Access Rights |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Permissions | Please note that any update in MS Exchange can take up to 5 minutes to be reflected. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
User |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Access Rights |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Calendar Permissions | Please note that any update in MS Exchange can take up to 5 minutes to be reflected. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
User |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Access Rights |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Local User | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
User Name * | User's Username. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
User |
|
||||||||||||||||||||||||||||||||||||||||||||||||
User Name * | User's Username. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
First Name | The User first name. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Last Name | The User last name. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Title | Title. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Email Address | The User email address. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
First Name | The User first name. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Last Name | The User last name. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Title | Title. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Email Address | The User email address. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Hybrid Status Message |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Guicontrol |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Hybrid Status Message |
|