Calling Plans for Canada now generally available
Published May 01 2018 04:00 PM 14.4K Views

In January 2018, we announced Calling Plans for Canada was in public preview. Today, May 1, we are excited to announce the General Availability of Microsoft Calling Plans for Canada. Please contact your Microsoft Account Team or partner for details on purchasing.


All current Calling Plan features will be available to customers including domestic, international, and lower minute plans.  Canada’s domestic Calling Plan will include 3,000 minutes per user per month.


We are also offering an additional useful feature for US and Canadian customers. Any calls made between US and Canada users (in both directions) will be considered domestic, not international. This was a request we heard multiple times during the preview process. This will help customers further control costs.


It’s important to note that Calling Plans work with both Microsoft Teams and Skype for Business. You can buy today and use with Skype for Business in Office 365. And when you are ready to use calling in Teams, you can easily transition users.


Phone System and Calling Plans in Office 365 together enable calling for your organization, giving each user a primary phone number for making and receiving phone calls. Your organization can shift away from expensive telephony hardware to simplify the management of your phone system.


Getting started with Calling Plans

To acquire and use Microsoft Calling Plans, customers must have Phone System (formerly Cloud PBX), which is included with the Office 365 E5 plan and available as an add-on to other Office 365 plans. And if you are new to Teams, please review our quick start guide. You can learn more about geographic availability of Calling Plans here


Correction: in an earlier version of this blog, it was stated that minutes can pool across Canada and the US. This is incorrect. Pooling of minutes is by both SKU and country. Minutes are not shared across countries. We regret this error and any confusion it has caused. The blog has been corrected.

Version history
Last update:
‎May 02 2018 08:40 AM
Updated by: