[Index]

Model: relation/MicrosoftSubscriber

Microsoft Subscribers

Full HTML Help

Overview

You will need to onboard Microsoft users to create Microsoft subscribers in VOSS Automate.

Onboarding a Microsoft user involves importing users and related data to the customer level from the Microsoft Cloud service, and then moving users to the correct sites as fully provisioned subscribers.

Automated workflows configure imported objects once changes are synced in, and apply the required configuration, policies, and licenses. This means administrators won't need to continually monitor the sync, or to perform additional steps to complete the process.

Once synced in (at the customer or site level), administrators can manage Microsoft users and subscribers via a single interface and login, from within the VOSS Automate Admin Portal. To maintain data integrity, to manage licenses, and to automate number auditing for synced in users, regular, targeted backend syncs poll for changes made at the device model layer.

To access the flowcharts, view the topic via the release documentation at: https://documentation.voss-solutions.com/automate.html

Related Topics

Microsoft Overview in the Core Feature Guide

Automate Configuration and Sync for Microsoft Services in the Core Feature Guide

Sync with Flow Through in the Core Feature Guide

Microsoft Exchange in the Core Feature Guide

Onboarding Microsoft Users

VOSS Automate provides two onboarding options for Microsoft users:

Sync users to customer level, and then to sites

VOSS Automate Configuration and Sync

This option starts with an initial import of dial plans, policies, licenses, and Microsoft users, to the customer level (sync all to the tenant).

Then you will need to set up the configuration and user move criteria before moving users to the sites (set up model filter criteria, site defaults, quick add groups, subscriber profiles, and number inventory).

Finally, you have two options to move users to the sites as fully provisioned subscribers:

  • Run the overbuild to move multiple users to your sites at once.
  • Update single users via Quick Subscriber (for Microsoft users)

When moving users to site, the VOSS Automate automated workflow applies the required configuration, services, lines, policies, and licenses.
Sync users directly to sites

Sync with Flow Through

In this option, you run the initial sync together with flow through provisioning. In this case, you start by setting up the configuration and user move criteria before running the initial sync. That is, to set up the model filter criteria, site defaults, quick add groups, and subscriber profiles.

In addition, you will need to:

  • Configure flow through provisioning criteria
  • Enable flow through in the Global Settings

Once changes are synced in from the Microsoft Cloud, VOSS Automate automated workflows move the tenant dial plan, policies, and licenses to the customer level, and moves users directly to the appropriate sites as fully provisioned subscribers.

Note

View and Edit Microsoft Subscribers

View a summary list of all Microsoft subscribers

This procedure displays a summary list of Microsoft subscribers.

  1. Log in to the VOSS Automate Admin Portal.

  2. Choose the hierarchy.

  3. Go to (default menus) Microsoft Subscriber Management > Subscribers.

  4. On the Subscribers list, view a summary of Microsoft subscribers at the current hierarchy.

    The Subscribers summary list view for Microsoft users provides details for the following, for each subscriber in the list:

    • User principal name, first name, and last name
    • Licenses
    • Department
    • City, country, phone number, location
    • Associated device

View and update a Microsoft subscriber

This procedure displays and edits the details of a single Microsoft subscriber.

Note

