With a Calling Plan, Microsoft is both the phone system and the phone company. The two can be bought as one bundle, Teams Phone with Calling Plan, or as a Teams Phone Standard license with a Calling Plan license added. The names sound alike, but Teams Phone and a Calling Plan are different things: one is the phone system and the other is Microsoft's calling service. On the other three routes Microsoft provides the phone system and a carrier provides the service behind it.
Atlantech Online shows what that looks like. It is a carrier in the Operator Connect program, and its Operator Connect page says it manages the PSTN calling services and the session border controllers, the devices that join a carrier's network to Teams. The customer's administrator still works in the Teams admin center, where the carrier's numbers are assigned to users. Atlantech lists a flat rate "as low as $3 per user/month" for that service, with unlimited calling in the US and number porting. That figure is a starting price for the carrier's part. Microsoft's licensing is a separate requirement, which a user's existing plan may already meet.
Suppose a company is set up this way and a customer calls its main number. The menu that answers, the queue that holds the call and the voicemail that takes it after hours all run in Microsoft's cloud. The phone number and the calling service that carried the call to Teams come from the carrier. A working Teams Phone deployment is both halves together.
A tenant can use more than one route. Any combination is supported, so a company can put office staff on one carrier and field staff on mobile numbers. We walk through that decision in how to choose a PSTN connectivity option for Teams Phone. What each route adds to the bill is in how much Teams Phone costs.