That seam is where this category drifts, because each half of the bill goes to a team that can only see its half. The Microsoft invoice lands with whoever manages software licensing — a team fluent in SKUs and entitlements that has never read a telecom contract. The carrier invoice lands with telecom or network — a team that knows trunks and rate schedules and has no visibility into which users carry which licenses. Both teams can do their jobs perfectly and still miss everything that lives in between, because the thing that needs validating isn’t either invoice. It’s the relationship between them.

Look at what accumulates in that blind spot. Users licensed for a Microsoft calling plan at sites already served by Operator Connect trunks — the same seat, provisioned for voice twice, each half legitimate on its own invoice. Departed employees whose accounts were disabled on schedule while the voice license behind them kept renewing, because deprovisioning runs on the identity checklist and the license true-up runs on the anniversary. Phone System entitlements purchased as add-ons for users whose bundled licenses already include them. And on the carrier side of the seam: trunk capacity sized for the migration’s peak week and never stepped back down, per-minute international and toll charges billing at rates nobody has held against the rate schedule since the contract was signed.

Then there’s the layer underneath all of it — the voice estate Teams Phone was supposed to replace. Every rollout plan I’ve seen has a go-live date for every site. Almost none of them carries a corresponding date for when the PRIs, the analog lines, and the legacy voice contracts

behind those sites stop billing. The project celebrates cutover; the old circuits bill on, site after site, waiting for a decommissioning effort that belongs to no phase of the project plan. I sat on the buyer’s side of enough voice transitions at Simon Property Group to know how reliable that pattern is: the migration ends at go-live, and the billing tail runs for quarters.

The tail ends in a decision worth scrutinizing, too. When the legacy contracts finally do get terminated, the exit math deserves the same line-by-item treatment as any invoice. On our reference engagement, one vendor exit arrived with a $120,584 early termination fee attached. Validated against the contracted terms, the fee did not survive — it was waived in full. Termination charges are drafted by the party collecting them; they are also governed by the agreement both parties signed, and the difference between those two facts is real money at exactly the moment a migration is supposed to be producing its payoff.

None of this argues against Teams Phone. The consolidation of calling into the collaboration layer is happening for good reasons, and the estates doing it deliberately are right to. The argument is narrower: a service that bills through two vendors needs its governance built across both, not inside either. That means one inventory — every voice-enabled user, every number, every trunk — held against both contracts at once, with each invoice validated line-by-item against that shared inventory and each variance disputed inside its window. That cross-seam validation is what we operate through BearGuard, our managed governance process, and voice modernization is where it earns its place early, because the seam opens on day one of the migration and never closes on its own.

The call will connect either way — that half of the story takes care of itself. What the estate actually pays for the call depends on somebody reading both invoices as one bill. In most organizations, that somebody hasn’t been named.