This workflow is intended for Microsoft-only users. When choosing a hybrid user with Cisco-Microsoft services, you'll need to work with this user via the Hybrid multi vendor actions. The Hybrid Status Message field displays the user's hybrid status. See Cisco-Microsoft Hybrid Subscribers

  1. Log in to the Automate Admin Portal.

  2. Choose the hierarchy.

  3. Go to (default menus) Microsoft Subscriber Management > Subscribers.

  4. On the Subscribers list, view a summary of Microsoft subscribers at the current hierarchy.

  5. Click on a subscriber in the list to open the Subscribers[subscriber name] page.

  6. Select a tab (or scroll to the relevant panel) to view and update settings:

    Note

    Automate allows you to toggle between a panel or tab layout via a toolbar button. The tabs/panels that display depend on enabled functionality.

    Tab/Panel Description
    MS 365 Microsoft user details, such as their display name, first and last name, User Principal Name (UPN), contact details, location, and groups.
    Exchange Custom Attributes

    Read-only. Displays on the subscriber's form only when Microsoft Exchange is installed and enabled for the subscriber (the subscriber has a Microsoft Exchange license), and provided values are filled out for these fields on the subscriber's Microsoft Exchange settings in Automate.

    These are fifteen additional fields that can be used for filtering from Microsoft Entra ID using model filter criteria, and to have the values available for flow through provisioning. The same fields are also available in the Microsoft Exchange settings (when installed) in Automate.

    The fields allow more flexibility when filtering users to be imported and then moved and, optionally, processed with flow through provisioning in Automate.
    MS Licenses

    View and update the subscriber's Microsoft license details, including their type (Group or Direct), and their licenses.

    Note

    When the license type is "Group", all license details (SKU and service plans) read-only.
    MS Teams

    The Microsoft subscriber's MS Teams details. The fields below are read-only:

    • User status
    • Interpreted User Type
    • Country or Region
    • Feature Types
    • Line URI
    • Line Type

    On this tab you can also enable or disable Enterprise Voice for this user.

    • You can only enable Enterprise Voice for a user that has a PhoneSystem license.
    • You can only assign a number to a user that has a PhoneSystem license.
    Local User The user corresponding with this subscriber.
  1. Save your changes.

Related Topics

Manage a Subscriber's MS Teams Policies

This procedure displays and updates the policies of individual subscribers via the Subscriber edit functionality:

Note

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

Note

This workflow is intended for Microsoft-only users. When choosing a hybrid user with Cisco-Microsoft services, you'll need to work with this user via the Hybrid multi vendor actions. The Hybrid Status Message field displays the user's hybrid status. See Cisco-Microsoft Hybrid Subscribers

  1. Go to (default menu) Subscriber Management > Subscribers.
  2. Click on a subscriber to open the Subscribers [subscriber name] page.
  3. Select the MS Teams tab.
  4. View currently applied policies for the subscriber.
  5. To choose different policies, click the down-arrow at the relevant policy, and select an alternative from the drop-down.
  6. Save your changes. Policy changes are synced back to the Microsoft cloud when performing an overbuild or a sync.

Microsoft Subscriber Relation

Model Details: relation/MicrosoftSubscriber

Title Description Details
MS 365 Group Assigned by FDP
  • Field Name: MS 365
  • Type: Object
Display Name
  • Field Name: MS 365.DisplayName
  • Type: String
First Name
  • Field Name: MS 365.FirstName
  • Type: String
Last Name
  • Field Name: MS 365.LastName
  • Type: String
User Principal Name
  • Field Name: MS 365.UserPrincipalName
  • Type: String
Title
  • Field Name: MS 365.Title
  • Type: String
Phone Number
  • Field Name: MS 365.PhoneNumber
  • Type: String
Mobile Phone
  • Field Name: MS 365.MobilePhone
  • Type: String
