You choose a Teams Phone PSTN connectivity option by matching one of Microsoft's four models to where your users are, whether you want to keep an existing carrier, and how much of the telephony plumbing you are willing to run yourself.[1] A Microsoft Calling Plan makes Microsoft your carrier and is the simplest setup, but it is sold in only a limited set of countries.[1][2] Operator Connect and Teams Phone Mobile hand the carrier role to a certified operator that manages the connection for you, with Teams Phone Mobile built around a single SIM-based mobile number that also rings in Teams.[1][3][4] Direct Routing works in any country and connects almost any carrier through a session border controller you or a partner manage, which is why organizations pick it to keep a current carrier or connect legacy PBX and analog equipment.[1][5] One tenant can use several of these at once, so the practical decision is often per country or per type of worker rather than a single choice for the whole company.[1]
\n","summary":"Teams Phone needs a PSTN connection on top of the phone license, and Microsoft offers four ways to provide it: a Microsoft Calling Plan, Operator Connect, Teams Phone Mobile, and Direct Routing. The right pick depends on whether Calling Plans are sold in your countries, whether you want to keep a current carrier, how much infrastructure you want to run, and any emergency-calling or continuity needs. A single tenant can combine options by region or by type of worker.","publishedAt":"2026-07-18T03:43:05.249","verifiedAt":"2026-07-17T00:00:00","editorialStatus":"APPROVED","lastReviewedAt":"2026-07-17T00:00:00","nextReviewDueAt":"2026-10-17T00:00:00","templateVersion":"v2","aliases":["How do I pick a PSTN option for Microsoft Teams Phone?","Calling Plan vs Operator Connect vs Direct Routing","Which Teams Phone PSTN connectivity option should I choose?","Teams Phone PSTN options compared","Operator Connect or Direct Routing for Teams?","How to connect Teams Phone to the PSTN","Teams Phone calling options explained","Direct Routing vs Calling Plan for Teams","Choosing a Teams Phone carrier option","Teams Phone Mobile vs Operator Connect","What PSTN option is right for Teams Phone?","Best way to add phone calling to Microsoft Teams"],"confidenceScore":92,"confidenceLabel":"High","canonicalUrl":null},"contributor":{"id":"ec39deab-44fe-48d8-9029-fefe993ab85a","slug":"answer-stack","displayName":"AnswerStack","websiteUrl":null},"contributorOrganizationProfile":{"entityId":"ec39deab-44fe-48d8-9029-fefe993ab85a","legalName":null,"description":null,"websiteUrl":null,"imageUrl":null,"slogan":null,"subtitle":null,"facts":[],"coiNote":null,"foundingDate":null,"numberOfEmployeesText":null,"contactPoint":null,"address":null,"headquartersText":null,"organizationType":null},"contributorPerson":{"slug":"answerstack-editorial-team","displayName":"AnswerStack Editorial Team"},"sections":[{"id":"db67756a-dbd8-4309-a29c-57164ed4f2fa","sectionKey":"what_you_are_choosing","sectionType":"markdown_section","heading":"What are you choosing between?","introMarkdown":"Choosing a PSTN connectivity option means deciding how Teams Phone reaches the regular telephone network, because the phone license by itself only handles calls between people inside your organization.[1][2] To dial and receive normal landline and mobile numbers, each user needs a Teams Phone license plus a separate connection to the public switched telephone network, or PSTN, and Microsoft supports four ways to supply that connection: a Microsoft Calling Plan, Operator Connect, Teams Phone Mobile, and Direct Routing.[1] The four models differ mainly in who acts as your carrier and how much of the underlying connection you manage, so the choice is less about call quality and more about coverage, control, and who holds the support contract.[1]\n\n### The license and the connection are separate decisions\n\nA Teams Phone license turns on the calling and PBX features, and every one of the four options still requires that license on each user.[1] What changes between the options is the source of the phone numbers and the route to the outside network, which means you can settle the licensing question first and treat the PSTN option as a second, independent decision.[1][2]\n\n### You are not locked into one model\n\nOne tenant can run more than one connectivity type at the same time, and you can add or change them over time in any order.[1] That matters for the decision because a company with offices in several countries rarely finds a single option that covers everyone, so the realistic outcome is often a mix, for example a Calling Plan where it is sold and Direct Routing where it is not.[1]","introHtml":"Choosing a PSTN connectivity option means deciding how Teams Phone reaches the regular telephone network, because the phone license by itself only handles calls between people inside your organization.[1][2] To dial and receive normal landline and mobile numbers, each user needs a Teams Phone license plus a separate connection to the public switched telephone network, or PSTN, and Microsoft supports four ways to supply that connection: a Microsoft Calling Plan, Operator Connect, Teams Phone Mobile, and Direct Routing.[1] The four models differ mainly in who acts as your carrier and how much of the underlying connection you manage, so the choice is less about call quality and more about coverage, control, and who holds the support contract.[1]
\nA Teams Phone license turns on the calling and PBX features, and every one of the four options still requires that license on each user.[1] What changes between the options is the source of the phone numbers and the route to the outside network, which means you can settle the licensing question first and treat the PSTN option as a second, independent decision.[1][2]
\nOne tenant can run more than one connectivity type at the same time, and you can add or change them over time in any order.[1] That matters for the decision because a company with offices in several countries rarely finds a single option that covers everyone, so the realistic outcome is often a mix, for example a Calling Plan where it is sold and Direct Routing where it is not.[1]
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":0},{"id":"ef73e923-74f7-4f64-b24a-47eab6da603d","sectionKey":"options_table","sectionType":"table_section","heading":"How do the four options compare?","introMarkdown":"The four options split along two lines that drive most decisions: who is your PSTN carrier, and how much infrastructure you have to run yourself.[1] The table sums up those differences, and each option gets a fuller explanation below.","introHtml":"The four options split along two lines that drive most decisions: who is your PSTN carrier, and how much infrastructure you have to run yourself.[1] The table sums up those differences, and each option gets a fuller explanation below.
\n","outroMarkdown":"Every row still assumes a Teams Phone license on each user. The option you pick changes who supplies the numbers and the connection, not whether the license is needed.[1]","outroHtml":"Every row still assumes a Teams Phone license on each user. The option you pick changes who supplies the numbers and the connection, not whether the license is needed.[1]
\n","contentJson":{"rows":[{"cells":["Microsoft Calling Plan","Microsoft","None","Countries where Calling Plan is sold and you want an all-Microsoft setup [1][2]"]},{"cells":["Operator Connect","A certified landline operator","None","Your preferred carrier is in the program and you want it managed for you [1][3]"]},{"cells":["Teams Phone Mobile","A certified mobile operator","A mobile SIM (can be an eSIM)","Staff who want one SIM mobile number that also rings in Teams [1][4]"]},{"cells":["Direct Routing","Any operator you choose","A certified session border controller (SBC)","Any country, keeping a current carrier, or connecting legacy PBX and analog gear [1][5]"]}],"columns":["Option","Who is your carrier","Infrastructure you run","Where it tends to fit"]},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":1},{"id":"9ce31c5d-2327-4bf1-a62f-65d5be43799c","sectionKey":"calling_plan","sectionType":"markdown_section","heading":"When does a Microsoft Calling Plan make sense?","introMarkdown":"A Microsoft Calling Plan fits when having Microsoft sell you the dial tone in your country is acceptable and you would rather not manage a carrier relationship at all.[1][2] With this option Microsoft is your PSTN carrier, supplying the phone numbers, the calling minutes, United States emergency screening, and support under a 99.999% reliability service level agreement, and there is no hardware or session border controller to run.[1][2]\n\nYou buy a Teams Phone license first, then add a Calling Plan license per user, choosing a Domestic, International, or Pay-As-You-Go plan based on how much your users call out.[2] Users in the same country on the same plan share a pool of minutes, so a Domestic plan suits steady in-country calling while Pay-As-You-Go tends to fit lighter or occasional callers.[2] The deciding factor is usually availability, because Calling Plans are sold in a limited set of countries, and the country is set by the location of each user's Microsoft 365 license rather than your billing address.[2][7] A company with users outside that list has to cover those users with one of the other three options.[1][7]","introHtml":"A Microsoft Calling Plan fits when having Microsoft sell you the dial tone in your country is acceptable and you would rather not manage a carrier relationship at all.[1][2] With this option Microsoft is your PSTN carrier, supplying the phone numbers, the calling minutes, United States emergency screening, and support under a 99.999% reliability service level agreement, and there is no hardware or session border controller to run.[1][2]
\nYou buy a Teams Phone license first, then add a Calling Plan license per user, choosing a Domestic, International, or Pay-As-You-Go plan based on how much your users call out.[2] Users in the same country on the same plan share a pool of minutes, so a Domestic plan suits steady in-country calling while Pay-As-You-Go tends to fit lighter or occasional callers.[2] The deciding factor is usually availability, because Calling Plans are sold in a limited set of countries, and the country is set by the location of each user's Microsoft 365 license rather than your billing address.[2][7] A company with users outside that list has to cover those users with one of the other three options.[1][7]
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":2},{"id":"08cc9d84-0f8f-401f-8455-be58fa90de22","sectionKey":"operator_connect","sectionType":"markdown_section","heading":"When is Operator Connect the better fit?","introMarkdown":"Operator Connect fits when you want a specific third-party carrier to run the connection for you, either your current provider or a new one from Microsoft's directory, without buying or managing any voice hardware.[1][3] The operator supplies the PSTN access, phone numbers, emergency screening option, support, and the service level agreement, and you enable them and assign their numbers from the Teams admin center.[1][3] The operator manages the session border controllers, so you avoid running that infrastructure yourself, and deployment is generally quick because the carrier has already certified the connection into Teams.[3]\n\nThis tends to suit an organization whose preferred carrier participates in the program, or one that needs managed calling in a country where Microsoft's own Calling Plan is not sold.[1][3] Coverage is the thing to check first, since each operator serves its own list of countries, so the practical question is whether a participating operator covers the places your people work.[3][8] Users need a Teams Phone license and must be in TeamsOnly mode, though the whole organization does not have to be.[3]","introHtml":"Operator Connect fits when you want a specific third-party carrier to run the connection for you, either your current provider or a new one from Microsoft's directory, without buying or managing any voice hardware.[1][3] The operator supplies the PSTN access, phone numbers, emergency screening option, support, and the service level agreement, and you enable them and assign their numbers from the Teams admin center.[1][3] The operator manages the session border controllers, so you avoid running that infrastructure yourself, and deployment is generally quick because the carrier has already certified the connection into Teams.[3]
\nThis tends to suit an organization whose preferred carrier participates in the program, or one that needs managed calling in a country where Microsoft's own Calling Plan is not sold.[1][3] Coverage is the thing to check first, since each operator serves its own list of countries, so the practical question is whether a participating operator covers the places your people work.[3][8] Users need a Teams Phone license and must be in TeamsOnly mode, though the whole organization does not have to be.[3]
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":3},{"id":"455ab97f-6284-4c51-b24a-80c0698c8d1c","sectionKey":"teams_phone_mobile","sectionType":"markdown_section","heading":"Who should consider Teams Phone Mobile?","introMarkdown":"Teams Phone Mobile fits staff who want a single company mobile number that works as both their cell number and their Teams number, so one line rings on the native mobile dialer and inside Teams at the same time.[1][4] It relies on a certified mobile operator that has completed the integration with Microsoft, and the piece you administer is the mobile SIM, which can be an eSIM.[1][4] The operator provides the PSTN access, numbers, support, and service level agreement, much like Operator Connect but built around a mobile subscription rather than a landline service.[1][4]\n\nThis is aimed at mobile-first roles such as field and sales teams, where carrying one number across the desk phone, the Teams app, and the handset removes the split between a work line and a personal mobile.[4] Availability again decides it, because your mobile provider has to take part in the Teams Phone Mobile program, so confirming that with the carrier comes before any planning.[1][4] In practice it is the least adopted of the four models, so it is worth treating as a fit for specific mobile workers rather than a default for the whole company.[8]","introHtml":"Teams Phone Mobile fits staff who want a single company mobile number that works as both their cell number and their Teams number, so one line rings on the native mobile dialer and inside Teams at the same time.[1][4] It relies on a certified mobile operator that has completed the integration with Microsoft, and the piece you administer is the mobile SIM, which can be an eSIM.[1][4] The operator provides the PSTN access, numbers, support, and service level agreement, much like Operator Connect but built around a mobile subscription rather than a landline service.[1][4]
\nThis is aimed at mobile-first roles such as field and sales teams, where carrying one number across the desk phone, the Teams app, and the handset removes the split between a work line and a personal mobile.[4] Availability again decides it, because your mobile provider has to take part in the Teams Phone Mobile program, so confirming that with the carrier comes before any planning.[1][4] In practice it is the least adopted of the four models, so it is worth treating as a fit for specific mobile workers rather than a default for the whole company.[8]
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":4},{"id":"45f12f4c-7f22-4c76-a69b-66daf2b2b8a3","sectionKey":"direct_routing","sectionType":"markdown_section","heading":"When is Direct Routing worth the extra work?","introMarkdown":"Direct Routing fits when you need to keep a specific carrier, operate in a country where the managed options are not available, or connect Teams to existing phone equipment, and you accept running more infrastructure in return for that flexibility.[1][5] It connects almost any PSTN trunk to Teams through a certified session border controller that you, an integrator, or a Direct-Routing-as-a-Service provider procures and manages, and it is the one model that works in any country.[1][5] It also interoperates with third-party PBXs and analog devices such as overhead paging, which is often the reason a business with legacy gear chooses it.[1][5]\n\nThe cost of that flexibility is responsibility, since the SBC brings certificate management, DNS and firewall configuration, call-routing policies in Teams, and the last-mile circuit into the SBC, so it asks more of your IT team or partner than the other options do.[1][5] Direct Routing is also the only model that can keep local PSTN calls working through a Survivable Branch Appliance if the connection to the Microsoft cloud is interrupted, which matters for sites that cannot tolerate losing the phones during an outage.[1][11] Where the extra control is not needed, a managed option usually reaches a working state faster.[9][11]","introHtml":"Direct Routing fits when you need to keep a specific carrier, operate in a country where the managed options are not available, or connect Teams to existing phone equipment, and you accept running more infrastructure in return for that flexibility.[1][5] It connects almost any PSTN trunk to Teams through a certified session border controller that you, an integrator, or a Direct-Routing-as-a-Service provider procures and manages, and it is the one model that works in any country.[1][5] It also interoperates with third-party PBXs and analog devices such as overhead paging, which is often the reason a business with legacy gear chooses it.[1][5]
\nThe cost of that flexibility is responsibility, since the SBC brings certificate management, DNS and firewall configuration, call-routing policies in Teams, and the last-mile circuit into the SBC, so it asks more of your IT team or partner than the other options do.[1][5] Direct Routing is also the only model that can keep local PSTN calls working through a Survivable Branch Appliance if the connection to the Microsoft cloud is interrupted, which matters for sites that cannot tolerate losing the phones during an outage.[1][11] Where the extra control is not needed, a managed option usually reaches a working state faster.[9][11]
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":5},{"id":"291ab7e1-dd07-47ee-90c1-01e0ed7e9068","sectionKey":"decision_criteria","sectionType":"markdown_section","heading":"Which questions actually decide the choice?","introMarkdown":"Four practical questions settle most of the decision: where your users are, whether you want to keep a current carrier, how much infrastructure you can run, and what your emergency-calling and continuity requirements are.[1] Working through them in order usually points to one or two options per group of users rather than a single company-wide answer.[1]\n\n### Are the managed options sold where your users are?\n\nStart with geography, because Microsoft Calling Plans are sold only in a limited set of countries, and each Operator Connect or Teams Phone Mobile carrier covers its own list.[2][3][7] If a managed option covers all your locations, it removes the most infrastructure from your plate; if it does not, Direct Routing is the model that reaches any country.[1][5]\n\n### Do you need to keep your existing carrier or numbers?\n\nIf a current carrier contract or a specific operator relationship has to stay in place, that narrows the field quickly.[1] Operator Connect keeps a preferred carrier when that carrier is in the program, while Direct Routing keeps any carrier at the cost of running the connection yourself.[1][3][5] A Microsoft Calling Plan replaces the carrier entirely, so it only fits when you are content to move that role to Microsoft.[2]\n\n### How much telephony infrastructure do you want to run?\n\nThe options line up on a scale from fully managed to fully self-run.[9][10] Calling Plan and Operator Connect leave no SBC for you to manage, Teams Phone Mobile adds only the mobile SIM, and Direct Routing puts the session border controller and its upkeep on you or a partner.[1] Matching that scale to the telephony skills you actually have in-house, or the partner you can call on, keeps the deployment realistic.[9][10]\n\n### What are your emergency-calling and uptime needs?\n\nEmergency calling and outage tolerance differ by option and can be decisive in regulated or safety-sensitive settings.[1] A Microsoft Calling Plan includes United States emergency screening and a Teams-admin-managed registered address, the operator-led options offer emergency screening as an option they manage, and Direct Routing supports dynamic emergency calling but needs extra configuration and does not support a registered address.[1] If a site must keep calling during a cloud interruption, only Direct Routing with a Survivable Branch Appliance provides that local fallback.[1][11]","introHtml":"Four practical questions settle most of the decision: where your users are, whether you want to keep a current carrier, how much infrastructure you can run, and what your emergency-calling and continuity requirements are.[1] Working through them in order usually points to one or two options per group of users rather than a single company-wide answer.[1]
\nStart with geography, because Microsoft Calling Plans are sold only in a limited set of countries, and each Operator Connect or Teams Phone Mobile carrier covers its own list.[2][3][7] If a managed option covers all your locations, it removes the most infrastructure from your plate; if it does not, Direct Routing is the model that reaches any country.[1][5]
\nIf a current carrier contract or a specific operator relationship has to stay in place, that narrows the field quickly.[1] Operator Connect keeps a preferred carrier when that carrier is in the program, while Direct Routing keeps any carrier at the cost of running the connection yourself.[1][3][5] A Microsoft Calling Plan replaces the carrier entirely, so it only fits when you are content to move that role to Microsoft.[2]
\nThe options line up on a scale from fully managed to fully self-run.[9][10] Calling Plan and Operator Connect leave no SBC for you to manage, Teams Phone Mobile adds only the mobile SIM, and Direct Routing puts the session border controller and its upkeep on you or a partner.[1] Matching that scale to the telephony skills you actually have in-house, or the partner you can call on, keeps the deployment realistic.[9][10]
\nEmergency calling and outage tolerance differ by option and can be decisive in regulated or safety-sensitive settings.[1] A Microsoft Calling Plan includes United States emergency screening and a Teams-admin-managed registered address, the operator-led options offer emergency screening as an option they manage, and Direct Routing supports dynamic emergency calling but needs extra configuration and does not support a registered address.[1] If a site must keep calling during a cloud interruption, only Direct Routing with a Survivable Branch Appliance provides that local fallback.[1][11]
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":6},{"id":"d0d92ed9-93ea-4721-b547-10ff624e5585","sectionKey":"combine_options","sectionType":"markdown_section","heading":"Can you combine more than one option?","introMarkdown":"Yes, one tenant can use several PSTN connectivity types at once, and mixing them is a normal design for anything beyond a single-country setup.[1] Microsoft's own guidance describes starting with Calling Plans and Shared Calling for everyone, then layering more specific options by persona, such as Teams Phone Mobile for mobile workers, Operator Connect for knowledge workers, and Direct Routing for people in regions the other options do not cover.[1]\n\nYou can also mix options for a single user. A user assigned a Calling Plan or an Operator Connect number can still route some calls through Direct Routing, which is commonly set up so that calls to a third-party PBX stay on the enterprise network instead of going out to the PSTN.[5] Enterprises with users in many countries often end up here by necessity, running one managed option where a carrier has strong coverage and Direct Routing where it does not, or where local integration and compliance rules require an on-premises connection.[8][10]","introHtml":"Yes, one tenant can use several PSTN connectivity types at once, and mixing them is a normal design for anything beyond a single-country setup.[1] Microsoft's own guidance describes starting with Calling Plans and Shared Calling for everyone, then layering more specific options by persona, such as Teams Phone Mobile for mobile workers, Operator Connect for knowledge workers, and Direct Routing for people in regions the other options do not cover.[1]
\nYou can also mix options for a single user. A user assigned a Calling Plan or an Operator Connect number can still route some calls through Direct Routing, which is commonly set up so that calls to a third-party PBX stay on the enterprise network instead of going out to the PSTN.[5] Enterprises with users in many countries often end up here by necessity, running one managed option where a carrier has strong coverage and Direct Routing where it does not, or where local integration and compliance rules require an on-premises connection.[8][10]
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":7},{"id":"d053ccf7-8f86-4444-a181-e09291164553","sectionKey":"trade_offs","sectionType":"markdown_section","heading":"Trade-offs and limits to plan around","introMarkdown":"Each option carries limits that are easier to plan for than to discover later, and most of them touch cost, coverage, or who carries the support burden.[1][6]\n\n### The phone license is not the whole bill\n\nA Teams Phone license on its own cannot call the outside world, so the real cost includes the PSTN option on top of it.[1][2] Microsoft lists Teams Phone Standard at $10.00 per user per month, while a bundle that adds a domestic Calling Plan runs about $17.00 and a domestic-and-international bundle about $34.00, and Operator Connect or Direct Routing carry their own carrier and, for Direct Routing, SBC costs.[6] Budgeting only for the phone license understates what a working deployment costs.[6]\n\n### Coverage and carrier participation vary\n\nMicrosoft Calling Plan availability is limited by country, and both Operator Connect and Teams Phone Mobile depend on a specific carrier taking part and covering your locations, so coverage can be the constraint that removes an option before cost ever enters the picture.[2][3][7] Confirming availability early for every country you operate in avoids designing around an option you cannot actually buy.[7][8]\n\n### Direct Routing shifts work onto you\n\nThe flexibility of Direct Routing comes with the ongoing upkeep of the session border controller, its certificates, and its routing configuration, whether your team runs it or a Direct-Routing-as-a-Service provider does.[1][5] That upkeep is manageable, but it is a standing responsibility rather than a one-time setup, so it belongs in the decision rather than as an afterthought.[5][9]\n\n### Continuity and emergency calling need attention\n\nBecause Teams calls travel over the internet, a managed cloud option depends on the connection to Microsoft staying up, and only Direct Routing with a Survivable Branch Appliance keeps local calling during a cloud interruption.[1][11] Emergency-calling setup also differs by option, so the registered-address and dynamic-location details are worth confirming per site, especially for people who move between locations.[1]","introHtml":"Each option carries limits that are easier to plan for than to discover later, and most of them touch cost, coverage, or who carries the support burden.[1][6]
\nA Teams Phone license on its own cannot call the outside world, so the real cost includes the PSTN option on top of it.[1][2] Microsoft lists Teams Phone Standard at $10.00 per user per month, while a bundle that adds a domestic Calling Plan runs about $17.00 and a domestic-and-international bundle about $34.00, and Operator Connect or Direct Routing carry their own carrier and, for Direct Routing, SBC costs.[6] Budgeting only for the phone license understates what a working deployment costs.[6]
\nMicrosoft Calling Plan availability is limited by country, and both Operator Connect and Teams Phone Mobile depend on a specific carrier taking part and covering your locations, so coverage can be the constraint that removes an option before cost ever enters the picture.[2][3][7] Confirming availability early for every country you operate in avoids designing around an option you cannot actually buy.[7][8]
\nThe flexibility of Direct Routing comes with the ongoing upkeep of the session border controller, its certificates, and its routing configuration, whether your team runs it or a Direct-Routing-as-a-Service provider does.[1][5] That upkeep is manageable, but it is a standing responsibility rather than a one-time setup, so it belongs in the decision rather than as an afterthought.[5][9]
\nBecause Teams calls travel over the internet, a managed cloud option depends on the connection to Microsoft staying up, and only Direct Routing with a Survivable Branch Appliance keeps local calling during a cloud interruption.[1][11] Emergency-calling setup also differs by option, so the registered-address and dynamic-location details are worth confirming per site, especially for people who move between locations.[1]
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":8},{"id":"832ce305-c89e-4adb-80f7-ec425b911803","sectionKey":"what_it_is_not","sectionType":"markdown_section","heading":"What choosing a PSTN option is not","introMarkdown":"Choosing a PSTN option is a separate decision from buying the Teams Phone license, and a few common mix-ups are worth clearing up before you commit.[1]\n\n### It is not the same as the Teams Phone license\n\nThe Teams Phone license enables the calling features but does not connect you to the outside phone network on its own.[1][2] The PSTN option is the second piece that supplies the numbers and the route to landlines and mobiles.[1]\n\n### A Microsoft Calling Plan is not the only way\n\nA Microsoft Calling Plan is one of the four options, not a requirement.[1] You can run Teams Phone entirely on Operator Connect, Teams Phone Mobile, or Direct Routing and never buy a Microsoft Calling Plan, which matters most in countries where Calling Plans are not sold.[1][2]\n\n### It is not a permanent, one-time commitment\n\nThe choice is not locked in, since a tenant can add, change, or combine connectivity types over time and in any order.[1] An option chosen for one group of users does not bind the rest of the organization, so the decision can grow with the deployment.[1]\n\n### Operator Connect and Direct Routing are not a quality ranking\n\nNeither managed nor self-run connectivity is inherently better calling; they differ in who runs the connection and how much control you keep, not in call quality.[9][10] The right pick depends on coverage, existing carrier relationships, and the infrastructure you want to own, which is why the same feature can be the deciding factor for one organization and irrelevant to another.[1][9]","introHtml":"Choosing a PSTN option is a separate decision from buying the Teams Phone license, and a few common mix-ups are worth clearing up before you commit.[1]
\nThe Teams Phone license enables the calling features but does not connect you to the outside phone network on its own.[1][2] The PSTN option is the second piece that supplies the numbers and the route to landlines and mobiles.[1]
\nA Microsoft Calling Plan is one of the four options, not a requirement.[1] You can run Teams Phone entirely on Operator Connect, Teams Phone Mobile, or Direct Routing and never buy a Microsoft Calling Plan, which matters most in countries where Calling Plans are not sold.[1][2]
\nThe choice is not locked in, since a tenant can add, change, or combine connectivity types over time and in any order.[1] An option chosen for one group of users does not bind the rest of the organization, so the decision can grow with the deployment.[1]
\nNeither managed nor self-run connectivity is inherently better calling; they differ in who runs the connection and how much control you keep, not in call quality.[9][10] The right pick depends on coverage, existing carrier relationships, and the infrastructure you want to own, which is why the same feature can be the deciding factor for one organization and irrelevant to another.[1][9]
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":9},{"id":"00934471-2e57-4207-9709-0d89bd202091","sectionKey":"contributor_perspective","sectionType":"markdown_section","heading":"How this answer was researched","introMarkdown":"The definitions, the four connectivity models, the comparison details, and the decision criteria here come primarily from Microsoft's own Teams documentation on Microsoft Learn, which is the authoritative source for how Teams Phone connects to the PSTN and what each option manages.[1][2][3][4][5][7] Pricing reflects Microsoft's published figures on its Teams Phone product page as of the verification date, and independent telecom and integrator sources were used to corroborate market details such as country coverage, carrier participation, relative adoption, and the practical trade-offs of running Direct Routing versus a managed option.[6][8][9][10][11] Microsoft changes Teams licensing, pricing, availability, and feature details regularly, so the specific figures, country lists, and option names here reflect what the cited pages stated when they were checked. Practitioners who deploy, administer, or support Teams Phone connectivity at scale are welcome to suggest corrections or additions, which are checked against Microsoft's primary documentation before any update.","introHtml":"The definitions, the four connectivity models, the comparison details, and the decision criteria here come primarily from Microsoft's own Teams documentation on Microsoft Learn, which is the authoritative source for how Teams Phone connects to the PSTN and what each option manages.[1][2][3][4][5][7] Pricing reflects Microsoft's published figures on its Teams Phone product page as of the verification date, and independent telecom and integrator sources were used to corroborate market details such as country coverage, carrier participation, relative adoption, and the practical trade-offs of running Direct Routing versus a managed option.[6][8][9][10][11] Microsoft changes Teams licensing, pricing, availability, and feature details regularly, so the specific figures, country lists, and option names here reflect what the cited pages stated when they were checked. Practitioners who deploy, administer, or support Teams Phone connectivity at scale are welcome to suggest corrections or additions, which are checked against Microsoft's primary documentation before any update.
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":"This answer was written and reviewed by the AnswerStack Editorial Team, which has no commercial stake in the products, companies, or methods discussed. Every claim is cited inline and verified on the dates shown.","noteHtml":"This answer was written and reviewed by the AnswerStack Editorial Team, which has no commercial stake in the products, companies, or methods discussed. Every claim is cited inline and verified on the dates shown.
\n","sortOrder":10}],"citations":[{"title":"Microsoft - PSTN connectivity options","url":"https://learn.microsoft.com/en-us/microsoftteams/pstn-connectivity","excerpt":"In order to use PSTN telephony services with Teams Phone, the user account must be licensed with the Teams Phone application and also be equipped with a PSTN solution from your PSTN service provider of choice.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-17T00:00:00","supportsText":"The four PSTN connectivity models and their differences, the per-option comparison table (carrier, infrastructure, emergency screening, registered address, survivability), the license-plus-PSTN requirement, the 'could be a good solution if' decision criteria, combining options by persona, and Surviv","domain":"learn.microsoft.com","publisherName":"Microsoft"},{"title":"Microsoft Teams Calling Plans","url":"https://learn.microsoft.com/en-us/microsoftteams/calling-plans-for-office-365","excerpt":"This solution is the simplest option that connects Teams Phone to the PSTN for external calling. With this option, Microsoft acts as your PSTN carrier.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-17T00:00:00","supportsText":"Microsoft acts as your PSTN carrier and this is the simplest external-calling option; Domestic, International, and Pay-As-You-Go plan types; buy a Teams Phone license first then a Calling Plan; minute pooling; country determined by the user's license location; availability limited by country","domain":"learn.microsoft.com","publisherName":"Microsoft Learn"},{"title":"Microsoft - Plan for Operator Connect","url":"https://learn.microsoft.com/en-us/microsoftteams/operator-connect-plan","excerpt":"Operator-managed infrastructure. Your operator manages the PSTN calling services and Session Border Controllers (SBCs), allowing you to save on hardware purchase and management.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-17T00:00:00","supportsText":"Operator keeps a preferred carrier or finds a new one, operator-managed SBC infrastructure, faster deployment through the Teams admin center, operator support and shared SLA; requirements are a Teams Phone license and TeamsOnly mode; operator directory covers its own countries","domain":"learn.microsoft.com","publisherName":"Microsoft"},{"title":"Plan for Teams Phone Mobile - Microsoft Teams","url":"https://learn.microsoft.com/en-us/microsoftteams/operator-connect-mobile-plan","excerpt":"With Teams Phone Mobile, a user's SIM-enabled phone number is also their Teams phone number.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-17T00:00:00","supportsText":"A SIM-enabled mobile number becomes the Teams phone number as a single-number solution; requires a certified mobile operator; aimed at mobile and field workforces; the mobile SIM (can be eSIM) is what the customer administers; requires a Teams Phone license and TeamsOnly mode","domain":"learn.microsoft.com","publisherName":"Microsoft Learn"},{"title":"Plan Direct Routing - Microsoft Teams","url":"https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan","excerpt":"Direct Routing lets you connect a supported, customer-provided Session Border Controller (SBC) to Microsoft Teams Phone.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-17T00:00:00","supportsText":"Direct Routing connects a customer-provided certified SBC to Teams Phone, works with virtually any PSTN trunk in any country, interoperates with third-party PBX and analog devices, and fits when Calling Plan is unavailable or an existing carrier contract must stay; SBC upkeep (certificates, domains,","domain":"learn.microsoft.com","publisherName":"Microsoft Learn"},{"title":"Microsoft Teams Phone","url":"https://www.microsoft.com/en-us/microsoft-teams/microsoft-teams-phone","excerpt":"Teams Phone Standard $10.00 user/month, paid yearly. 99.999% uptime SLA.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-17T00:00:00","supportsText":"Teams Phone Standard at $10.00 per user per month paid yearly, Teams Phone with domestic Calling Plan about $17.00, domestic and international bundle about $34.00, 99.999% uptime SLA, and the four PSTN connectivity options listed on the product page","domain":"microsoft.com","publisherName":"Microsoft"},{"title":"Country and region availability for Audio Conferencing and Calling Plans","url":"https://learn.microsoft.com/en-us/microsoftteams/country-and-region-availability-for-audio-conferencing-and-calling-plans/country-and-region-availability-for-audio-conferencing-and-calling-plans","excerpt":"Use the drop-down list at the top of the page to search for a country or region and find out if Calling Plans are available for purchase for your country/region.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-17T00:00:00","supportsText":"Calling Plan availability must be checked per country or region; the country is based on the location of the user's Microsoft 365 license; a per-country lookup determines whether Calling Plans can be purchased","domain":"learn.microsoft.com","publisherName":"Microsoft Learn"},{"title":"Microsoft Teams Phone & PSTN Connectivity: 4 Options Enterprise IT Need to Know","url":"https://www.pure-ip.com/blog/microsoft-teams-phone-pstn-connectivity-4-options-enterprise-it-need-to-know","excerpt":"109 operators across 106 countries as of mid-2025.","quoteText":null,"sourceRole":"INDEPENDENT","verifiedAt":"2026-07-17T00:00:00","supportsText":"Independent corroboration that Calling Plans reach roughly 34 countries; that Operator Connect had about 109 operators across 106 countries as of mid-2025; that Teams Phone Mobile has low relative adoption; and that global organizations typically combine Operator Connect with Direct Routing by regio","domain":"pure-ip.com","publisherName":"Pure IP"},{"title":"Microsoft Teams: Calling Plans Vs Operator Connect Vs Direct Routing","url":"https://www.communicationsquare.com/news/calling-plans-vs-operator-connect-vs-direct-routing/","excerpt":"Calling plans offer the least amount of customization, as businesses are limited to the features and options provided by the telecommunications provider.","quoteText":null,"sourceRole":"INDEPENDENT","verifiedAt":"2026-07-17T00:00:00","supportsText":"Independent corroboration of the simplicity-versus-control spectrum: Calling Plan is simplest with least customization, Direct Routing gives the most control but requires an SBC and more setup, and managed options sit in between","domain":"communicationsquare.com","publisherName":"Communication Square"},{"title":"Microsoft Teams Phone PSTN Connectivity Options","url":"https://ceriumnetworks.com/microsoft-teams-phone-pstn-connectivity-options/","excerpt":"There are no carrier negotiations, SBC deployments, or complex telecom integrations to manage.","quoteText":null,"sourceRole":"INDEPENDENT","verifiedAt":"2026-07-17T00:00:00","supportsText":"Independent corroboration that the choice is a simplicity-versus-control trade-off, that only Direct Routing gives full carrier independence and legacy integration, and that many enterprises run hybrid environments with different PSTN models for different users, locations, or business units","domain":"ceriumnetworks.com","publisherName":"Cerium Networks"},{"title":"Microsoft Operator Connect vs. Direct Routing: The Inside Story","url":"https://www.atlantech.net/blog/operator-connect-microsoft-teams-vs-direct-routing","excerpt":null,"quoteText":null,"sourceRole":"SUPPORTING","verifiedAt":"2026-07-17T00:00:00","supportsText":"Business-facing corroboration that Operator Connect is carrier-managed with minimal IT involvement while Direct Routing requires customer-run SBCs, and that Direct Routing enables local SBC failover so calling continues during a Teams cloud outage; corroborated on survivability by [1] and on the man","domain":"atlantech.net","publisherName":"Atlantech Online"}],"revisions":[],"relatedAnswers":[{"id":"9cfa6183-815b-4644-861d-2bfe543492cc","slug":"how-does-teams-phone-work","question":"How does Teams Phone work?","publishedAt":"2026-07-18T03:47:27.534","confidenceScore":93,"confidenceLabel":"High","industry":{"id":"ff619d7c-d7d7-485e-a05a-53fba07f33ed","slug":"telecommunications","label":"Telecommunications","description":"Business voice, fiber, UCaaS, and network services"},"topic":{"slug":"teams-phone","label":"Teams Phone","description":"Microsoft Teams Phone: licensing, PSTN connectivity, calling plans, and setup.","schemaKind":null},"contributor":{"id":"ec39deab-44fe-48d8-9029-fefe993ab85a","slug":"answer-stack","displayName":"AnswerStack","websiteUrl":null},"snippet":"Teams Phone turns Microsoft 365 into a cloud phone system: a call-control service in the cloud acts as the PBX, internal calls run over the internet, and a Teams Phone license plus a PSTN connection (Microsoft Calling Plan, Operator Connect, Teams Phone Mobile, or Direct Routing) let users dial real phone numbers. Admins assign numbers, voice enable users, and build auto attendants and call queues, while call audio flows over the most direct path it can find, encrypted with SRTP.","url":"/q/how-does-teams-phone-work"},{"id":"67fc8518-2dba-4c3b-8029-0a39c59afd28","slug":"what-is-the-difference-between-teams-phone-and-a-calling-plan","question":"What is the difference between Teams Phone and a Calling Plan?","publishedAt":"2026-07-18T03:41:44.225","confidenceScore":95,"confidenceLabel":"High","industry":{"id":"ff619d7c-d7d7-485e-a05a-53fba07f33ed","slug":"telecommunications","label":"Telecommunications","description":"Business voice, fiber, UCaaS, and network services"},"topic":{"slug":"teams-phone","label":"Teams Phone","description":"Microsoft Teams Phone: licensing, PSTN connectivity, calling plans, and setup.","schemaKind":null},"contributor":{"id":"ec39deab-44fe-48d8-9029-fefe993ab85a","slug":"answer-stack","displayName":"AnswerStack","websiteUrl":null},"snippet":"Teams Phone and a Microsoft Calling Plan are two different purchases that most organizations buy together. Teams Phone is the cloud phone system, the per-user license that adds PBX features like auto attendants, call queues, and PSTN dialing. A Calling Plan is one of four ways to connect that phone system to the public phone network; it makes Microsoft your carrier and supplies the numbers and minutes. Internal Teams calls need neither, and a Calling Plan cannot work without a Teams Phone license underneath it.","url":"/q/what-is-the-difference-between-teams-phone-and-a-calling-plan"},{"id":"dc0dd213-a7d5-4cd3-95e3-5457b9308922","slug":"what-teams-phone-license-do-i-need","question":"What Teams Phone license do I need?","publishedAt":"2026-07-18T03:41:33.762","confidenceScore":93,"confidenceLabel":"High","industry":{"id":"ff619d7c-d7d7-485e-a05a-53fba07f33ed","slug":"telecommunications","label":"Telecommunications","description":"Business voice, fiber, UCaaS, and network services"},"topic":{"slug":"teams-phone","label":"Teams Phone","description":"Microsoft Teams Phone: licensing, PSTN connectivity, calling plans, and setup.","schemaKind":null},"contributor":{"id":"ec39deab-44fe-48d8-9029-fefe993ab85a","slug":"answer-stack","displayName":"AnswerStack","websiteUrl":null},"snippet":"Teams Phone licensing comes in layers. Every user needs a base Microsoft 365 or Teams subscription, then a Teams Phone license, then a PSTN connection for external calls. E5 plans already include Teams Phone; lower tiers add Teams Phone Standard at about $10 per user per month. A Microsoft Calling Plan, Operator Connect, Teams Phone Mobile, or Direct Routing supplies the outside line, and only the Microsoft Calling Plan route needs its own extra license.","url":"/q/what-teams-phone-license-do-i-need"},{"id":"856a2341-d0c5-4496-a8d2-d97388060c1c","slug":"how-much-does-teams-phone-cost","question":"How much does Teams Phone cost?","publishedAt":"2026-07-18T03:40:01.318","confidenceScore":92,"confidenceLabel":"High","industry":{"id":"ff619d7c-d7d7-485e-a05a-53fba07f33ed","slug":"telecommunications","label":"Telecommunications","description":"Business voice, fiber, UCaaS, and network services"},"topic":{"slug":"teams-phone","label":"Teams Phone","description":"Microsoft Teams Phone: licensing, PSTN connectivity, calling plans, and setup.","schemaKind":null},"contributor":{"id":"ec39deab-44fe-48d8-9029-fefe993ab85a","slug":"answer-stack","displayName":"AnswerStack","websiteUrl":null},"snippet":"Teams Phone Standard is $10 per user per month for cloud PBX features with no calling minutes. Microsoft's bundled Calling Plans run $17 (3,000 pooled domestic minutes) or $34 (adds international). Microsoft 365 E5 already includes the phone-system license. Once you add PSTN connectivity, resource accounts, and a base Microsoft 365 license, independent estimates put the real all-in cost near $25 to $35 per user per month.","url":"/q/how-much-does-teams-phone-cost"}],"contributorStats":{"verifiedAnswers":224,"openDisputes":0},"schemaJson":{"@context":"https://schema.org","@type":"Question","name":"How do I choose a PSTN connectivity option for Teams Phone?","text":"How do I choose a PSTN connectivity option for Teams Phone?","url":"https://www.answerstack.io/q/how-do-i-choose-a-pstn-connectivity-option-for-teams-phone","answerCount":1,"datePublished":"2026-07-18T03:43:05.249","author":{"@type":"Person","name":"AnswerStack Editorial Team","worksFor":{"@type":"Organization","name":"AnswerStack"},"url":"https://www.answerstack.io/contributors/answer-stack"},"about":[{"@type":"Thing","name":"Teams Phone"},{"@type":"Thing","name":"Telecommunications"}],"acceptedAnswer":{"@type":"Answer","text":"You choose a Teams Phone PSTN connectivity option by matching one of Microsoft's four models to where your users are, whether you want to keep an existing carrier, and how much of the telephony plumbing you are willing to run yourself.[1] A Microsoft Calling Plan makes Microsoft your carrier and is the simplest setup, but it is sold in only a limited set of countries.[1][2] Operator Connect and Teams Phone Mobile hand the carrier role to a certified operator that manages the connection for you, with Teams Phone Mobile built around a single SIM-based mobile number that also rings in Teams.[1][3][4] Direct Routing works in any country and connects almost any carrier through a session border controller you or a partner manage, which is why organizations pick it to keep a current carrier or connect legacy PBX and analog equipment.[1][5] One tenant can use several of these at once, so the practical decision is often per country or per type of worker rather than a single choice for the whole company.[1]","url":"https://www.answerstack.io/q/how-do-i-choose-a-pstn-connectivity-option-for-teams-phone","upvoteCount":0,"datePublished":"2026-07-18T03:43:05.249","dateModified":"2026-07-17T00:00:00","author":{"@type":"Person","name":"AnswerStack Editorial Team","worksFor":{"@type":"Organization","name":"AnswerStack"},"url":"https://www.answerstack.io/contributors/answer-stack"},"citation":[{"@type":"CreativeWork","name":"Microsoft - PSTN connectivity options","url":"https://learn.microsoft.com/en-us/microsoftteams/pstn-connectivity"},{"@type":"CreativeWork","name":"Microsoft Teams Calling Plans","url":"https://learn.microsoft.com/en-us/microsoftteams/calling-plans-for-office-365"},{"@type":"CreativeWork","name":"Microsoft - Plan for Operator Connect","url":"https://learn.microsoft.com/en-us/microsoftteams/operator-connect-plan"},{"@type":"CreativeWork","name":"Plan for Teams Phone Mobile - Microsoft Teams","url":"https://learn.microsoft.com/en-us/microsoftteams/operator-connect-mobile-plan"},{"@type":"CreativeWork","name":"Plan Direct Routing - Microsoft Teams","url":"https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan"},{"@type":"CreativeWork","name":"Microsoft Teams Phone","url":"https://www.microsoft.com/en-us/microsoft-teams/microsoft-teams-phone"},{"@type":"CreativeWork","name":"Country and region availability for Audio Conferencing and Calling Plans","url":"https://learn.microsoft.com/en-us/microsoftteams/country-and-region-availability-for-audio-conferencing-and-calling-plans/country-and-region-availability-for-audio-conferencing-and-calling-plans"},{"@type":"CreativeWork","name":"Microsoft Teams Phone & PSTN Connectivity: 4 Options Enterprise IT Need to Know","url":"https://www.pure-ip.com/blog/microsoft-teams-phone-pstn-connectivity-4-options-enterprise-it-need-to-know"},{"@type":"CreativeWork","name":"Microsoft Teams: Calling Plans Vs Operator Connect Vs Direct Routing","url":"https://www.communicationsquare.com/news/calling-plans-vs-operator-connect-vs-direct-routing/"},{"@type":"CreativeWork","name":"Microsoft Teams Phone PSTN Connectivity Options","url":"https://ceriumnetworks.com/microsoft-teams-phone-pstn-connectivity-options/"},{"@type":"CreativeWork","name":"Microsoft Operator Connect vs. Direct Routing: The Inside Story","url":"https://www.atlantech.net/blog/operator-connect-microsoft-teams-vs-direct-routing"}]}}}