.. _ms-teams-policies: Introduction to Microsoft Teams policies ---------------------------------------- .. _21.1|VOSS-847: .. _21.3|VOSS-1072|EKB-12733: .. _21.3|VOSS-1068: .. _24.1|VOSS-1066: .. _24.2|VOSS-1397: .. _24.2|VOSS-1339: .. _24.2-PB2|VOSS-1453: .. _25.2|VOSS-1534: .. tip:: :ref:`use-action-search-to-navigate-automate` Overview ......... Microsoft Teams policies in Automate are synced with Microsoft Teams at the customer level. Automate provides tools to manage these policies at both the customer and site levels. Changes made in Automate are synced to Microsoft Teams, and vice versa. Policies are automatically assigned to users based on: * Their roles and profiles (in the initial sync and provisioning workflow) * Quick Add Groups (QAG) (in the initial sync and provisioning workflow) * Site Defaults settings (view and choose default policies per site on the **MS Teams** tab of the Site Defaults page) Choosing a default policy for a site via the Site Defaults (**MS Teams** tab) automatically assigns the policy to users at the site. When creating a user via Quick User, the setting in the site defaults is used, but you can also edit the configuration template (CFT) for the Quick Add Group to use a policy different to the one selected in the site defaults, or you can edit a user directly to choose a different policy for that user. Managing MS Teams policies ................................ View and manage MS Teams policies via the **Microsoft Detailed Configuration** dashboard in Automate, or use the *Action search* to search for the policy in Automate. * Calling policy * Meeting policy * Messaging policy * Live Events policy * Call park policy * App permission policy * App setup policy * Teams policy * Update policy * Emergency calling policy * Enhanced encryption policy * :ref:`ms-voice-application-policy` * Voice routing policy * Voicemail policy * Audio conferencing policy * :ref:`ms-call-hold-policy` * :ref:`ms-sba-policy` * :ref:`mobility-policy` * :ref:`shared-calling-routing-policy` Some policies support full CRUD (Create, Read, Update, Delete) operations directly in Automate. .. rubric:: Related topics * .. raw:: latex Microsoft Detailed Configuration dashboard .. raw:: html Microsoft Detailed Configuration dashboard * .. raw:: latex Microsoft Users in the Core Feature Guide .. raw:: html Microsoft Users * .. raw:: latex Site Defaults in the Core Feature Guide .. raw:: html Site Defaults * .. raw:: latex Quick Add Groups in the Core Feature Guide .. raw:: html Quick Add Groups .. _shared-calling-routing-policy: Shared calling routing policy .............................. Automate supports full CRUD (create, update, delete) for Microsoft Shared Calling Routing policy. .. note:: This policy is integrated with CsOnlineUser (CSOL) so that management of user details and Shared Calling Routing policies are synced between Automate and the MS Teams portal. 1. At the customer level of the site defaults, on the **MS Teams** tab, select the Shared Calling Routing policy. .. note:: When onboarding the user via Quick Subscriber, the Shared Calling Routing policy selected in the site defaults is the policy assigned to the user. 2. To view, update, or delete existing Shared Calling Routing policies or add new Shared Calling Routing policies, go to **Shared Calling Routing Policy**. The list view displays existing Shared Calling Routing policies. * Select a policy in the list to delete it. * Click on an existing policy to update it. * To add a new Shared Calling Routing policy, click the Plus icon (+), then: * Fill out a name and description * Select a resource account * Add emergency callback numbers, one or more, if required. * Save the new policy. 3. To assign or update the Shared Calling Routing policy for a Microsoft user provisioned with MS Teams, go to **Microsoft User Details**, click on the relevant user to view their settings, then, to assign or update the policy, select the Shared Calling Routing policy for this user. .. _ms-call-hold-policy: Call hold policy (Microsoft Music on Hold) ........................................... To create or update a call hold policy for Microsoft Teams, an audio file (MP3, WAV, and WMA and file size less than 5 MB) upload is required. Go to the **File Management** page for this task. Thereafter, the **Audio file** drop-down list will show the file and can be selected to create or manage the policy. .. note:: * The Call Hold policy name can't be changed upon policy updates. * The audio file names of imported call hold policies are initially undetermined and are represented by a hash value. Subsequent syncs of the policy will resolve existing hash values to filenames. .. rubric:: Related topics * :ref:`troubleshoot-audio-file-errors-in-ms-auto-attendants-and-call-queues` .. _ms-sba-policy: Survivable branch appliance policy .................................. If the Microsoft Teams client is in offline mode, the Teams Phone operations can be made available by a Survivable Branch Appliance (SBA) Policy. This allows for the placement and reception of Public Switched Telephone Network (PSTN) calls during service disruptions. **Survivable Branch Appliance Policy** (SBA Policy) management is available from the **MS Teams Policies** menu. The policy can then be assigned to users, Quick Add Groups and set in Site Defaults. The following policy fields can be managed at a hierarchy: * **Identity**: The identity of the SBA * **Fqdn** The FQDN of the SBA .. _mobility-policy: Mobility policy ................. Microsoft's Teams Phone Mobility policy is assigned to a user that is given a Teams Phone Mobile number via Quick User, or you can assign the policy to an existing user via User Management. This policy tells the system where to route incoming calls, for example, to your mobile phone or to your Teams application. Full CRUD is supported for this policy from within Automate. Changes are synced between Automate and the Microsoft Cloud portal. The Mobility policy is added to Automate via the site defaults, where you can assign a different mobility policy per site, or assign the policy at the customer level. Automate admins onboard and provision Teams Phone Mobile users via Quick User, where the user can be assigned their Teams Phone Mobile license via a license group in a Quick Add Group. The license group can be removed for that user when they're offboarded. The policy is also assigned when updating an existing Microsoft user and choosing a Teams Phone Mobile number to the user. Teams Phone Mobile users are assigned numbers reserved for this functionality in the Automate number inventory. These numbers won't be available to anyone else even if a user with a Teams Phone Mobile number is offboarded. .. rubric:: Add a mobility policy Mobility policies can be added on the MS Teams Cloud portal and synced in to Automate, or you can add a mobility policy from within Automate and sync the policy into the MS Teams Cloud portal. This procedure adds a mobility policy in Automate. 1. In the Automate Admin Portal, go to **Mobility Policy**. Existing mobility policies display in the list view. 2. Click the Plus icon (+) to add a new mobility policy. 3. Fill out an identifying name (**Identity**) and optionally, a description. 4. Optionally, select a mode for IP video and/or IP audio mobile, either WiFi only, or all networks. 5. Optionally, select a mobile dialer preference, either Teams, native, or user override. 6. Save your changes. .. image:: /src/images/ms-mobility-policy.png .. rubric:: Apply the mobility policy to a site or customer 1. Go to **Defaults** (for a site or at the customer level). 2. On the **MS Teams** tab/panel, at **Default Mobility Policy**, select the mobility policy to apply at the site or customer. 3. Save your changes. .. rubric:: Assign a policy to a user Mobility policies can be assigned automatically when onboarding a Microsoft user via Quick User, or you can modify a user and apply a mobility policy. To assign a policy to an existing user, see :ref:`manage-subscriber-policies` .. rubric:: Related topics * :ref:`onboard-user-ms` * :ref:`manage-subscriber-policies` * :ref:`quick-add-subscriber-groups` * :ref:`qas-for-ms-users` .. _ms-voice-application-policy: Voice application policy ........................... Microsoft Voice Application policies define the configuration changes an authorized user can make to the call queues and auto attendants they're authorized for. Automate allows full CRUD (create, update, delete) for the voice application policy from within Automate, and any changes made in either Automate or the Microsoft Teams portal are synced between these two platforms. The voice applications policy can be assigned to a user in Quick User (from the site defaults), or a different voice applications policy can be assigned, via Automate's user management functionality. MS Teams voice policies, including the voice application policy, is available, by default, on the **MVS-MSDialPlan** dashboard. .. image:: /src/images/voice-app-policy-aa-tab.png .. rubric:: Related topics * :ref:`ms-teams-tab` * :ref:`quick-add-subscriber-groups` * :ref:`manage-subscriber-policies` Set up Automate for voice application policies '''''''''''''''''''''''''''''''''''''''''''''''''' To set up Automate for managing Microsoft's Voice Application policies: 1. Add and configure voice applications policies, one or more. 2. On the **MS Teams** tab in the site defaults at the customer level, choose the default voice applications policy to apply. 3. Assign the voice applications policy to a user via Quick User or via Automate's user management functionality. Manage voice application policies in Automate ''''''''''''''''''''''''''''''''''''''''''''''' 1. In the Automate Admin Portal, go to the **Voice Applications Policy** page. 2. View existing voice application policies in the list view. 3. Choose an option: * **Delete a voice application policy**? Select the policy in the list, then click the toolbar **Delete** icon. * **Update a voice application policy**? Click on a policy in the list to view its details. Update the policy, then save. * **Add a new voice application policy**? Click the Plus icon (+) to add a new record. Configure the voice applications policy settings for auto attendants and call queues, then save your changes. * Auto attendant settings for the voice application policy include settings for greetings, time zone, language, holiday and business hours, routing changes, and reporting permissions * Call queue settings for the voice application policy includes settings for greetings, general settings such as whether to allow call queue language, membership, or conference mode changes, as well as settings for exception handling, agent monitoring, and reporting permissions .. image:: /src/images/voice-app-policy-cq-tab.png