Microsoft Teams is a unified communication and collaboration platform that combines phone service, workplace chat, video meetings, file storage, and application integration.
8x8 Voice for Microsoft Teams is a cloud-based PBX-to-PBX integration with Microsoft Phone System, which creates a seamless, behind-the-scenes integration of 8x8 Work phone service into Microsoft Teams.
So in essence, the Voice for Teams service provides enterprise-grade telephony and global PSTN connectivity to customers who want to retain Microsoft Teams as their sole collaboration interface.
Microsoft Teams is supported only through our Voice for Microsoft Teams product referred to in this article.
- 8x8 has CRM integrations for Salesforce, NetSuite, and many other applications—all of which use a docked or floating communication panel tied to our Maestro integrations platform.
- Currently there are no plans to develop a separate Maestro integration for Microsoft Teams.
- Microsoft Teams
- Microsoft Office 365
- 8x8 Voice for Teams
- 8x8 Work
- 8x8 Admin Console
- Contact Center
How It Works
The 8x8 telephony service essentially replaces existing or potential voice service offered by Microsoft Teams.
When the setup is completed, Microsoft Teams devices are registered as SIP devices, just like a desk phone. The required phone extension and user information is synchronized from 8x8 to the Microsoft Teams environment, and the user's 8x8 phone number will appear in Teams devices.
So when a Teams user makes or receives phone calls using a Teams client or device, the calls are transparently handled by the 8x8 phone service. The end user will probably not even be aware that they are using 8x8 unless they're told about it.
8x8 desk phones are not required, but are supported. Customer 8x8 PBXs handle desk phones directly, rather than through the Microsoft Teams infrastructure.
All other devices and clients typically supported by Microsoft Teams are also supported by 8x8 Voice for Teams. So in the event of service issues with Microsoft Office 365 or Teams specifically, any assigned 8x8 desk phone would still continue to work.
Obtaining 8x8 Voice for Microsoft Teams Service
All requests for the 8x8 Voice for Microsoft Teams service must be directed to 8x8 Sales representatives or Partners.
- Only 8x8 X-Series accounts are supported. CRM/Account Manager accounts are not compatible with the service.
- Contact Center is supported, but requires use of the AGUI. The Microsoft Teams dialpad will display call activity of the associated 8x8 Work extension.
- 8x8 Work for Desktop is generally not available, but can be enabled by a service administrator in the event of Microsoft service issues.
- Microsoft's Phone System License is required per user for the Teams dial pad to be visible. Microsoft E5 licenses include this function, but a Phone System License must be purchased from Microsoft for E1 and E4 licenses.
- Microsoft Teams Voicemail: It's recommended that Microsoft's implementation of voicemail in Teams be disabled, especially when agents are assigned to 8x8 Work ring groups and call queues. In this case, to avoid calls routing to voicemail instead of an available agent, Call Waiting should also not be disabled at the user extension level.
- Microsoft Azure is supported as an Identity Provider in the Admin Console. Azure SCIM / sync is also supported with an Azure AD App Gallery application for 8x8. This means that Office 365 administrators can push new user creation from Azure AD to the 8x8 Admin Console, which can then be synced to Teams via the 8x8 Voice for Teams Admin Portal.
- Initial sync of new Voice for Teams users can take up to seventy-two hours, due to general service impact experienced by Microsoft Office 365—this is not an issue on the 8x8 side. The Microsoft Teams dial pad will appear for users only after sync has been completed. Note that this applies to ALL sync activity between 8x8 and Microsoft Teams, so any subsequent change made to a user in 8x8 Admin Console will require time to sync to Teams.
- Additional information can be found in the article linked, below.