.. _qas-for-ms-users:


Quick Subscriber for Microsoft Users
-----------------------------------------

.. _21.3|EKB-11892:
.. _21.3-PB1|EKB-12295:
.. _21.3-PB1|VOSS-1072|EKB-12763:
.. _21.3-PB1|VOSS-1072|EKB-12730:
.. _21.3-PB1|VOSS-1072|EKB-12869:
.. _21.3-PB1|VOSS-1072|EKB-12890:
.. _21.3-PB1|VOSS-1072|EKB-12954:



This procedure displays and updates a Microsoft user, and moves the user 
to the correct site, with all configuration and licensing applied. 
 

.. note:: 
  
   Quick Subscriber simplifies onboarding with the use of Quick Add Groups (QAGs). 
   QAGs are service and policy assignment templates that allow you to 
   pre-configure how calling rights, policies, and services are assigned to users based on their user 
   role. 
   
   When updating a user via Quick Subscriber, you select the relevant QAG, and the automated 
   workflows in VOSS Automate handles the required cloud sync and licensing. The workflow 
   also removes the need for an administrator to check the licensing, or to flag the required 
   policies and settings individually, and then to wait for the cloud to sync in. 


**Prerequisites**:

* Sync in the MS Teams user to the Customer level 
* Set up the site defaults and QAG with the appropriate configuration 
  and licenses.


**Perform these steps**:

1. Log in to the Admin Portal as a Provider admin, at the Customer level.  
#. Go to (default menu) **MS Subscriber Management > Quick Subscriber**. 
#. Choose the relevant site. 
#. On the Quick Subscriber page: 

   * Required. In the **Username** field, select the user to populate fields on the page. 
   * To include users higher in the hierarchy in the **Username** drop-down, select **Include users at higher hierarchy**.  
   * To send a subscriber a welcome email once they're set up, select **Send welcome email**. 
   
     .. note:: 
        
        * You must have a SMTP server set up to send emails. 
        * The read-only **User status** field displays the user's current status; that is, whether they are 
          online, in staging, or not yet provisioned. 
        * The value in the read-only **Feature type** field defines whether this Microsoft 
          user has MS Teams with or without the voice service. The user has MS Teams and 
          voice service when feature type displays both `Teams` and `PhoneSystem` 
     
   * Required. From the **Quick Add Group** drop-down, select the relevant Quick Add Group (QAG) 
     (licenses the user and applies settings defined in the QAG). 
   * From the **Line URI** drop-down, choose a number; alternatively, select **Use next available line** to 
     automatically populate the **Line URI** field with the next available line. 

     .. note:: 

        * The **Line URI** and **Use next available line** fields display *only* when 
          **Feature Type** is `PhoneSystem`, or **Manage Licenses and Allow User Staging** is 
          enabled (via the **MS Teams** tab in the site default docs). 

        * The **Enterprise Voice Enabled** option has been deprecated since PowerShell V4.0.0.
          Setting **Enterprise Voice Enabled** is no longer required. To enable a user for Voice,
          ensure the user has a **Line URI** set and that the **Feature Type** shown contains
          ``Teams, PhoneSystem``.

        * The **Line URI** drop-down displays available lines (staged lines are excluded), 
          with the vendor and line type shown in brackets, for example, `Microsoft - CallingPlan`. 
          Lines types may be: Direct Routing, Calling Plan, or Operator Connect
        * When choosing a line, the INI will eventually update to this number. 
        * The default for **Use next available line** is False (disabled). 
          
          When selecting **Use next available line**: 
        
          * If the user does not already have a line, they are assigned the next available line. 
          * If the user has an existing line, this line is replaced by the next available line. 
          * Staged numbers are considered unavailable and will not be used. 

   * Optionally, from the **Tenant dial plan** field, choose a tenant dial plan.

     .. note:: 

        Choosing a tenant dial plan different from the default set up in the site defaults (SDD) overwrites the default. 
        If you don't choose an option for this field, the tenant dial plan set up 
        in the SDD applies.
      
   * From **Calling Line Identity**, assign a calling line identity for this user, or use the value 
     that comes from the QAG. 
   * Click **Save**. 

#. Go to **MS Subscriber Management > Subscriber Staging** to view the user in the staging queue. 
     
   .. note:: 
      
      The user is placed in the staging queue (with all configuration applied) while waiting for the 
      cloud to sync in. Once the licensed user appears in the Microsoft Teams portal, 
      a second, targeted sync is triggered, which searches only for staged users 
      (not all users from the tenant). Once the sync completes, the user becomes a fully provisioned subscriber, and the 
      number is flagged as used. The subscriber receives a welcome email 
      (if you've chosen this option, and you have a SMTP server configured). 

      Users can only be staged if the following setting in the site defaults is enabled (accessed via, default 
      menus, **Site Management > Defaults**, on the **MS Teams** tab): `Manage Licenses and Allow User Staging` 

      Starting with VOSS Automate v21.3-PB1, you can, with immediate effect, un-stage a user waiting in the 
      staging queue. This executes a direct sync to the Microsoft cloud to determine whether the user has 
      appeared in MS Teams after their licensing update.

#. Verify that the subscriber is configured and licensed: 

   * Go to (default menu) **Subscriber Management > Subscribers**. 
     
     .. note:: 
        The **Located At** column on the Subscriber list displays the hierarchy location of 
        each subscriber added to the system, for example, customer or site. 

   * Click on the subscriber to open the Subscribers[name] page.  

   * On the **MS Licenses** tab, view the subscriber's license details. 
   * On the **MS Teams** tab, verify the following:
   
     * The user's number is allocated
     * Policies are assigned



.. rubric:: Related Topics 

*
  .. raw:: latex

     Microsoft Subscribers in the Core Feature Guide

  .. raw:: html

     <a href="ms-subscribers.html">Microsoft Subscribers</a>

*
  .. raw:: latex

     Microsoft User Move Configuration in the Core Feature Guide

  .. raw:: html

     <a href="concepts-user-move-for-microsoft.html">Microsoft User Move Configuration</a> 

*
  .. raw:: latex

     Flow Through Provisioning in the Core Feature Guide

  .. raw:: html

     <a href="flow-through-provisioning.html">Flow Through Provisioning</a> 

*
  .. raw:: latex

     Subscriber Staging (Microsoft Users) in the Core Feature Guide

  .. raw:: html

     <a href="ms-subscriber-staging.html">Subscriber Staging (Microsoft Users)</a> 

*
  .. raw:: latex

     Microsoft Licenses in the Core Feature Guide

  .. raw:: html

     <a href="concepts-ms-licenses.html">Microsoft Licenses</a>