.. _qas-for-ms-users: Microsoft Quick User ------------------------ .. _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: .. _21.4|EKB-13371: .. _21.4-PB2|VOSS-1214: .. _21.4-PB3|EKB-15364: .. _21.4-PB3|EKB-17035: .. _21.4-PB4|EKB-16760: .. _24.2-PB1|EKB-22376: .. _24.2-PB2|VOSS-1493: .. _25.1|VOSS-1210: .. _25.3|EKB-26436: .. _25.4|EKB-27416: .. _25.4|EKB-27489: .. tip:: :ref:`use-action-search-to-navigate-automate` .. Model Details: view/MicrosoftSubscriberQas Overview .......... Microsoft Quick User simplifies onboarding and updates for Microsoft Teams users by applying predefined services, policies, and licenses based on Quick Add Groups (QAGs). The workflow automatically handles configuration, licensing, and synchronization with Microsoft Teams, reducing the need for manual intervention. This workflow can be used to create or update Microsoft users, move users to the correct site, assign licenses and policies, and optionally assign a calling line for voice-enabled users. Before you begin ................... The Microsoft Quick User workflow applies specific behavior and constraints that affect how users, licenses, and numbers are provisioned. Review the following information to avoid unexpected behavior during licensing and provisioning. * **User type limitations**: This workflow is intended for Microsoft-only users. Hybrid Cisco-Microsoft users must be managed using the Hybrid multi-vendor actions. The user's hybrid status is displayed in the **Hybrid Status Message** field. For more information, see :ref:`cisco-ms-hybrid-subscribers` * **Licensing and staging behavior**: If an existing Microsoft user already holds a license and you assign a Quick Add Group that adds additional services (for example, upgrading from IM-only to Voice services), the user's license is updated during onboarding. Depending on tenant configuration, the user is either placed in the staging queue until the license update syncs and provisioning completes, or provisioned immediately without staging. The Microsoft Teams tenant staging sync is disabled by default. You can enable and schedule this sync if staged provisioning is required. * **Automatic line assignment behavior**: * When using **Use next available line** with Microsoft Quick User, automatic line assignment applies only to Internal Number Inventory (INI) entries where the Vendor is set to Microsoft only. * Numbers configured with a multi-vendor value (for example, Cisco,Microsoft) are excluded from automatic assignment. This behavior applies whether or not a line filter is used. * When choosing a line, the INI will eventually update to this number. * By default, **Use next available line** is disabled. When enabled, the system prioritizes local numbers, numbers available at the current site, before checking for available numbers from higher levels in the hierarchy. Additionally, * When used with a filter, the system selects the first available line returned from the filter. * A user without a line is 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 won't be used. * Reserved numbers are excluded (numbers reserved for the user you're working with and numbers reserved for other users). See :ref:`ini-reserve-for` * **Line selection behavior**: The **Line URI** drop-down displays available numbers only. Staged numbers and numbers reserved for other users are excluded. Each line displays its vendor and line type, for example, **Microsoft - CallingPlan**. Lines types may be: Direct Routing, Calling Plan, or Operator Connect * **Email notifications**: To send welcome emails during onboarding, an SMTP server must be configured in VOSS. * **Enterprise Voice configuration**: The **Enterprise Voice Enabled** option is deprecated (since PowerShell V4.0.0) and no longer required. To enable voice services for a licensed user, assign a line and ensure that the **Feature Type** is set to ``Teams, PhoneSystem``, or use a Quick Add Group that enables voice services. To disable or re-enable Enterprise Voice later, update the user's account settings (``relation/MicrosoftSubscriber``). See :ref:`ms-subscribers` Add or update a Microsoft user using Quick User ................................................ This procedure displays and updates a Microsoft user, and moves the user to the correct site, with all configuration and licensing applied. **Prerequisites**: Before starting this workflow: * Sync the Microsoft Teams user to the customer level. * Configure site defaults and Quick Add Groups with the required licenses and settings. **Perform these steps**: 1. Log in to the Admin Portal as a Provider admin, at the customer level. #. Go to **Microsoft Quick User**. #. Choose the relevant site. #. On the **Microsoft Quick User** page: * Mandatory. At **Username**, select the user to populate fields on the page. * Optional. Select **Include users at higher hierarchy** to include users higher in the hierarchy in the **Username** drop-down. * Optional. Select **Send welcome email** to send a user a welcome email once they're set up. When a welcome email is sent during the Microsoft Quick User process, the user's email address is included in the final transaction message. .. note:: * 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` * Mandatory. At **Quick Add Group**, select the relevant Quick Add Group (QAG), which is to license the user and apply settings defined in the QAG. Available QAGs in the list are filtered by vendor (see :ref:`quick-add-subscriber-vendor-filtering`), and are restricted to those available at a selected hierarchy, based on the option selected for **Quick Add Group & User Profile lookup level** in the General Settings of the Global Settings. See :ref:`global-settings`. Quick Add Groups support group licensing for MS 365 groups, so that users can be licensed according to group membership. Refer to: * *Microsoft Licenses* in the Core Feature Guide * :ref:`quick-add-subscriber-groups` .. note:: * If **Enable Microsoft User License Enforcement** has been 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* in the Core Feature Guide. * If **Tenant dial plan**, **Calling line identity** and **Online voice routing policy** values are set, these will be used. * At **Line URI**, select a number; alternatively, select **Use next available line** to automatically populate the **Line URI** field with the next available line. If filtering is enabled at the current hierarchy, you can select a line filter. See :ref:`manage-number-filters`. See **Automatic line assignment behavior** above for vendor eligibility rules. .. note:: The **Line URI** and **Use next available line** fields display *only* when **Feature Type** is `PhoneSystem`, or **Manage Licenses** is enabled (via the **MS Teams** tab in the site default docs). * If a **Quick Add Group** is selected and related values are set, the **Tenant dial plan**, **Calling line identity** and **Online voice routing policy** fields, will take those values, else values from the site defaults (SDD). Choosing different values will overwrite QAG or site defaults (SDD) values. * From **Calling Line Identity**, assign a calling line identity for this user, or use the value that comes from the QAG. * Click **Save**. #. Verify: * Go to **User Staging** to verify the user is in the staging queue, and note the following: * 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 (if the schedule is enabled), which searches only for staged users (not all users from the tenant). * Once the sync completes, the user becomes fully provisioned and the number is flagged as used. * The user receives a welcome email (if you've chosen this option and you have a SMTP server configured). You may also immediately 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. * Check that the user is configured and licensed: * Go to the **Users** list view. The **Located At** column on the Users list displays the hierarchy location of each user added to the system, for example, customer or site. * Click on the user to view their settings. * On the **MS Licenses** tab, view the user's license details. * On the **MS Teams** tab, ensure that: * The user's number is allocated * Policies are assigned .. rubric:: Related topics * .. raw:: latex Microsoft users in the Core Feature Guide .. raw:: html Microsoft Users * .. raw:: latex Sync to customer then to site in the Core Feature Guide .. raw:: html Sync to customer then to site * .. raw:: latex Flow through provisioning in the Core Feature Guide .. raw:: html Flow through provisioning * .. raw:: latex User staging in the Core Feature Guide .. raw:: html User staging * *Microsoft licenses* in the Core Feature Guide * :ref:`user-voicemail-settings-ms-subscriber` * :ref:`ini-reserve-for` * *Introduction to Microsoft Teams policies* in the Core Feature Guide * :ref:`manage-number-filters`