[Index]

Model: device/msteamsonline/CsTeamsMessagingPolicy

MS Teams Policies

Full HTML Help

Overview

Microsoft Teams policies are synced between Microsoft Teams and the customer level in Automate.

Automate provides an interface for managing Microsoft Teams policies at customer or site level. Updates in Automate are synced back to Microsoft Teams, and external changes are synced back to Automate.

Microsoft Teams policies are assigned automatically to users via their user roles and profiles, and via Quick Add Groups (QAG), as part of the initial sync and provisioning workflow.

You can view and choose default policies for sites on the MS Teams tab of the Site Defaults page.

Choosing a default policy for a site via the Site Defaults 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 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.

Policies also display on, for example, the Teams User (CSOL) page.

To manage Microsoft Teams policies, go to the page for the relevant policy, for example:

• 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
• Voice application policy
• Voice routing policy
• Voicemail policy
• Audio conferencing policy
• Call hold policy
• Survivable branch appliance policy
• Mobility Policy
• Shared Calling Routing Policy

Related topics

Microsoft Users in the Core Feature Guide

Site Defaults in the Core Feature Guide

Quick Add Groups in the Core Feature Guide

Shared calling routing policy

Automate supports full CRUD (create, update, delete) for Microsoft Shared Calling Routing policy.

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.

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.

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

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.

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.

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.

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 Manage a Subscriber's MS Teams Policies

Related topics

• Onboard user (Microsoft)
• Manage a Subscriber's MS Teams Policies
• Quick Add Groups
• Microsoft Quick User

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.

Related topics

• MS Teams Defaults Tab
• Quick Add Groups
• Manage a Subscriber's MS Teams Policies

Model Details: device/msteamsonline/CsTeamsMessagingPolicy