Microsoft Business Voice

Microsoft Business Voice


Microsoft Business Voice: A Telephone System for the Modern Workplace

Service update: Microsoft Business Voice retired in June 2022. This article explains the former offering and the checks to make when reviewing current Teams calling options. Do not use an old Business Voice price or feature list to purchase a new service.

The video provides historical context. Product names, licences, features, and commercial terms may have changed since it was recorded. Check the current Microsoft guidance and your agreement before making a decision.

What Was Microsoft Business Voice?

Business Voice was a cloud-based telephony offering that added calling functions to Microsoft Teams. Its service description lists features such as call forwarding, call queues, auto attendants, audio conferencing, and calling plans. These functions supported business communication within Teams.

It was not a separate replacement for every Microsoft 365 application. Calling, meetings, file collaboration, and office applications have different features and licensing requirements. Review the specific capability your business needs.

Retirement and the Licensing Transition

According to the Microsoft service description and retirement note, the offering retired in June 2022. Microsoft says existing customers are not automatically moved to the new licensing model. The note identifies these options for evaluating a transition:

  • Teams Phone Standard: cloud-based phone-system capabilities in Teams.
  • Audio Conferencing: dial-in and dial-out conferencing for meetings, subject to the applicable plan.
  • Teams Calling Plans: a Microsoft option for public switched telephone network connectivity.

These names describe different parts of a calling solution. The exact combination depends on your base subscription, region, users, and required features. Confirm the currently available plans and terms with Microsoft or your authorized provider.

Review Calling and Meeting Requirements

First, list the tasks your users need: incoming calls, transfers, queues, voicemail, meeting dial-in, or calls from supported mobile devices. Then map each requirement to the proposed service and licence. A Teams meeting entitlement alone does not establish that all external calling features are included.

Also, review number ownership, number transfers, emergency-calling locations, and any recording requirements. Number availability and transfers depend on the provider, country, and existing service. Do not assume every number or destination is supported.

Compare the Full Cost

Request a current written quote for the intended region and service. Include base licences, phone-system features, connectivity, usage, devices, setup, and support. Ask which charges or restrictions apply to international calls, conferencing, storage, and cancellation.

Historical minute bundles are not a reliable guide to today’s offer. Compare the complete scope against your existing service. A cloud phone system may change equipment and management costs, but savings depend on actual usage and responsibilities.

Plan Reliability and Security

A hosted calling service depends on power, internet access, supported devices, account configuration, and provider availability. It cannot guarantee uninterrupted calls or prevent every security incident. Test audio quality and your approved fallback arrangements before a wider move.

Review cloud dependencies as part of the wider IT plan. Private cloud hosting is a separate service; it does not replace the Teams calling licences or connectivity your users require.

Limit administrative access, protect accounts, and define who can change routing or recover service. Staff should know how to report suspicious calls and account activity. Document escalation and recovery responsibilities with the provider.

Pilot the Change with Your Team

Start with representative users and call scenarios. Check transfers, queues, voicemail, remote access, and emergency-calling configuration through the provider’s approved test process. Never place an unsolicited test call to emergency services.

Next, plan number transfers and cutover around business needs. Agree acceptance checks, fallback steps, and a support contact. Keep records of the tests and unresolved issues before expanding the rollout.

Discuss Your Business Phone Requirements

Technijian can help review communication requirements and related IT responsibilities. Bring your current subscriptions, phone contract, user locations, and known service gaps. Contact Technijian to discuss the options, scope, and tests needed for your environment.

Ravi JainAuthor posts

Avatar for Ravi Jain

Technijian was founded in November of 2000 by Ravi Jain with the goal of providing technology support for small to midsize companies. As the company grew in size, it also expanded its services to address the growing needs of its loyal client base. From its humble beginnings as a one-man-IT-shop, Technijian now employs teams of support staff and engineers in domestic and international offices. Technijian’s US-based office provides the primary line of communication for customers, ensuring each customer enjoys the personalized service for which Technijian has become known.

Comments are disabled