Teams Calling Plans
There is a current offer in the legacy CSP price list for:
Microsoft 365 Domestic Calling Plan for US and Canada
This SKU existed over the summer and a current customer transacted using it at the $8 list price based on guidance from Microsoft. On the current NCE price list this SKU does not exist. I can't find any old information that this was a promo SKU, what it was intended to be used as, or an end date.
The current challenge is that the customer has been using this and when shifting to NCE they would need to use the Domestic Calling Plan which is $12 vs. the $8. A 50% price increase, which is pain point given they are 7 months into making this purchase.
Additionally, with all the Teams SKU changes E3 users can add the Microsoft Teams Phone with Calling Plan for $15, which includes both the phone system itself and calling plan. This essentially makes the calling plan roughly $8, inline with above SKU. For the M365 E5 user their only option is the $12 Domestic Calling Plan. It seems that an E3 user is in a better price position than the E5 user even though they are investing more heavily in Microsoft.
Any guidance or information about this old SKU and if we would expect to see it on the NCE price list, was it a promo, etc... would be extremely helpful to help relieve a customer sat issue.
On the same topic, are all add-on products now considered new subscriptions (ie. only available in NCE even though the pre-qualifying product is legacy) if they have not been provisioned before?
Our customer has a legacy subscription and wants to try out Teams Phone. However the only add-on option that shows up is the $20 Teams Phone with Calling Plan (country zone 1 - US) product ID # 1ee81de6-4d8b-4cf1-b926-2fd2a774a4ca.
The legacy $15 and Trial subscriptions are still on the pricelist, but are these only available to customers who already have this add-on?
Is provisioning the $15 annual susbscription in NCE the best way to go in this case?
It has now been 7 months since @Jalt originally posted this issue. I have attempted to run this down through my CSP, at both Synnex and Ingram, and it falls on deaf ears, seemingly because Microsoft is happy to ignore that they are burning the customers that are paying them for their flagship, premium, E5 plans. There is no doubt that someone, likely many someones, inside of Microsoft are aware of the pricing issue that has been created with the transition to NCE. I jumped into the Teams direct stuff with MS as it works great. Zero response from Microsoft from this is typical corporate America. No time for anyone but themselves except when they want to sell you more stuff. No wonder America is on its way to hell in a handbasket.
@v-jillarmour : I think this is resolved, isn't it? There were a couple of additional changes in July for Teams Calling Plans as well and Domestic calling plans are available in NCE (new, zone-based model); @CoreyRacing did post a rhetorical question only.
@Jalt : Looking at the price list in Europe it looks a bit different though, seems this is something specific for USD (and probably Canada) market:
Domestic Calling Plan (1200 Minutes, in US this has 3000 minutes) - CFQ7TTC0LHXJ:0001:
- Europe: €10.1/month (annual term)
- US: $12/month (annual term)
Teams Phone with Calling Plan - CFQ7TTC0HL73:0001
- Europe: €16.9/month (annual Term)
- US: $15/month (annual Term)
Teams Phone Standard - CFQ7TTC0LH0T:0001
- Europe: €5.36/month (annual Term)
- US: $6.4/month (annual Term)
While for Europe this adds up as expected - I now see the issue for US as well where the specific bundle is cheaper then expected (especially given the same was priced at $20 in legacy). Will check with team if there is some reasoning for this.
Did you find out anymore info on the Domestic Calling Plan US not being available via NCE? It makes no sense that Microsoft would release the SKU in the fall and have no plans to roll it into NCE.
Thanks for the update @v-jillarmour
Is is possible for someone else at MS to investigate/assist with this? This is an issue that is impacting many of us CSPs. We were told it would be resolved by the middle of this week, but that time has come and gone.
Any help will be greatly appreciated by us all.
I understand you have been waiting for answers and I'm sorry, I'm not a subject matter expert on this and I don't know of anyone else that can answer this for you currently. I will look into it and see what I can find out, no promises! 🙂
We had a cloud consult on the new Teams Phone with Calling Plan in January. At that time there were no plans to transition that plan to NCE. We asked support about two weeks ago, same answer
That doesn't align with this though from last week: Audio Conferencing select dial-out delayed in new ... - Microsoft Partner Community
Actually surprised that thread isn't getting more attention.
Let’s make sure we are talking about the same thing. I was talking about the Domestic calling plan that started this thread. The dial out for Audio Conferencing is delayed.
President / CEO
www.BoxTechs.com| firstname.lastname@example.org | (267) 885-0985
This is my exact same challenge. One specific customer is already M365 E5. They are now being forced to use the $12 plan, while a small subset are using M365 E3 and can use a $15 all-in.
To be frank, they are just considering 3rd parties vs. the calling plans if this doesn't get resolved as they would face a 50% price increase for the same thing.
How about a third party with a carrier-grade NA Network developed and designed for the purposeful use of Teams Calling? Dedicated to MSPs only, fully integrated with the Microsoft Core, and carries the Microsoft badge of, "Advanced Specialization in Calling for Microsoft Teams"