[Index]
Tip
Use the Action search to navigate Automate
Overview
Microsoft users must be onboarded in VOSS before they can be fully provisioned and managed. Onboarding involves importing users and related data from the Microsoft Cloud, placing users in the correct customer and site hierarchies, and applying configuration, policies, and licenses through automated workflows.
Once users are synced at the customer or site level, administrators can manage Microsoft users centrally from the VOSS UI. Targeted backend synchronizations continuously poll for changes at the device model layer to:
Note
License management for Microsoft users is available only when Enable Microsoft User License Enforcement is set to True (Yes) in Global Settings (User settings). When enabled, users can be added only if sufficient license allocation exists for their hierarchy.
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
Configuration and Sync for Microsoft Services in the Core Feature Guide
Sync to Site with Flow Through in the Core Feature Guide
Microsoft Exchange in the Core Feature Guide
View and edit Microsoft users
This procedure displays a list of Microsoft users at the selected hierarchy.
Log in to the VOSS Admin Portal.
Choose the hierarchy.
Go to the Microsoft User Details page.
View a summary of Microsoft users at the current hierarchy.
The list view shows the following details for each user:
From the list view you can click on a user to open their settings, or select one or more users to apply bulk actions via the toolbar icons (filter, refresh, export, or move).
Related topics
This procedure displays and edits details for an individual Microsoft user.
Note
This workflow applies to Microsoft-only users. For Cisco-Microsoft hybrid users, use the hybrid multi vendor actions. The Hybrid Status Message field displays the user's hybrid state. See Cisco-Microsoft Hybrid Users
Log in to the VOSS Admin Portal.
Select the required hierarchy.
Go to the Microsoft User Details.
Click on a user in the list to open their settings.
Select a tab (or panel) to view and update settings:
Note
VOSS supports either a tab or panel layout via a toolbar button. The tabs/panels that display depend on enabled functionality.
Related topics
This section describes Microsoft user settings available via Microsoft User Details:
MS 365: Microsoft user attributes such as display name, first and last name, User Principal Name (UPN), title, contact details, usage location, department, employee ID, employee type, groups, and Microsoft Entra account enabled status.
Exchange Custom Attributes: Read-only. Available only when Microsoft Exchange is enabled and licensed for the user. These fifteen attributes can be used for:
MS Licenses: View and update the Microsoft license assignments for the user.
Note
When the license type is "Group", all license details (SKU and service plans) are read-only.
MS Teams: Displays Microsoft Teams configuration. The following fields are read-only:
Enterprise Voice can be enabled or disabled only if the user has a PhoneSystem license. Numbers can be assigned only when the PhoneSystem licenses is present.
Local User: The local VOSS user associated with the Microsoft user.
Related Topics
Microsoft Exchange in the Core Feature Guide
The read-only AccountEnabled attribute indicates whether a Microsoft Entra ID (Azure AD) user account is enabled. This value is synced from Microsoft and cannot be modified in VOSS.
VOSS uses this attribute to determine whether a user should be included in analytics reporting, and license optimization workflows:
Migration behavior
To avoid excessive resynchronization and performance impact during upgrades, AccountEnabled defaults to True during migration. After synchronization completes:
Manage a user's MS Teams policies
This procedure updates Microsoft Teams policies assigned to an individual user.
Note
Some policies support full CRUD (create, update, delete) operations in VOSS. This workflow applies to Microsoft-only users.
Policy updates are synced back to Microsoft during an overbuild or synchronization.
Related topics
Licensing for Microsoft users
This section describes how licensing is applied, enforced, and managed for Microsoft users in VOSS
VOSS supports assigning, modifying, and removing Microsoft licenses for users as part of onboarding, offboarding, and ongoing user management.
To enable license management:
When license management is enabled:
Important
VOSS requires the LicenseAssignment permission to manage Microsoft licenses.
This behavior applies across onboarding, updates, and offboarding workflows.
Licensing by group membership can be configured:
VOSS provides reference configuration templates:
Best practice is to use separate Quick Add Groups for onboarding and offboarding to avoid overlapping add/remove behavior.
Related topics
Configuration Templates (Core Feature Guide)
VOSS provides reference configuration templates that control Microsoft group membership during onboarding, offboarding, and flow through provisioning. These templates can be cloned to a hierarchy, renamed, and modified to customize the group membership changes applied by an operation.
The templates are available on the Configuration Templates page. The menu and model associated with the configuration templates is view/MsGraphManageGroup.
The following reference templates are provided:
Group names must be entered manually. Available groups can be inspected via the Groups page. If Microsoft licenses are associated with a group, they are applied or removed according to the configuration template Operation setting.
For cloned templates, the User and Operation values do not need to be modified if the original template behavior is to be preserved.
Important
Do not select both Add and Remove configuration templates containing the same group list when creating a Quick Add Group. Doing so results in the same group being added and removed in a single operation.
Best practice is to define separate Quick Add Groups for onboarding and offboarding, each containing only the required configuration templates.
In scenarios where a fixed set of groups must be enforced for both onboarding and offboarding, templates can be combined deliberately to achieve the desired outcome.
These configuration templates can be applied to Quick Add Groups for use in on-boarding, off-boarding, and flow-through provisioning workflows.
Related topics
Configuration Templates (Core Feature Guide)
To view a user's licensing details:
Related topics
| Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| User Details | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| User Principal Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Title |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| First Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Last Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Display Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Company Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Classification |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| User Type |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Account Enabled | Default: True |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Department |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Employee Id |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Employee Type |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Proxy Addresses |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Primary Smtp Address |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Phone Number |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Mobile Phone |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Office |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Street Address |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| City |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| State |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Postal Code |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Country |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Usage Location | Country code, eg. US |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Licenses Summary |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| On Premises Extension Attributes | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Extension Attribute 1 | Extension Attribute 1 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Extension Attribute 2 | Extension Attribute 2 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Extension Attribute 3 | Extension Attribute 3 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Extension Attribute 4 | Extension Attribute 4 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Extension Attribute 5 | Extension Attribute 5 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Extension Attribute 6 | Extension Attribute 6 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Extension Attribute 7 | Extension Attribute 7 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Extension Attribute 8 | Extension Attribute 8 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Extension Attribute 9 | Extension Attribute 9 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Extension Attribute 10 | Extension Attribute 10 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Extension Attribute 11 | Extension Attribute 11 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Extension Attribute 12 | Extension Attribute 12 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Extension Attribute 13 | Extension Attribute 13 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Extension Attribute 14 | Extension Attribute 14 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Extension Attribute 15 | Extension Attribute 15 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Licenses | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Is Licensed |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Licenses |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| License | License Name (SKU Part Name) |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| SKU Part Number |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Service Plans |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Service Plan | Service Plan Name |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Service Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Enabled |
|
||||||||||||||||||||||||||||||||||||||||||||||||