Usage Location Country code, eg. US
  • Field Name: MS 365.UsageLocation
  • Type: String
  • Choices: ["Afghanistan", "Åland Islands", "Albania", "Algeria", "American Samoa", "Andorra", "Angola", "Anguilla", "Antarctica", "Antigua and Barbuda", "Argentina", "Armenia", "Aruba", "Australia", "Austria", "Azerbaijan", "Bahamas, The", "Bahrain", "Bangladesh", "Barbados", "Belarus", "Belgium", "Belize", "Benin", "Bermuda", "Bhutan", "Bolivia", "Bonaire, Saint Eustatius and Saba", "Bosnia and Herzegovina", "Botswana", "Bouvet Island", "Brazil", "British Indian Ocean Territory", "Brunei", "Bulgaria", "Burkina Faso", "Burundi", "Cabo Verde", "Cambodia", "Cameroon", "Canada", "Cayman Islands", "Central African Republic", "Chad", "Chile", "China", "Christmas Island", "Cocos (Keeling) Islands", "Colombia", "Comoros", "Congo", "Congo (DRC)", "Cook Islands", "Costa Rica", "Côte d’Ivoire", "Croatia", "Curaçao", "Cyprus", "Czech Republic", "Denmark", "Djibouti", "Dominica", "Dominican Republic", "Ecuador", "Egypt", "El Salvador", "Equatorial Guinea", "Eritrea", "Estonia", "Ethiopia", "Falkland Islands (Islas Malvinas)", "Faroe Islands", "Fiji Islands", "Finland", "France", "French Guiana", "French Polynesia", "French Southern and Antarctic Lands", "Gabon", "Gambia, The", "Georgia", "Germany", "Ghana", "Gibraltar", "Greece", "Greenland", "Grenada", "Guadeloupe", "Guam", "Guatemala", "Guernsey", "Guinea", "Guinea-Bissau", "Guyana", "Haiti", "Heard Island and McDonald Islands", "Holy See (Vatican City State)", "Honduras", "Hong Kong SAR", "Hungary", "Iceland", "India", "Indonesia", "Iraq", "Ireland", "Isle of Man", "Israel", "Italy", "Jamaica", "Japan", "Jersey", "Jordan", "Kazakhstan", "Kenya", "Kiribati", "Korea, Republic of", "Kuwait", "Kyrgyzstan", "Laos", "Latvia", "Lebanon", "Lesotho", "Liberia", "Libya", "Liechtenstein", "Lithuania", "Luxembourg", "Macao SAR", "Macedonia, Former Yugoslav Republic of", "Madagascar", "Malawi", "Malaysia", "Maldives", "Mali", "Malta", "Marshall Islands", "Martinique", "Mauritania", "Mauritius", "Mayotte", "Mexico", "Micronesia", "Moldova", "Monaco", "Mongolia", "Montenegro", "Montserrat", "Morocco", "Mozambique", "Myanmar", "Namibia", "Nauru", "Nepal", "Netherlands", "Netherlands Antilles (Former)", "New Caledonia", "New Zealand", "Nicaragua", "Niger", "Nigeria", "Niue", "Norfolk Island", "Northern Mariana Islands", "Norway", "Oman", "Pakistan", "Palau", "Palestinian Authority", "Panama", "Papua New Guinea", "Paraguay", "Peru", "Philippines", "Pitcairn Islands", "Poland", "Portugal", "Puerto Rico", "Qatar", "Reunion", "Romania", "Russia", "Rwanda", "Saint Barthélemy", "Saint Helena, Ascension and Tristan da Cunha", "Saint Kitts and Nevis", "Saint Lucia", "Saint Martin", "Saint Pierre and Miquelon", "Saint Vincent and the Grenadines", "Samoa", "San Marino", "São Tomé and Príncipe", "Saudi Arabia", "Senegal", "Serbia", "Seychelles", "Sierra Leone", "Singapore", "Sint Maarten", "Slovakia", "Slovenia", "Solomon Islands", "Somalia", "South Africa", "South Georgia and the South Sandwich Islands", "South Sudan", "Spain", "Sri Lanka", "Suriname", "Svalbard and Jan Mayen Island", "Swaziland", "Sweden", "Switzerland", "Taiwan", "Tajikistan", "Tanzania", "Thailand", "Timor-Leste", "Togo", "Tokelau", "Tonga", "Trinidad and Tobago", "Tunisia", "Turkey", "Turkmenistan", "Turks and Caicos Islands", "Tuvalu", "U.S. Minor Outlying Islands", "Uganda", "Ukraine", "United Arab Emirates", "United Kingdom", "United States", "Uruguay", "Uzbekistan", "Vanuatu", "Venezuela", "Vietnam", "Virgin Islands, British", "Virgin Islands, U.S.", "Wallis and Futuna", "Western Sahara", "Yemen", "Zambia", "Zimbabwe"]
