Does a Teams Phone license include a phone number?

A Teams Phone license and a phone number are sold and provisioned separately, so buying the license alone leaves a user with calling features but no number to dial from or receive calls on.[1][3] Microsoft is direct about this in its number management guidance: telephone numbers are not included with Teams Phone licensing, and numbers for your tenant are acquired through the service provider that supplies your connection to the public switched telephone network (PSTN).[3]

What the license entitles you to

The Teams Phone license, sold on its own as Teams Phone Standard, turns on the Microsoft 365 Phone System features, the private branch exchange (PBX) capabilities such as cloud voicemail, call forwarding, call transfer, auto attendants, call queues, and caller ID.[8] It also grants the user access to whatever PSTN solution your organization has connected, which is the piece that carries calls to and from ordinary phone numbers.[4] What the license does not do is supply the number itself or any outbound minutes, so a user who holds only Teams Phone Standard can use the calling features internally but cannot yet place a call to a landline or mobile.[3][8]

What the PSTN solution supplies

A PSTN solution provides two things the license cannot: the phone numbers allocated to your organization, and the actual route to domestic, international, and emergency calling.[1][2] Microsoft describes the service provider as your partner for both PSTN access and the allocation of telephone numbers for your enterprise, and it requires a secure PSTN integration with your tenant before any licensed Teams Phone account can make or receive calls.[2] So a working setup has two line items, the license per user and a PSTN option, and you plan and budget for both.

A Microsoft Calling Plan makes Microsoft your carrier, so your numbers, your outbound minutes, and emergency screening in the United States all come from Microsoft.[2][5] You buy the Teams Phone add-on first, then add a Domestic, International, or Pay-As-You-Go Calling Plan, and you acquire numbers inside the Teams admin center with Microsoft listed as the operator.[5][6] A Calling Plan license is the prerequisite for pulling numbers from Microsoft, because without at least one assigned in your tenant you cannot acquire a Microsoft number at all.[6] This option fits organizations in a country where Calling Plans are sold and who would rather run one vendor than assemble their own carrier relationship, so the first thing to confirm is availability in your region.[2][5]

Operator Connect lets you use a third-party carrier that has already built a certified connection into Teams, so that operator supplies your numbers, PSTN access, and support while Microsoft keeps running the Teams platform.[2][12] You choose a participating operator from Microsoft's directory, enable them in the Teams admin center, and assign their numbers to your users, with the operator holding the underlying contract and service level agreement.[2] Because the carrier owns the connection, much of the setup and ongoing management shifts to them, which is usually the reason a team picks this route in a country where Microsoft's own Calling Plan is not sold or where they want to keep a preferred provider.[2] The number still lands on a user who holds a Teams Phone license, so the license and the number stay distinct even when one company manages both.[2][8]

Teams Phone Mobile ties a user's SIM-enabled mobile number to their Teams identity, so a single number rings on the cellular network and inside Teams.[2] The number and PSTN access come from a certified mobile operator that has completed the integration with Microsoft, and the mobile SIM, which can be an eSIM, is the piece your administrators manage.[2] This fits mobile-first staff who would rather carry one number for the handset, the desk app, and the desktop than juggle a separate work line.[2] Availability depends on whether your mobile provider takes part in the Microsoft Teams Phone Mobile program, so confirm participation with the carrier before you plan around it.[2]

Direct Routing connects a carrier of your choice to Teams Phone through a certified session border controller (SBC) that you, an integrator, or a Direct-Routing-as-a-Service provider runs, and that carrier supplies the numbers.[2] It works in any country and gives you the most control, which is why organizations use it to keep an existing carrier contract, meet a local regulatory requirement, or connect legacy equipment such as analog devices, paging systems, and third-party PBXs.[2] The cost of that flexibility is responsibility, since the SBC brings certificate management, DNS settings, call-routing policies in Teams, and last-mile circuit integration, so it asks more of your IT team or partner than the managed options do.[2] Every user still needs a Teams Phone license, and Direct Routing is the only model that can keep local PSTN calls working through a Survivable Branch Appliance if the link to the cloud is interrupted.[2][8]

You can either request brand-new numbers or transfer the numbers you already use, and both paths run through your PSTN provider rather than the Teams Phone license.[3][6] With a Microsoft Calling Plan, you request new numbers through the Add phone numbers wizard in the Teams admin center, choosing a country, a number type, and a quantity, with Microsoft as the operator.[6]

Porting an existing number

To keep a number you already own, you submit a port order that moves it from your current carrier to Microsoft, which then becomes the service provider of record for that number.[9] The port runs on a Letter of Authorization signed by the account's authorized user, and Microsoft manages fulfillment with your losing carrier, so the number keeps working while it transfers.[9] Porting timelines and required documents vary by country, and ported numbers do not count against the standard allotment of new numbers your licenses would otherwise grant.[6][9]

Numbers for people and numbers for services

Not every number is for a person. Microsoft separates user or subscriber numbers, assigned to individual users, from service numbers used by voice apps such as auto attendants and call queues, and the two types are acquired and counted differently.[3][6]

Two bundled licenses do fold a number and calling into a single purchase, which is the closest Teams Phone comes to including a number.[7] Teams Phone with Calling Plan, listed at about $17 per user each month paid yearly, pairs the license with a Microsoft Calling Plan that provides a phone number and roughly 3,000 outbound domestic minutes, and Teams Phone with Pay-As-You-Go Calling, listed around $13, provides a number with metered outbound minutes.[7] The standalone Teams Phone Standard license, at about $10 per user each month, carries no calling plan and no number, which independent pricing guides current to 2026 confirm.[7][10][11] Treat these as planning figures, because Microsoft changes pricing and availability by region and over time.[7]

Owning E5 does not change the rule

A Microsoft 365 E5 or Office 365 E5 subscription already includes the Phone System license, so those customers do not buy Teams Phone Standard separately.[4][8] Even so, E5 still does not include a phone number, because an E5 tenant needs a PSTN option and its numbers just like any other.[3][4]

Shared Calling shares one number

Shared Calling lets several users make outbound calls through the number of a single resource account, so those users need only a Teams Phone license and no dedicated number or calling plan of their own.[4] It is a way to give occasional callers outbound access without allocating a number to every person, and the shared number itself still comes from a PSTN option.[4]

Because the number lives outside the license, a few practical details shape how you buy and run Teams Phone.

The license is not the whole bill

A Teams Phone Standard license on its own cannot reach the outside world, so the real per-user cost includes a PSTN option on top of it, whether that is a Microsoft Calling Plan, an Operator Connect subscription, or the SBC and carrier contract behind Direct Routing.[7][8] Budgeting only for the phone license understates what a working deployment costs.

Calling Plan availability is uneven

Microsoft's own Calling Plan is sold in a limited set of countries, so an organization with offices outside that list often combines connectivity types by region, for example Operator Connect where a Calling Plan is not available.[2][5]

Number quantities are capped by license count

With a Microsoft Calling Plan, the count of user numbers you can hold is tied to how many Calling Plan licenses you have assigned, and service numbers scale in bands with your Teams Phone and Audio Conferencing license totals, so you cannot stockpile far more numbers than you license.[6] Ported numbers sit outside those limits.[6]