About this Document
Last updated: 20 March 2026
Fusion for Microsoft Teams Module (Admin View – Process & Functionality)
Module Purpose
Fusion for Microsoft Teams provides structured, tenant-based administration for Teams onboarding, user provisioning, number assignment, template-driven configuration, and resource-account management. The module is intended to reduce the complexity of working directly with Microsoft Graph, PowerShell, and related dependencies by exposing a controlled administrative layer in Fusion.
Onboarding Context
Fusion supports Microsoft Teams onboarding in both Direct Routing and Operator Connect contexts. As part of onboarding, Fusion creates the operational link between the Fusion tenant and the customer’s Microsoft tenant. After successful onboarding, routing policies can be provisioned automatically on the customer tenant to simplify initial service activation.
Microsoft Teams Administration Workflow
A typical Microsoft Teams administration sequence is:
- Confirm that the tenant subscription has the required Teams-related entitlements
- Complete or validate Teams tenant onboarding
- Confirm that the Microsoft tenant is linked to the Fusion tenant
- Review available groups and user filtering options
- Select the Microsoft groups whose users should be managed in Fusion
- Review, add, or bulk-manage users
- Apply templates where standardised provisioning is required
- Assign numbers, customer licenses, and voice-related properties as needed
- Manage resource accounts for service entities such as call queues and auto attendants
This flow is designed to move from entitlement and linkage into operational user administration.
Groups and Users
Fusion can display existing Microsoft users already available in the customer’s Active Directory / Microsoft environment, and it supports management based on selected groups. Multiple subscriptions can be linked to the same Microsoft tenant using different filters, which allows administrators to organise the customer view according to operational or business structure.
Administrators should use group filtering deliberately. It allows the service view in Fusion to reflect the intended management boundary rather than exposing all users indiscriminately.
User Provisioning and Bulk Management
Fusion supports both individual and bulk user management. Bulk upload functionality is available for managing multiple Microsoft users at once, which is especially useful during onboarding, migration, or large-scale service changes.
When managing users, the administrator typically works through the following process:
- Select the relevant tenant subscription
- Filter the visible user scope using groups where needed
- Review existing users and license state
- Add a new user or select existing users for update
- Use UPN as the primary identifier when updating users in bulk
- Assign numbers and service-related attributes according to entitlement and template logic
- Confirm successful provisioning
Fusion also checks the Microsoft license associated with each user, which helps ensure alignment between service assignment and the user’s eligibility to be voice-enabled.
Templates
Templates provide a standardised way to apply the same configuration pattern to multiple users. Within a subscription, a template can include:
- Location
- License
- Voice routing policy
- Groups
- Customer licenses
Templates support both rapid onboarding and consistency of service configuration. They can also be used during bulk provisioning, which reduces repetitive manual work and improves governance.
Number Assignment
Numbers can be assigned to Teams users depending on Microsoft license compatibility and voice-enablement requirements. Once a number is correctly assigned and the user is voice-enabled, the Microsoft Teams client can be used for external calling.
Resource Accounts
Resource accounts in Microsoft Teams are used for service entities such as Call Queues and Auto Attendants. Fusion supports the management of these resource accounts and automates the assignment of service attributes so that they can be reached externally. Administrators can manage resource-account properties such as phone number, voice policy, customer license, and location, while the creation of the underlying service constructs themselves is more limited in scope.
Post-Onboarding Visibility
Once onboarding is complete, the module provides visibility into key tenant subscription details, including:
- Tenant ID
- Domain
- Mode
- Routing-policy provisioning status
This gives administrators an immediate summary of the tenant context and provisioning state.