Introduction to Microsoft Teams Policies#

Overview#

Microsoft Teams policies are synced between Microsoft Teams and VOSS Automate, to the customer level.

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

You can view and choose default policies for sites in the site defaults via (default menus) Site Management > Defaults (and select the MS Teams tab).

Microsoft Teams policies are assigned automatically to subscribers via their user roles and profiles, and via quick add groups (QAG), as part of the initial sync and provisioning workflow.

Choosing a default policy for a site in the Site Defaults (SDD) automatically assigns the policy to subscribers at the site. When creating a subscriber via Quick Subscriber, the SDD is used, but you can also edit the configuration template for the Quick Add Group (QAG) to use a policy different to the SDD, or you can edit a subscriber directly to choose a different policy for that subscriber.

Policies are then also shown on for example the Teams User (CSOL) menu.

To manage Microsoft Teams policies, go to (default menu) MS Teams Policies; then, select the relevant menu, 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 Routing Policy

  • Voicemail Policy

  • Audio Conferencing Policy

  • Call Hold Policy

  • Survivable Branch Appliance Policy

  • Mobility Policy

Note

  • Some policies support full CRUD (create, update, delete) operations within VOSS Automate.

Related Topics

Call Hold Policy (Microsoft Music on Hold)#

To create or update a Call Hold Policy from the MS Teams Policies menu, an audio file (MP3, WAV, and WMA and file size less than 5 MB) upload is required. Use the File Management menu for this task.

Thereafter, the Audio file dropdown list will show the file and can be selected to create or manage the policy.

Note

  • The Call Hold Policy Name cannot 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.

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 Subscriber, or you can assign the policy to an existing subscriber via Subscriber 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 Subscriber, 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 subscriber and choosing a Teams Phone Mobile number to the subscriber.

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.

../../_images/ms-mobility-policy.png

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 subscriber

Mobility policies can be assigned automatically when onboarding a Microsoft user via Quick Subscriber, or you can modify a subscriber and apply a mobility policy. To assign a policy to an existing subscriber, see Manage a Subscriber’s MS Teams Policies

Related Topics