Department
  • Field Name: MS 365.Department
  • Type: String
Office
  • Field Name: MS 365.Office
  • Type: String
Street Address
  • Field Name: MS 365.StreetAddress
  • Type: String
Postal Code
  • Field Name: MS 365.PostalCode
  • Type: String
City
  • Field Name: MS 365.City
  • Type: String
State
  • Field Name: MS 365.State
  • Type: String
Country
  • Field Name: MS 365.Country
  • Type: String
Groups List of groups a user belongs to in Microsoft
  • Field Name: MS 365.groups
  • Type: String
Guicontrol
  • Field Name: guicontrol
  • Type: Object
Groups List of groups a user belongs to in Microsoft
  • Field Name: MS 365.guicontrol.groups
  • Type: String
Exchange Custom Attributes Group Assigned by FDP
  • Field Name: Exchange Custom Attributes
  • Type: Object
Custom Attribute 01 Extension Attribute 1
  • Field Name: Exchange Custom Attributes.extensionAttribute1
  • Type: String
Custom Attribute 02 Extension Attribute 2
  • Field Name: Exchange Custom Attributes.extensionAttribute2
  • Type: String
Custom Attribute 03 Extension Attribute 3
  • Field Name: Exchange Custom Attributes.extensionAttribute3
  • Type: String
Custom Attribute 04 Extension Attribute 4
  • Field Name: Exchange Custom Attributes.extensionAttribute4
  • Type: String
Custom Attribute 05 Extension Attribute 5
  • Field Name: Exchange Custom Attributes.extensionAttribute5
  • Type: String
Custom Attribute 06 Extension Attribute 6
  • Field Name: Exchange Custom Attributes.extensionAttribute6
  • Type: String
Custom Attribute 07 Extension Attribute 7
  • Field Name: Exchange Custom Attributes.extensionAttribute7
  • Type: String
Custom Attribute 08 Extension Attribute 8
  • Field Name: Exchange Custom Attributes.extensionAttribute8
  • Type: String
Custom Attribute 09 Extension Attribute 9
  • Field Name: Exchange Custom Attributes.extensionAttribute9
  • Type: String
Custom Attribute 10 Extension Attribute 10
  • Field Name: Exchange Custom Attributes.extensionAttribute10
  • Type: String
Custom Attribute 11 Extension Attribute 11
  • Field Name: Exchange Custom Attributes.extensionAttribute11
  • Type: String
Custom Attribute 12 Extension Attribute 12
  • Field Name: Exchange Custom Attributes.extensionAttribute12
  • Type: String
Custom Attribute 13 Extension Attribute 13
  • Field Name: Exchange Custom Attributes.extensionAttribute13
  • Type: String
Custom Attribute 14 Extension Attribute 14
  • Field Name: Exchange Custom Attributes.extensionAttribute14
  • Type: String
Custom Attribute 15 Extension Attribute 15
  • Field Name: Exchange Custom Attributes.extensionAttribute15
  • Type: String
MS Licenses Group Assigned by FDP
  • Field Name: MS Licenses
  • Type: Object
License type User License type (Group or Direct)
  • Field Name: MS Licenses.license_type
  • Type: String
Guicontrol
  • Field Name: guicontrol
  • Type: Object
License type User License type (Group or Direct)
  • Field Name: MS Licenses.guicontrol.license_type
  • Type: String
Licenses
  • Field Name: Licenses.[n]
  • Type: Array
SKU Part Number
  • Field Name: MS Licenses.Licenses.[n].AccountSkuId
  • Type: String
  • Target: device/msgraph/MsolAccountSku
  • Target attr: SkuPartNumber
  • Format: uri
