[Index]
Tip
Use the Action search to navigate Automate
Overview
You will need to onboard Microsoft users in 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 users.
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 via a single interface and login, from within the 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.
Note
If Enable Microsoft User License Enforcement is set to Yes in the Global Settings, a user can only be added if the license allocation limit for the user's hierarchy is not exceeded. For details, see: Microsoft license management and alerting.
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
Automate 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 summary list of Microsoft users.
Log in to the Automate 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 for Microsoft users provides details for the following, for each user in the list:
This procedure displays and edits the details of a single Microsoft 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 Users
Log in to the Automate Admin Portal.
Choose the hierarchy.
Go to the Microsoft User Details page.
View a summary of Microsoft users at the current hierarchy.
Click on a user in the list to open their settings.
Select a tab (or scroll to the relevant panel) to view and update settings:
Note
Automate allows you to toggle between a panel or tab layout via a toolbar button. The tabs/panels that display depend on enabled functionality.
| Tab/Panel | Description |
|---|---|
| MS 365 | Microsoft user details, such as their display name, first and last name, User Principal Name (UPN), title, contact details, usage location, department, employee ID, employee type, and groups. |
| Exchange Custom Attributes | Read-only. Displays on the user's form only when Microsoft Exchange is installed and enabled for the user (the user has a Microsoft Exchange license), and provided values are filled out for these fields on the user's Microsoft Exchange settings in Automate. These are fifteen additional fields that can be used for filtering from Microsoft Entra ID using model filter criteria, and to have the values available for flow through provisioning. The same fields are also available in the Microsoft Exchange settings (when installed) in Automate. The fields allow more flexibility when filtering users to be imported and then moved and, optionally, processed with flow through provisioning in Automate. |
| MS Licenses | View and update the user's Microsoft license details, including their type (Group or Direct), and their licenses. Note When the license type is "Group", all license details (SKU and service plans) read-only. |
| MS Teams | The Microsoft user's MS Teams details. The fields below are read-only:
On this tab you can also enable or disable Enterprise Voice for this user.
|
| Local User | The user corresponding with this user. |
Related Topics
Manage a user's MS Teams policies
This procedure displays and updates the policies of individual users via the user edit functionality:
Note
Some policies support full CRUD (create, update, delete) operations within 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 Users
Related topics
| Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| User Details | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| User Principal Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Title |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| First Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Last Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Display Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Company Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| User Type |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| 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 |
|
||||||||||||||||||||||||||||||||||||||||||||||||