A product team can keep its calling interface, preserve its customer workflows and still face a different bill after an infrastructure retirement. The reason is that the cost may move from an ACS consumption meter to a Teams-aligned licensing model, while the people using the product are customers your company does not control.
That is the important qualification in the title. Staying on an ACS Calling path does not automatically mean buying one Teams licence for every person who joins a call. The applicable model depends on how the workload identifies users, whether they participate as Teams users or external meeting participants, which Teams-aligned service is involved and which Microsoft terms apply.
The commercial decision is therefore straightforward: first classify the calling scenario, then compare its unavoidable licence and usage meters. A per-minute ACS price can look inexpensive until the required identity or Teams product changes who carries the cost.
Start with the retirement boundary
Microsoft’s Azure Communication Services retirement and breaking-changes guide, checked on October 29, 2026, gives September 30, 2028 as the retirement date for the affected standalone services. Microsoft defines retirement as permanent removal from Azure; after retirement, a retired service is unsupported and cannot be used.
That date matters because it prevents a misleading comparison. You cannot evaluate a future Teams-aligned path by looking only at today’s ACS usage charge. You need to establish which part of your implementation remains available, which product or service it must align with and whether that alignment introduces a separate licensing requirement.
For a white-labelled product, this classification is more consequential than it is for an internal company application. An internal deployment can usually identify its users, assign the relevant licences and pass the cost to one operating budget. A product sold to other organisations has a different boundary: its users belong to customers, may have different identities and may join through different meeting or calling paths.
That brings the analysis to the meter you can verify today.
The ACS usage meter is clear
Microsoft’s Teams interop pricing page lists ACS consumption for a Teams user participating through ACS APIs or SDKs at $0.004 per user minute. The unit is a user minute, so the charge follows the participating user minutes recorded through that ACS path.
The same pricing material shows native Teams-client participation at $0 per minute because that participation is covered by the applicable Teams licence. Those are different billing situations. One is an ACS consumption charge for a user participating through ACS APIs or SDKs; the other is participation through the Teams client under its applicable licence.
Microsoft’s Calling and Chat pricing page also lists an ACS over-IP calling rate of $0.004 per user minute for VoIP calling and video or audio participant legs. The page notes that a total bill can contain other meters, including recording, PSTN, direct routing, chat and storage.
The useful conclusion is limited but important. ACS gives you a visible variable charge for the ACS portion of the call. It does not tell you the total cost of a future Teams-aligned architecture, because the future model may add a licence, change the user identity model or introduce other service charges.
Before comparing totals, separate those units instead of treating them as interchangeable.
Three user models produce three different cost questions
The first model is an ACS application serving users through ACS APIs or SDKs. In that case, the directly documented consumption input is the ACS user-minute rate. Your forecast needs the number of participating user minutes, the call types that use ACS and any additional meters attached to the workload.
The second model is a Teams-aligned application in which participants are Teams users. Here, the question is whether each relevant user has the required Teams identity and licence for the specific product configuration. The answer cannot be inferred from the ACS rate alone. It must be confirmed against the applicable Microsoft product terms and the exact calling scenario.
The third model is a Teams-meeting arrangement in which people join as external participants. This can avoid additional Teams licences for those external participants, depending on the meeting and integration model. It also changes the product. Your application may have less control over identity, meeting policy, user experience and calling features than it had when the product owned the interaction through ACS.
These models are not interchangeable ways to buy the same thing. A lower apparent licence burden can come with a narrower integration surface, while a richer application experience can place more responsibility on the product owner to resolve identity, licensing and usage costs.
The third-party product problem
For a product sold to third parties, the hard question is who is expected to hold the licence. If the Teams-aligned scenario requires licensed Teams users, the product owner must determine whether those users are its own employees, the customer’s employees or people invited into a customer-controlled meeting.
That distinction changes the feasibility of the model. A company can budget for licences assigned to its staff. It has a much harder commercial and operational problem when every customer organisation must provide appropriately licensed users, or when the product owner is expected to account for users it does not administer.
Do not turn that problem into a universal rule. Some external-participant models may avoid additional Teams licences for those participants. They may also fail to provide the same product capabilities as a Teams-user or ACS SDK integration. The buyer needs Microsoft to confirm the permitted identity and licensing arrangement for the exact flow before treating the model as a migration plan.
This is why “the Teams licence costs less than the ACS minutes” is an incomplete conclusion. The licence may attach to a different population, and the product may have to change to qualify for that treatment.
Why the $0.004 rate is useful but insufficient
The verified $0.004 rate gives you a starting point for the variable side of the comparison. For example, a call with 10 participating user minutes would produce a $0.04 ACS consumption charge before any other applicable meter. That calculation uses only the published per-user-minute rate and the stated 10-minute workload assumption.
It does not establish a break-even point against a Teams plan. A break-even calculation requires a readable, current price for the applicable Teams product, the licence population, the billing period and the exact relationship between that licence and the calling workload. Those inputs vary by scenario, and a single Teams price would misrepresent the decision.
Once those inputs are confirmed, the method in the usage-based versus flat licensing crossover analysis applies directly.
The practical comparison should therefore be built as a model rather than a headline number:
| Cost question | What to measure | Why it matters |
|---|---|---|
| ACS consumption | ACS user minutes through APIs or SDKs | Applies the documented $0.004 per-user-minute rate to the relevant ACS path. |
| Teams-aligned licensing | Which users need which Teams identity or product licence | Determines whether the cost sits with your company, your customer or the participant’s existing organisation. |
| External participation | Which users join as external meeting participants | May avoid additional Teams licences while changing the available integration and product experience. |
| Additional service meters | Recording, PSTN, direct routing, chat, storage and other applicable services | Prevents the ACS or licence figure from being mistaken for the complete bill. |
Use the table for a workload-specific forecast. Record the user population, identity path, participant type, minutes and additional services separately. Then ask Microsoft to confirm which product terms apply to that exact configuration.
What a buyer should verify before staying
Ask five questions before treating the existing ACS Calling implementation as the low-risk option.
- Which service supports this workload after the retirement boundary? Record the Microsoft product name and the dated documentation that covers your particular API, SDK and participant flow.
- Who is a licensed user in this design? Separate your employees, your customer’s employees, Teams users and external meeting participants.
- What happens when a customer has no suitable Teams licence? Confirm whether the user can join through an external-participant path and which application capabilities would change.
- Which costs remain usage-based? Apply the ACS user-minute rate where it still applies, then add the documented rates for recording, PSTN, direct routing, chat, storage or other services in scope.
- Who owns the commercial obligation? Put the answer in the contract and operating model. A technically valid flow can still be unsuitable if the product owner cannot administer or recover the required licensing cost.
Microsoft may revise retirement and product documentation before September 30, 2028, so recheck the guide and the applicable pricing and licensing pages before committing to the path. Base the decision on the current documented scenario, and treat continuity of the existing ACS user experience and billing model as something to verify.
Bottom Line
Staying on an ACS Calling path does not automatically create a Teams licence obligation for every caller. The cost depends on whether the workload uses ACS consumption, licensed Teams identities or an external-participant meeting model, and those choices affect the product experience as well as the bill.
For a third-party white-labelled product, the safest recommendation is to model the user and identity path before comparing prices. Use the documented ACS rate of $0.004 per user minute as one input, obtain written confirmation of the applicable Teams licensing scenario and reject any forecast that assigns one unverified seat price to every customer user.
What's Next
Cost is only one part of the replacement decision. The companion guide, Choosing an ACS Replacement: What to Check Before You Commit Again, turns the retirement into a broader evaluation of roadmap durability, deployment control and the ability to leave later.
Read it after you have mapped your current users, identities and billing meters, because those details determine which replacement options are genuinely comparable.
FAQs
Does staying on ACS Calling always require a Teams licence for every user?
No. Licensing depends on the Teams-aligned scenario, the identity model and whether people participate as Teams users or external meeting participants. Confirm the exact configuration and applicable Microsoft terms before assigning a licence obligation to every caller.
What is the ACS price for a Teams user participating through an ACS SDK?
Microsoft lists ACS consumption for a Teams user participating through ACS APIs or SDKs at $0.004 per user minute. The rate applies to that ACS consumption path and does not represent the total cost of every Teams-aligned design.
Can external participants avoid additional Teams licences?
Some Teams-meeting integration models allow external participants to join without additional Teams licences for those participants. That model can have different identity, control and feature constraints, so it should be evaluated as a different product flow rather than treated as a like-for-like replacement.
Can I calculate the break-even point between ACS minutes and Teams licences?
Only after you have a verified price for the applicable Teams product, the licence population and the relevant billing terms. The $0.004 ACS rate alone is insufficient to produce a valid break-even point.
What else can appear on an ACS calling bill?
Microsoft’s Calling pricing documentation identifies additional possible meters, including recording, PSTN, direct routing, chat and storage. Forecast each applicable service separately instead of treating the user-minute rate as the complete bill.
When should a company recheck the ACS retirement information?
Recheck Microsoft’s retirement and breaking-changes guide before committing to a migration or long-term licensing model. The guide currently gives September 30, 2028 as the retirement date for the affected services, and product documentation can change before that date.