Service Plans
  • Field Name: ServicePlans.[n]
  • Type: Array
Service Name
  • Field Name: MS Licenses.Licenses.[n].ServicePlans.[n].ServiceName
  • Type: String
Enabled
  • Field Name: MS Licenses.Licenses.[n].ServicePlans.[n].Enabled
  • Type: Boolean
MS Teams Group Assigned by FDP
  • Field Name: MS Teams
  • Type: Object
User status Status shows whether the user is licensed and provisioned for Teams, pending provisioning (in the event that the user is in staging and waiting for the MS cloud to sync in the User's Teams account) or only as a MS 365 User
  • Field Name: MS Teams.user_status
  • Type: String
Guicontrol
  • Field Name: guicontrol
  • Type: Object
User status Status shows whether the user is licensed and provisioned for Teams, pending provisioning (in the event that the user is in staging and waiting for the MS cloud to sync in the User's Teams account) or only as a MS 365 User
  • Field Name: MS Teams.guicontrol.user_status
  • Type: String
Enterprise Voice Enabled
  • Field Name: MS Teams.EnterpriseVoiceEnabled
  • Type: Boolean
Ms Teams
  • Field Name: MsTeams.[n]
  • Type: Array
Enterprise Voice Enabled
  • Field Name: MS Teams.MsTeams.[n].EnterpriseVoiceEnabled
  • Type: Boolean
Feature Types MS Teams Feature Types
  • Field Name: FeatureTypes.[n]
  • Type: Array
Account Enabled Account Enabled
  • Field Name: MS Teams.MsTeams.[n].AccountEnabled
  • Type: Boolean
Is SIP Enabled Is SIP Enabled
  • Field Name: MS Teams.MsTeams.[n].IsSipEnabled
  • Type: Boolean
Line URI
  • Field Name: MS Teams.MsTeams.[n].LineURI
  • Type: ["String", "Null"]
Line Type
  • Field Name: MS Teams.MsTeams.[n].LineURIType
  • Type: String
  • Choices: ["Direct Routing", "Calling Plan", "Operator Connect"]
Line URI TEL portion The tel value of the caller ID field is shown here, and is selectable from a drop-down list of available Internal numbers
  • Field Name: MS Teams.MsTeams.[n].LineURItel
  • Type: String
Line URI EXT portion If an ext value exists in the caller ID field, it will be shown here for information purposes
  • Field Name: MS Teams.MsTeams.[n].LineURIext
  • Type: String
Dial Plan A dial plan is a set of rules that translate a phone number that a user dials into a standard E.164 number for call authorization and routing
  • Field Name: MS Teams.MsTeams.[n].TenantDialPlan
  • Type: String
  • Target: device/msteamsonline/CsTenantDialplan
  • Target attr: Identity
  • Format: uri
Voice Routing Policy A voice routing policy for Direct Routing will be linked to a voice route using PSTN usage records. You can add existing PSTN usage records, change the order in which the usages will be processed, and assign the voice routing policy to users
  • Field Name: MS Teams.MsTeams.[n].OnlineVoiceRoutingPolicy
  • Type: String
  • Target: device/msteamsonline/CsOnlineVoiceRoutingPolicy
  • Target attr: Identity
  • Format: uri
Voicemail Policy Voicemail policies control the available features for the voicemail service in Teams
  • Field Name: MS Teams.MsTeams.[n].OnlineVoicemailPolicy
  • Type: String
  • Target: device/msteamsonline/CsOnlineVoicemailPolicy
  • Target attr: Identity
  • Format: uri
Calling Policy Calling policies control which calling and call forwarding features are available to users. Calling policies determine whether a user can make private calls, use call forwarding or simultaneous ringing to other users or external phone numbers, route calls to voicemail, send calls to call groups, use delegation for inbound and outbound calls, and so on.
  • Field Name: MS Teams.MsTeams.[n].TeamsCallingPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsCallingPolicy
  • Target attr: Identity
  • Format: uri
Caller ID Policy Caller ID policies are used to change or block the Caller ID (also called a Calling Line ID) for users. By default, the user's phone number is displayed when a call is made to a PSTN phone number such as a landline or mobile phone
  • Field Name: MS Teams.MsTeams.[n].CallingLineIdentity
  • Type: String
  • Target: device/msteamsonline/CsCallingLineIdentity
  • Target attr: Identity
  • Format: uri
Call Park Policy Call park lets people put a call on hold and transfer it to other people within your organization. Call park policies let you control which users are call park enabled and make other call park setting changes for them
  • Field Name: MS Teams.MsTeams.[n].TeamsCallParkPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsCallParkPolicy
  • Target attr: Identity
  • Format: uri
Call Hold Policy
  • Field Name: MS Teams.MsTeams.[n].TeamsCallHoldPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsCallHoldPolicy
  • Target attr: Identity
  • Format: uri
Emergency Calling Policy Emergency calling policies are used to control how users in your organization can use dynamic emergency calling features.
  • Field Name: MS Teams.MsTeams.[n].TeamsEmergencyCallingPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsEmergencyCallingPolicy
  • Target attr: Identity
  • Format: uri
Emergency Call Routing Policy Emergency call routing policies are used to set up emergency numbers for Direct Routing and then specify how those emergency calls are routed
  • Field Name: MS Teams.MsTeams.[n].TeamsEmergencyCallRoutingPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsEmergencyCallRoutingPolicy
  • Target attr: Identity
  • Format: uri
Audio Conferencing Policy Audio Conferencing policies control phone numbers and features available to users with audio conferencing
  • Field Name: MS Teams.MsTeams.[n].TeamsAudioConferencingPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsAudioConferencingPolicy
  • Target attr: Identity
  • Format: uri
Messaging Policy Messaging policies are used to control which chat and channel messaging features are available to users (owners and members) in Microsoft Teams
  • Field Name: MS Teams.MsTeams.[n].TeamsMessagingPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsMessagingPolicy
  • Target attr: Identity
  • Format: uri
Meeting Policy Meeting policies in Microsoft Teams are used to control the features that are available to meeting participants for meetings that are scheduled by users in your organization
  • Field Name: MS Teams.MsTeams.[n].TeamsMeetingPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsMeetingPolicy
  • Target attr: Identity
  • Format: uri
Live Events Policy Live events policies are used to control who in your organization can hold live events and the features that are available in the events they create
  • Field Name: MS Teams.MsTeams.[n].TeamsMeetingBroadcastPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsMeetingBroadcastPolicy
  • Target attr: Identity
  • Format: uri
Teams Policy Teams policies are used to control what settings or features are available to users when they are using teams and channels
  • Field Name: MS Teams.MsTeams.[n].TeamsChannelsPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsChannelsPolicy
  • Target attr: Identity
  • Format: uri
App Permission Policy App permission policies control what apps you want to make available to Teams users in your organization
  • Field Name: MS Teams.MsTeams.[n].TeamsAppPermissionPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsAppPermissionPolicy
  • Target attr: Identity
  • Format: uri
App Setup Policy App setup policies control how apps are made available to a user with the Teams app
  • Field Name: MS Teams.MsTeams.[n].TeamsAppSetupPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsAppSetupPolicy
  • Target attr: Identity
  • Format: uri
Update Policy Update policies are used to manage Teams and Office preview users that will see pre-release or preview features in the Teams app
  • Field Name: MS Teams.MsTeams.[n].TeamsUpdateManagementPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsUpdateManagementPolicy
  • Target attr: Identity
  • Format: uri
Enhanced Encryption Policy Enhanced encryption policies are used to control if users in your organization can use enhanced encryption settings in Teams
  • Field Name: MS Teams.MsTeams.[n].TeamsEnhancedEncryptionPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsEnhancedEncryptionPolicy
  • Target attr: Identity
  • Format: uri
Interpreted User Type Internal diagnostic property
  • Field Name: MS Teams.MsTeams.[n].InterpretedUserType
  • Type: String
Usage Location
  • Field Name: MS Teams.MsTeams.[n].UsageLocation
  • Type: String
Feature Types MS Teams Feature Types
  • Field Name: FeatureTypes.[n]
  • Type: Array
Account Enabled Account Enabled
  • Field Name: MS Teams.AccountEnabled
  • Type: Boolean
Is SIP Enabled Is SIP Enabled
  • Field Name: MS Teams.IsSipEnabled
  • Type: Boolean
Line URI
  • Field Name: MS Teams.LineURI
  • Type: ["String", "Null"]
Line Type
  • Field Name: MS Teams.LineURIType
  • Type: String
  • Choices: ["Direct Routing", "Calling Plan", "Operator Connect"]
Line URI TEL portion The tel value of the caller ID field is shown here, and is selectable from a drop-down list of available Internal numbers
  • Field Name: MS Teams.LineURItel
  • Type: String
Line URI EXT portion If an ext value exists in the caller ID field, it will be shown here for information purposes
  • Field Name: MS Teams.LineURIext
  • Type: String
Dial Plan A dial plan is a set of rules that translate a phone number that a user dials into a standard E.164 number for call authorization and routing
  • Field Name: MS Teams.TenantDialPlan
  • Type: String
  • Target: device/msteamsonline/CsTenantDialplan
  • Target attr: Identity
  • Format: uri
Voice Routing Policy A voice routing policy for Direct Routing will be linked to a voice route using PSTN usage records. You can add existing PSTN usage records, change the order in which the usages will be processed, and assign the voice routing policy to users
  • Field Name: MS Teams.OnlineVoiceRoutingPolicy
  • Type: String
  • Target: device/msteamsonline/CsOnlineVoiceRoutingPolicy
  • Target attr: Identity
  • Format: uri
Voicemail Policy Voicemail policies control the available features for the voicemail service in Teams
  • Field Name: MS Teams.OnlineVoicemailPolicy
  • Type: String
  • Target: device/msteamsonline/CsOnlineVoicemailPolicy
  • Target attr: Identity
  • Format: uri
Calling Policy Calling policies control which calling and call forwarding features are available to users. Calling policies determine whether a user can make private calls, use call forwarding or simultaneous ringing to other users or external phone numbers, route calls to voicemail, send calls to call groups, use delegation for inbound and outbound calls, and so on.
  • Field Name: MS Teams.TeamsCallingPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsCallingPolicy
  • Target attr: Identity
  • Format: uri
Caller ID Policy Caller ID policies are used to change or block the Caller ID (also called a Calling Line ID) for users. By default, the user's phone number is displayed when a call is made to a PSTN phone number such as a landline or mobile phone
  • Field Name: MS Teams.CallingLineIdentity
  • Type: String
  • Target: device/msteamsonline/CsCallingLineIdentity
  • Target attr: Identity
  • Format: uri
Call Park Policy Call park lets people put a call on hold and transfer it to other people within your organization. Call park policies let you control which users are call park enabled and make other call park setting changes for them
  • Field Name: MS Teams.TeamsCallParkPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsCallParkPolicy
  • Target attr: Identity
  • Format: uri
Call Hold Policy
  • Field Name: MS Teams.TeamsCallHoldPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsCallHoldPolicy
  • Target attr: Identity
  • Format: uri
Emergency Calling Policy Emergency calling policies are used to control how users in your organization can use dynamic emergency calling features.
  • Field Name: MS Teams.TeamsEmergencyCallingPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsEmergencyCallingPolicy
  • Target attr: Identity
  • Format: uri
Emergency Call Routing Policy Emergency call routing policies are used to set up emergency numbers for Direct Routing and then specify how those emergency calls are routed
  • Field Name: MS Teams.TeamsEmergencyCallRoutingPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsEmergencyCallRoutingPolicy
  • Target attr: Identity
  • Format: uri
Audio Conferencing Policy Audio Conferencing policies control phone numbers and features available to users with audio conferencing
  • Field Name: MS Teams.TeamsAudioConferencingPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsAudioConferencingPolicy
  • Target attr: Identity
  • Format: uri
Messaging Policy Messaging policies are used to control which chat and channel messaging features are available to users (owners and members) in Microsoft Teams
  • Field Name: MS Teams.TeamsMessagingPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsMessagingPolicy
  • Target attr: Identity
  • Format: uri
Meeting Policy Meeting policies in Microsoft Teams are used to control the features that are available to meeting participants for meetings that are scheduled by users in your organization
  • Field Name: MS Teams.TeamsMeetingPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsMeetingPolicy
  • Target attr: Identity
  • Format: uri
Live Events Policy Live events policies are used to control who in your organization can hold live events and the features that are available in the events they create
  • Field Name: MS Teams.TeamsMeetingBroadcastPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsMeetingBroadcastPolicy
  • Target attr: Identity
  • Format: uri
Teams Policy Teams policies are used to control what settings or features are available to users when they are using teams and channels
  • Field Name: MS Teams.TeamsChannelsPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsChannelsPolicy
  • Target attr: Identity
  • Format: uri
App Permission Policy App permission policies control what apps you want to make available to Teams users in your organization
  • Field Name: MS Teams.TeamsAppPermissionPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsAppPermissionPolicy
  • Target attr: Identity
  • Format: uri
App Setup Policy App setup policies control how apps are made available to a user with the Teams app
  • Field Name: MS Teams.TeamsAppSetupPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsAppSetupPolicy
  • Target attr: Identity
  • Format: uri
Update Policy Update policies are used to manage Teams and Office preview users that will see pre-release or preview features in the Teams app
  • Field Name: MS Teams.TeamsUpdateManagementPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsUpdateManagementPolicy
  • Target attr: Identity
  • Format: uri
Enhanced Encryption Policy Enhanced encryption policies are used to control if users in your organization can use enhanced encryption settings in Teams
  • Field Name: MS Teams.TeamsEnhancedEncryptionPolicy
  • Type: String
  • Target: device/msteamsonline/CsTeamsEnhancedEncryptionPolicy
  • Target attr: Identity
  • Format: uri
Interpreted User Type Internal diagnostic property
  • Field Name: MS Teams.InterpretedUserType
  • Type: String
Usage Location
  • Field Name: MS Teams.UsageLocation
  • Type: String
Local User Group Assigned by FDP
  • Field Name: Local User
  • Type: Object
User Name * User's Username.
  • Field Name: Local User.username
  • Type: String
User
  • Field Name: User.[n]
  • Type: Array
User Name * User's Username.
  • Field Name: Local User.User.[n].username
  • Type: String
First Name The User first name.
  • Field Name: Local User.User.[n].first_name
  • Type: String
Last Name The User last name.
  • Field Name: Local User.User.[n].last_name
  • Type: String
Title Title.
  • Field Name: Local User.User.[n].title
  • Type: String
Email Address The User email address.
  • Field Name: Local User.User.[n].email
  • Type: String
First Name The User first name.
  • Field Name: Local User.first_name
  • Type: String
Last Name The User last name.
  • Field Name: Local User.last_name
  • Type: String
Title Title.
  • Field Name: Local User.title
  • Type: String
Email Address The User email address.
  • Field Name: Local User.email
  • Type: String
Hybrid Status Message
  • Field Name: Local User.mvs_hybrid_status_message
  • Type: String
Guicontrol
  • Field Name: guicontrol
  • Type: Object
Hybrid Status Message
  • Field Name: Local User.guicontrol.mvs_hybrid_status_message
  • Type: String