.. _ms-subscribers: Microsoft Subscribers ------------------------- .. _21.1|VOSS-847: .. _21.2|VOSS-873: .. _21.3-PB1|VOSS-1072|EKB-12730: .. _21.4|EKB-13371: .. _21.4-PB2|VOSS-1214|EKB-16623: .. _21.4-PB3|EKB-15364: .. _21.4-PB5|VOSS-1313: .. _24.1-PB2|EKB-21258: 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. .. index:: Flowchart;Microsoft Subscribers .. include:: microsoft-user-management.uml .. rubric:: Related Topics * .. raw:: latex Microsoft Overview in the Core Feature Guide .. raw:: html Microsoft Overview * .. raw:: latex Automate Configuration and Sync for Microsoft Services in the Core Feature Guide .. raw:: html Automate Configuration and Sync for Microsoft Services * .. raw:: latex Sync to Site with Flow Through in the Core Feature Guide .. raw:: html Sync to Site with Flow Through * .. raw:: latex Microsoft Exchange in the Core Feature Guide .. raw:: html Microsoft Exchange * :ref:`offboard-user-ms-subscribers` * :ref:`qas-for-ms-users` .. _tasks-onboard-offboard-ms-users: Onboarding Microsoft Users ............................ VOSS Automate provides two onboarding options for Microsoft users: =============================================== ===================================================================================== Sync users to customer level, and then to sites :ref:`VOSS-Automate-configuration-and-sync-for-microsoft` 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 :ref:`sync-to-site-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 :ref:`flow-through-provisioning` View and Edit Microsoft Subscribers .................................... View a summary list of all Microsoft subscribers '''''''''''''''''''''''''''''''''''''''''''''''''''' This procedure displays a summary list of Microsoft subscribers. 1. Log in to the VOSS Automate Admin Portal. #. Choose the hierarchy. #. Use the **Action Search** to go to Microsoft **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 Microsoft subscriber '''''''''''''''''''''''''''''''''''''''''''''''' This procedure displays and edits the details of 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 :ref:`cisco-ms-hybrid-subscribers` 1. Log in to the Automate Admin Portal. #. Choose the hierarchy. #. Use the **Action Search** to go to Microsoft **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 a tab (or scroll to the relevant panel) to view and update settings: .. image:: /src/images/ms-subscribers.png .. 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. .. tabularcolumns:: |p{5cm}|p{10cm}| +----------------------------------+-----------------------------------------------------------------------------------+ | 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 subscriber's form only when Microsoft Exchange is | | | installed and enabled for the subscriber (the subscriber has a Microsoft Exchange | | | license), and provided values are filled out for these fields on the subscriber'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 subscriber'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 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 | | | | | | On this tab you can also enable or disable Enterprise Voice for this user. | | | | | | * You can only enable Enterprise Voice for a user that has a PhoneSystem license. | | | * You can only assign a number to a user that has a PhoneSystem license. | +----------------------------------+-----------------------------------------------------------------------------------+ | Local User | The user corresponding with this subscriber. | +----------------------------------+-----------------------------------------------------------------------------------+ 7. Save your changes. .. rubric:: Related Topics * :ref:`model-filter-criteria` * :ref:`flow-through-provisioning` .. _manage-subscriber-policies: 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 :ref:`cisco-ms-hybrid-subscribers` 1. Go to (default menu) **Subscriber Management > Subscribers**. 2. Click on a subscriber to open the Subscribers [subscriber name] page. 3. Select the **MS Teams** tab. 4. View currently applied policies for the subscriber. 5. To choose different policies, click the down-arrow at the relevant policy, and select an alternative from the drop-down. 6. Save your changes. Policy changes are synced back to the Microsoft cloud when performing an overbuild or a sync. .. image:: /src/images/edit-ms-subscriber-ms-teams.png .. rubric:: Related Topics * :ref:`ms-teams-policies`