Cloud Telephony (VoIP & Cloud PBX)
Microsoft Teams Phone
Rest of world Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Microsoft Corporation · www.microsoft.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Microsoft Teams Phone at a glance
- Vendor
- Microsoft Corporation
- Headquarters
- Not stated on the vendor’s pages as of 5 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 5 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 5 Nov 2026
- Panel verdict
- The AI panel rates Microsoft Teams Phone 2/5, the mean of 6 judges. Microsoft Teams Phone is a cloud telephony add-on to Microsoft 365, reaching the public network through a Microsoft calling plan, Operator Connect, Direct Routing via a certified session border controller, or Teams Phone Mobile. how scores are made
- As of
- Vendor pages captured 5 Nov 2026; evaluated by the panel 6 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Microsoft Teams Phone is a cloud telephony add-on to Microsoft 365, reaching the public network through a Microsoft calling plan, Operator Connect, Direct Routing via a certified session border controller, or Teams Phone Mobile. It scores highest on integration and administration and network and compliance, citing a documented Graph API, PowerShell automation, voice policies at global, group and user level, a 99.999% reliability SLA, and SIP/TLS with SRTP. It is weakest on pricing transparency: the licence structure — three calling plan types, pooled minutes, pay-as-you-go funded by Communication Credits — is public, but no per-user price appears, so a year's bill cannot be computed. Contact center follows at 3-4: call queues and auto attendants are included, with no public information on wallboards, listen and whisper, per-agent statistics or dialers. Apps and devices spreads 4-6, higher scores crediting Direct Routing and Operator Connect depth, lower ones finding no public information on device makers and provisioning. Sovereignty sits at 4: the EU data boundary names fifteen data centre countries while allowing limited transfers outside it; the vendor is Microsoft Corporation, USA.
Speaks for it
- Number porting, new number purchase, auto attendants, call queues, cloud voicemail, forwarding, transfer and caller ID are documented
- Direct Routing connects an existing PBX and third-party carrier through a Microsoft-certified session border controller
- A documented Graph REST API with SDKs and change notifications sits beside PowerShell provisioning and voice policies at global, group and user level
- A 99.999% reliability service level agreement is published for the Microsoft calling plan, alongside SIP/TLS, SRTP and named codecs
- Teams Phone Mobile makes a user's SIM number their Teams number through certified mobile operators, with calls in the Teams desktop and mobile clients
Held against it
- No per-user price, per-minute rate or number, porting or device cost appears on the captured pages
- We found no public information on wallboards, listen and whisper, per-agent statistics, callbacks or dialers for agents
- Emergency calling is documented as an emergency screening service in the U.S.
- We found no public information on an EU contracting entity, a data processing agreement or a subprocessor list, and the EU data boundary allows limited transfers outside it
- We found no public information on CRM click-to-call, call logging, single sign-on, SCIM provisioning or audit logs
Best for
- You already run Microsoft 365 and want calling inside the Teams clients, administered through PowerShell and the Graph API
- You must keep an existing PBX or your own carrier contracts — Direct Routing connects them through a Microsoft-certified session border controller
- You need ported numbers with auto attendants and call queues for office calling rather than agent supervision
- Your mobile staff want one number — Teams Phone Mobile makes the SIM number the Teams number through certified mobile operators
Avoid if
- You run an agent-heavy contact center — the captured pages document call queues, auto attendants and a Dynamics 365 integration, with no public information on wallboards, live monitoring or per-agent statistics
- You must compute an annual bill from public prices before signing — ask the vendor: the public pages we read do not show it
- You require a stated EU contracting entity and no transfers outside the EU data boundary — the vendor is Microsoft Corporation in the USA and the boundary document states that limited circumstances allow transfers outside it
- You need confirmed emergency routing in Germany — the captured pages describe an emergency screening service in the U.S.
The scores
| Criterion | Panel median |
|---|---|
| Calling, numbers & call routing | 2.5 of 5 |
| Apps, desk phones & Microsoft Teams | 2.5 of 5 |
| Call centre, analytics & AI | 1.5 of 5 |
| CRM integration, API & administration | 3 of 5 |
| Reliability, call security & telecoms compliance | 2.5 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 1 of 5 |
Calling, numbers & call routing
Show reasoningHide reasoning
How this is scored
What the phone system does with a call: local geographic numbers in the customer's own area code and in other countries, number blocks and porting of existing numbers, extensions, IVR menus, queues, ring groups and hunt groups, time-based and holiday routing, call forwarding and transfer, voicemail to email, fax to email, conference calls, call recording, call park and pickup, busy lamp fields, caller ID per user or team, and emergency calls (110 and 112) with the caller's location.
0 — Places no phone calls on the public telephone network; a chat or meeting tool with internal calling only.
3 — Phone numbers and extensions with forwarding and voicemail; IVR, queues, time-based routing and porting are basic or not described.
5 — Local numbers in the customer's area code with porting documented, IVR menus, queues and ring groups, time-based and holiday routing, voicemail to email, call transfer and pickup, call recording, fax or fax to email, and emergency calling described.
8 — Number blocks and international numbers in many countries, a visual call flow editor, skills or priority routing, call park and busy lamp fields, recording rules per user or queue with consent announcements, emergency calls with a registered location per user or site, and the porting process and its timelines documented.
10 — Call handling a large multi-site company runs on: every feature above with number provisioning and porting by API, routing by caller data from the CRM, location-aware emergency calling for home offices, and the full feature set documented per plan with its limits.
The Office Manager
Porting our thirty-year-old number is documented — purchase new numbers or port existing ones, with a tenant-level review most commonly finished within three business days — and auto attendants for the greeting and call queues are included alongside cloud voicemail, forwarding, transfer and caller ID. What the captured pages leave open for a German office: time-based and holiday routing, ring groups, voicemail delivered to email, recording, fax, and how 110/112 emergency calls are handled (only a U.S. emergency screening service is described). 2 5 6 7
The IT Administrator
Auto attendants, call queues, cloud voicemail, call forwarding, transfer and caller ID are documented, and both new numbers and porting of existing numbers are described, with a KYC review for number acquisition stated at up to three business days. We found no public information on ring groups, time-based or holiday routing, call recording, fax or voicemail-to-email, and emergency screening is described only for the U.S., so I cannot confirm an emergency call from a German home office reaching the right control centre. 2 3 5 6 7
The Contact Centre Lead
Number porting and buying new numbers are documented, and the standard licence lists cloud voicemail, call forwarding, call transfer, auto attendants, call queues and caller ID, with international minutes to 196 countries and emergency calling mentioned. That covers the queue and IVR basics for my Monday rush, but we found no public information on these pages about skills or priority routing, ring groups, call recording, number blocks or holiday routing. 2 3 5 6 7
The Inside Sales Lead
Auto attendants and call queues, cloud voicemail, call forwarding, call transfer and caller ID are documented, alongside number porting and new number purchase and calling plans reaching 196 countries. Emergency calling is described, but only as a US screening service, and we found no public information on ring groups, time-based and holiday routing, call recording or fax. It would carry my DACH calling, though I would want the recording piece confirmed before signing. 2 5 7 6 3
The Data Protection Officer
Number porting, new number purchase, auto attendants, call queues, cloud voicemail, call transfer and forwarding, caller ID and access to emergency calling are all documented, with a KYC review for porting that Microsoft says is usually completed within three business days. I found no public information on time-based routing, ring groups, call recording, fax or emergency locations per user; with call recording itself not described, there is equally no public information on recording consent or retention periods, which our patients' calls would require. 2 3 5 6 7
The Skeptic
Auto attendants, call queues, cloud voicemail, forwarding, transfer and caller ID are documented as the core of the hosted PBX, porting of existing numbers is offered through the operator, and emergency calling is named with US screening — but we found no public information on time-based and holiday routing, ring groups, call recording, fax or number blocks, and the only timeline on show is a KYC review said to complete within three business days. 2 3 5 6 7
Apps, desk phones & Microsoft Teams
Show reasoningHide reasoning
How this is scored
Where the calls are made and taken: desktop and mobile softphone apps, a browser client, presence, desk phones and DECT handsets from named makers (Yealink, Snom, Gigaset, Poly, Cisco) provisioned automatically, devices for sale or rent, the mobile phone as an extension with the company number shown, fixed-mobile convergence, Microsoft Teams calling through Direct Routing or Operator Connect, headset support, and the apps' ratings and update notes.
0 — No app and no device support; calls only through hardware the customer configures by hand.
3 — A softphone or mobile app; desk phones, Teams calling and the company number on mobile are basic or not described.
5 — Desktop, mobile and browser apps with presence, desk phones from named makers provisioned automatically, the company number shown on outgoing mobile calls, call handover between devices, and a Microsoft Teams integration or connector.
8 — A list of supported desk and DECT phones with auto-provisioning documented, devices sold or rented, Microsoft Teams calling through Direct Routing or Operator Connect with certification stated, fixed-mobile convergence with a SIM or mobile network, and app features documented per platform.
10 — Every endpoint a workforce uses, managed from one place: desk, DECT, mobile, browser and Teams with feature parity stated, device fleet management and firmware updates from the portal, and the app's accessibility and offline behaviour documented.
The Office Manager
Calls run in the Teams desktop and mobile clients and on certified third-party desk phones, including common-area and shared-space devices, and a mobile option makes the SIM number the Teams number — the product is Teams calling itself, so that side needs no connector. We found no public information on the captured pages naming device makers, describing automatic provisioning, or covering a browser client, presence and handover between devices. 2 4 7
The IT Administrator
Desktop and mobile clients are documented along with Teams-certified phones, common area phones and shared-space device licences, and Teams Phone Mobile makes the SIM number the Teams number, which suits our service team abroad. We found no public information on a named device list, automatic provisioning of desk and DECT handsets or device sale and rental, which is the crux for our production halls on DECT. 2 3 4 7
The Contact Centre Lead
Calls are taken in the Teams desktop and mobile clients and on certified third-party phones and common area phones, and Teams Phone Mobile makes the SIM number the Teams number, which is fixed-mobile convergence through participating mobile operators. We found no public information on these pages about named desk phone makers, automatic device provisioning, presence or call handover between devices. 2 4 7
The Inside Sales Lead
The Teams desktop and mobile clients take the calls, certified third-party phones and common area phones are supported endpoints, and Teams Phone Mobile makes a rep's SIM number their Teams number. Direct Routing and Operator Connect are documented in real depth with certified SBCs and certified operators by region. We found no public information naming device makers, auto-provisioning, or device purchase or rental. 2 3 4 5 7
The Data Protection Officer
Teams Phone runs in the desktop and mobile clients, on certified third-party phones and common area phones, and Teams Phone Mobile makes a user's SIM number their Teams number through certified mobile operators. I found no public information on named device makers, automatic provisioning, a browser client or per-platform feature documentation on the captured pages. 2 3 4 7
The Skeptic
Desktop and mobile clients plus Teams-certified third-party phones are documented, and Teams Phone Mobile ties a SIM's number to the Teams account through certified mobile operators — but we found no public information on the device makers supported, auto-provisioning, devices for sale or rent, or app features documented per platform. 2 3 4 7
Call centre, analytics & AI
Show reasoningHide reasoning
How this is scored
How a team that lives on the phone is run: ACD queues with skills and priorities, agent states and wrap-up time, a wallboard, live monitoring with listen, whisper and barge, callbacks instead of waiting, outbound and power dialers, call statistics and reports per agent and queue, missed-call handling, AI transcription, summaries and sentiment, an AI receptionist or voicebot, and SMS or WhatsApp beside calls.
0 — No queues or call statistics of any kind; calls ring until someone answers.
3 — A simple queue and a call history; agent states, live monitoring, reports and AI features are basic or not described.
5 — Queues with agent log-in and log-out, wrap-up time, a wallboard or live view, call statistics per agent and queue, missed-call lists with callback, call recording for coaching, and AI transcription or summaries offered.
8 — Skills-based routing, listen, whisper and barge, callback in queue, outbound or power dialers, scheduled and exportable reports, AI transcription, summaries and sentiment with the languages listed, an AI receptionist or voicebot, and SMS or messaging channels beside calls.
10 — A contact centre that replaces a separate suite: workforce management and quality scoring, omnichannel routing, real-time AI coaching, and every AI feature documented with its model provider, data handling and an opt-out.
The Office Manager
Auto attendants and call queues are included, Teams Phone supports coexistence with an existing contact centre, and an integration with Dynamics 365 Contact Center is described. For agent states, wrap-up time, wallboards, live monitoring, per-agent statistics, callbacks and AI call handling we found no public information on the captured pages. 1 2
The IT Administrator
Call queues and auto attendants are documented, an integration with Dynamics 365 Contact Center is offered, and coexistence with an existing contact centre is described. We found no public information on agent states, wrap-up time, wallboards, live monitoring, per-agent statistics, callback handling or AI transcription and summaries of calls. 1 2
The Contact Centre Lead
Auto attendants and call queues are included, a Dynamics 365 contact centre integration is offered through Teams Phone extensibility, and coexistence with an existing contact centre is supported. But we found no public information on these pages about skills-based queues, a wallboard, listen and whisper for coaching new agents, callbacks instead of hold music, or per-agent and per-hour statistics, which is exactly what my eighteen agents need. 1 2
The Inside Sales Lead
There are call queues and auto attendants, an integration with Dynamics 365 Contact Center, and Copilot Studio AI agents for building voice-adjacent automation. But we found no public information on agent states, wallboards, listen/whisper, per-agent statistics, or any outbound or power dialer — the exact machinery my twelve reps live on. 2 1 10
The Data Protection Officer
Call queues and auto attendants are included features, coexistence with an existing contact centre is supported, and an integration with Dynamics 365 Contact Center is documented. I found no public information on agent states, wallboards, live monitoring, per-agent statistics, dialers, AI transcription or messaging channels — before any AI touches a patient call I would need to know which model produces the transcripts and where it runs. 1 2
The Skeptic
Call queues ship with the product and the pages point to a Dynamics 365 contact centre integration, coexistence with an existing contact centre, and a developer platform for building AI agents — but we found no public information on agent states, wrap-up, wallboards, live monitoring, callbacks, dialers, per-agent statistics or AI transcription of calls, so a phone-heavy team would still be buying elsewhere. 1 2 10
CRM integration, API & administration
Show reasoningHide reasoning
How this is scored
How the phone system fits the company: integrations with CRM and helpdesk tools (Salesforce, HubSpot, Pipedrive, Zendesk, Microsoft Dynamics) with click-to-call, caller pop-ups and automatic call logging, a documented REST API and webhooks for call events, SIP trunks for an existing PBX and bring-your-own-carrier, an admin portal with roles, single sign-on (SAML) and SCIM, two-factor authentication, multi-site and multi-company set-up, bulk user import, audit logs, and partner or reseller accounts.
0 — No integrations and no administration beyond one login per number.
3 — A web portal to manage users and numbers and one or two integrations; the API, roles and SSO are basic or not described.
5 — Integrations with the common CRM and helpdesk tools with click-to-call and call logging, a documented REST API and webhooks, an admin portal with roles, two-factor authentication, several sites in one account, and SIP trunking or a connection to an existing PBX.
8 — Caller pop-ups and call data written to the CRM record, an API covering users, numbers, routing and call records, single sign-on (SAML) and SCIM provisioning, audit logs, bulk import and templates, partner or reseller accounts with sub-customers, and SIP trunks documented for named PBX systems.
10 — Administration that scales across many sites and companies: every setting reachable by API with parity stated, granular roles per site and team, SSO enforced with SCIM, audit logs exportable to a SIEM, and a partner portal with white-label and separate billing.
The Office Manager
Administration runs through the Teams admin center with PowerShell automation, a documented Microsoft Graph REST API with SDKs and change notifications, and thousands of partner apps listed; an existing PBX can be connected through a certified session border controller. CRM tools by name with click-to-call and call logging, single sign-on, SCIM provisioning, audit logs and reseller accounts are not described on the captured pages. 4 5 9 11
The IT Administrator
Microsoft Graph is documented as a REST API with SDKs and change notifications, PowerShell covers provisioning of users and groups, voice policies exist at global, group and user level, and Direct Routing connects our existing PBX through a certified SBC, which fits my script-driven number plan. We found no public information on SAML single sign-on with SCIM, audit logs, bulk import, or CRM caller pop-ups and call logging on the captured pages. 1 2 4 5 11
The Contact Centre Lead
The Graph REST API with SDKs, change notifications and PowerShell automation is well documented, users and voice policies are managed in the Teams admin centre at global, group and user level, and Direct Routing connects third-party PBXs. We found no public information on these pages about click-to-call or automatic call logging into the common CRM and helpdesk tools, so call summaries written to my helpdesk without anyone typing them remain unproven. 1 2 4 5 11
The Inside Sales Lead
Microsoft Graph gives a genuinely documented REST API with SDKs, change notifications and PowerShell for provisioning users, and the Teams admin center controls voice policies at global, group and user level; Direct Routing covers bring-your-own-carrier and third-party PBXs. For my own workflow the gap is sharp: we found no public information on a HubSpot or other CRM integration, click-to-call, caller pop-ups or single sign-on. 11 5 2 4 3
The Data Protection Officer
Microsoft Graph is documented as a REST API with SDKs, change notifications and PowerShell for provisioning, users and voice policies are managed in the Teams admin centre, and Direct Routing connects a customer's certified session border controller to third-party PBXs and analog devices — the route our practices would use to keep German carrier contracts. I found no public information on SAML single sign-on, SCIM provisioning, audit logs or CRM click-to-call integrations on the captured pages. 2 4 5 11
The Skeptic
A documented REST API with SDKs, change notifications and PowerShell automation, a Teams admin centre, voice policies at global, group and user level, and Direct Routing that connects a customer's own certified SBC and third-party PBXs are all on the record — but we found no public information on CRM click-to-call and call logging for the common CRM tools, single sign-on, SCIM provisioning, audit logs or reseller sub-customers. 2 4 5 10 11
Reliability, call security & telecoms compliance
Show reasoningHide reasoning
How this is scored
Whether the service holds on a bad day and in an audit: redundant data centres and carrier connections, a stated availability or SLA with credits, the vendor's own public status page and incident history, call quality measures (codecs, quality monitoring), encryption of signalling and media (TLS and SRTP), registration as a telecoms provider with the national regulator (Bundesnetzagentur or its EU equivalent), the secrecy of telecommunications, recording consent and retention, emergency call handling for remote users, fraud protection against toll fraud, and security certifications such as ISO 27001.
0 — Nothing on availability, security or the provider's status as a telecoms operator.
3 — A claim of high availability or "German data centres"; encryption, the SLA, the status page and regulatory status are basic or not described.
5 — Redundant data centres named by country, a public status page, TLS and SRTP encryption offered, the provider's registration with the national regulator or the carrier behind the numbers stated, a stated availability, and call recording rules described.
8 — An SLA with credits published, the incident history public, encryption on by default with the protocols documented, ISO 27001 or comparable certification with its scope, toll fraud protection and spending limits, emergency calls from softphones and home offices documented, and retention of recordings and call records stated.
10 — Carrier-grade operation evidenced: geo-redundant platforms with failover tested and published, end-to-end encryption options, independent audits (ISO 27001, BSI C5 or SOC 2) with reports available, and the regulatory and lawful-interception obligations explained in plain language.
The Office Manager
The Microsoft calling plan carries a 99.999% reliability service level agreement, and SIP/TLS, SRTP and mutual TLS are documented along with the codecs and European media processor regions. We found no public information on the captured pages about a status page, incident history, registration with the Bundesnetzagentur, ISO certification, toll-fraud protection or call recording rules. 3 4
The IT Administrator
A 99.999 percent reliability SLA for the calling plan, SIP over TLS, SRTP media, named codecs, MTLS and media-processor regions including Europe are documented, and the EU data boundary names fifteen data-centre countries. We found no public information on a public status page, SLA credits, ISO 27001 certification, toll-fraud protection, retention of recordings, or emergency calls from home offices outside the U.S. screening service. 3 4 8
The Contact Centre Lead
A 99.999% reliability service level agreement is published for the calling plan, the Direct Routing documentation specifies SIP over TLS, SRTP media, mutual TLS, the supported codecs and media processor regions, and the EU data boundary names fifteen European data centre countries. We found no public information on these pages about a public status page with incident history, ISO 27001 certification, toll fraud protection or recording retention. 3 4 8
The Inside Sales Lead
A 99.999 percent reliability SLA is published for the Microsoft calling plan, SIP over TLS and UDP/SRTP are documented down to ports and codecs with mutual TLS, and the EU data boundary names data centres in fifteen European countries including Germany, Austria and Switzerland. We found no public information on a public status page, incident history, ISO 27001, registration with the Bundesnetzagentur, or retention of recordings. 3 4 8
The Data Protection Officer
A 99.999 percent reliability SLA for the Microsoft calling plan, documented SIP/TLS and SRTP with the codecs and ports named, mutual TLS with Microsoft root certificates, and the EU data boundary's fifteen named data-centre countries give a solid technical picture. I found no public information on SLA credits, a public status page, ISO 27001, toll fraud protection, or retention of recordings and call records — without a stated retention period I cannot sign off recording in a medical practice. 2 3 4 8
The Skeptic
A 99.999% reliability SLA for the calling plan, SIP/TLS and SRTP with documented ports and codecs, mutual TLS, and a named carrier behind the numbers (Microsoft itself, or Microsoft-certified operators) are stated — but we found no public information on what the SLA pays out in credits, a public status page with incident history, ISO 27001 certification, toll fraud protection, or retention of recordings and call records. 2 3 4 8
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where call records, voicemails, recordings, transcripts, contacts and account data are stored and processed, which carriers carry the calls, and who the subprocessors are (hosting, carriers and number providers, SMS gateways, AI transcription and summary models, email delivery, support and payment tools). Independently sourced by the sovereignty pipeline. International numbers and carriers needed to reach other countries are part of what the product does and are not counted against it; where the data is stored and who processes it is. A self-hosted phone system the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (AI transcription, SMS, support, payment) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every record on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting, carriers and every subprocessor including the AI models, or a self-hosted edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The Office Manager
The EU Data Boundary commitment covers storing and processing customer data for Microsoft 365 within the EU and EFTA, naming fifteen data centre countries including Germany, and requires pseudonymization of personal data in system logs. Against that stand a US parent company, an EU contracting entity and data processing agreement not evidenced on the captured pages, no subprocessor list, and a stated carve-out that limited transfers outside the boundary remain possible. 8
The IT Administrator
The EU data boundary documentation commits Microsoft to storing and processing customer data within EU and EFTA countries, naming fifteen data-centre countries including Germany, while stating that limited circumstances still allow transfers outside the boundary. The vendor is a US company and we found no public information on an EU contracting entity, a data processing agreement, or the subprocessors behind calls, numbers and AI features on the captured pages. 8
The Contact Centre Lead
The vendor is a US company and an EU contracting entity is not stated, but the EU data boundary commits Microsoft 365 to storing and processing customer data within the EU and EFTA in data centres across fifteen named European countries including Germany, while noting that limited circumstances still allow transfers outside the boundary. Calls are carried by Microsoft itself or by unnamed certified operators, and we found no public information about subprocessor lists, a data processing agreement or security certifications, so only the hosting side is evidenced. 3 8
The Inside Sales Lead
The EU data boundary documentation commits Microsoft to storing and processing customer data within the EU and EFTA, with data centres in fifteen European countries and GDPR pseudonymization obligations stated. Against that, the vendor is Microsoft Corporation in the USA, we found no statement of an EU contracting entity, no subprocessor list and no published data processing agreement, and the boundary document itself allows limited transfers outside it. 8
The Data Protection Officer
The EU data boundary documentation commits Microsoft to storing and processing customer data within EU and EFTA countries and names data centres in fifteen countries including Germany and Austria, while also stating that limited circumstances allow data to be transferred outside the boundary. The captured pages state no EU contracting entity, list no subprocessors with their locations, show no data processing agreement and name no AI transcription providers, and the vendor is Microsoft Corporation in the USA. 8
The Skeptic
The EU Data Boundary commits to storing and processing customer data in EU and EFTA countries and names fifteen datacentre countries, yet the same documentation concedes limited circumstances in which data still leaves the boundary, the carrier under the calling plan is the US vendor itself, and we found no public information on an EU contracting entity, a data processing agreement, or any subprocessor in the chain. 3 7 8
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per user or extension and per plan, what numbers, number blocks and porting cost, which calls are included in a flat rate (landline, mobile, international) and what the rest cost per minute, which features (call centre, recording, AI, CRM integrations, Teams calling) cost extra, device prices or rent, set-up fees, minimum term and notice period, and VAT.
0 — No public prices at all; every customer is a sales call or a partner quote.
3 — A starting price per user exists, but what numbers, minutes, porting and add-ons cost is unclear.
5 — Plans are public with their price per user and main inclusions, but at least one commonly needed piece (number blocks, porting, international minutes, call centre seats, AI or recording) is unpriced or "on request".
8 — Every plan priced publicly with its scaling rule, a per-minute price list for calls outside the flat rate, numbers, porting and devices priced, add-ons priced, set-up fees, minimum term and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given number of users, numbers, sites and call minutes, with every add-on, device, porting and support fee and the cancellation and number-export terms published.
The Office Manager
The licence architecture is laid out in detail — which add-on needs which licence, bundle versus separate plans, minute pooling, pay-as-you-go zones and funding, and a one-month trial that converts automatically into a twelve-month paid subscription — but we found no public prices on the captured pages: no per-user licence figures, per-minute rates, number or porting costs, set-up fees or VAT treatment. The partners could not compute our monthly bill from what is published here. 1 6 7
The IT Administrator
The plan landscape is public: three calling plans with zone definitions and pooled minutes, a bundle or separate licences, a one-month trial that converts to a twelve-month paid term, post-usage billing and a free audio conferencing option for the U.S. and Canada. The captured pages give no per-user price for Teams Phone or the calling plans and no per-minute rates, so I cannot compute the annual cost for 280 users, three sites and our minute volume from public pages alone. 1 6 7
The Contact Centre Lead
The licence structure is documented in detail — three calling plan types with zones, pooled minutes, pay-as-you-go funded by Communication Credits or post-usage billing, which add-ons are separate, and a free trial that auto-converts to a twelve-month paid subscription — but we found no public information on a price per user for Teams Phone or the calling plans, nor on what numbers, porting or devices cost. I can map the structure for eighteen agents but cannot compute the annual bill from these pages. 1 6 7
The Inside Sales Lead
The licence architecture is public in detail — domestic, international and pay-as-you-go calling plans with named zones, pooled minutes, communication credits, a phone-plus-calling bundle and the Teams Phone add-on prerequisite — and there is a free audio conferencing licence limited to the United States and Canada. But we found no price per user for any plan, no per-minute rates, no number or porting costs and no device prices, so I cannot compute a year's cost for my team from these pages. 6 7 1
The Data Protection Officer
The licence architecture is public in unusual detail: the Teams Phone add-on, three calling plan types with pooled minutes, pay-as-you-go zones, the phone-and-calling-plan bundle, audio conferencing inclusions and the EEA suite split are all described. I found no public information on per-user prices, or on what numbers, porting, devices or set-up cost, so the real annual cost for six practices is not computable from the captured pages. 1 6 7
The Skeptic
The licence architecture is documented in detail — Teams Phone add-on, three calling plan types with their inclusions, minute pooling, pay-as-you-go funded by Communication Credits or post-usage billing, and a one-month trial that auto-converts to a 12-month paid subscription with a credit card required — but no price per user for any paid plan appears on the captured pages, and we found no public information on per-minute rates, number and porting costs, devices, set-up fees or VAT, so neither the first nor the second year can be computed. 1 6 7
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined ⚠ unverified | — | uncited Report an error |
| Hosting options | Not determined ⚠ unverified | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Microsoft Teams Phone
Is Microsoft Teams Phone European?
No. whats-best.ai classifies Microsoft Teams Phone as Rest of world.
Where does Microsoft Teams Phone store data?
Not stated on the vendor’s pages as of 5 Nov 2026.
Does Microsoft Teams Phone have a free plan?
Not stated on the vendor’s pages as of 5 Nov 2026.
What are the best alternatives to Microsoft Teams Phone?
As of 6 Nov 2026, the panel rates Placetel (3.5/5), RingCentral RingEX (3/5) and Aircall (3/5) highest among the other 13 Cloud Telephony (VoIP & Cloud PBX) products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Placetel (EU origin, foreign-owned). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Microsoft Teams Phone alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 5 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting location, Hosting options. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 14 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 8 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage (product page) www.microsoft.com Checked 5 Nov 2026 Details →
- 2 Documentation (Teams Phone) learn.microsoft.com Checked 5 Nov 2026 Details →
- 3 Documentation (PSTN connectivity options) learn.microsoft.com Checked 5 Nov 2026 Details →
- 4 Documentation (Direct Routing) learn.microsoft.com Checked 5 Nov 2026 Details →
- 5 Documentation (Operator Connect) learn.microsoft.com Checked 5 Nov 2026 Details →
- 6 Documentation (calling plans) learn.microsoft.com Checked 5 Nov 2026 Details →
- 7 Documentation (licensing) learn.microsoft.com Checked 5 Nov 2026 Details →
- 8 EU data boundary learn.microsoft.com Checked 5 Nov 2026 Details →
- 9 Apps, desk phones & Microsoft Teams — found from sitemap developer.microsoft.com Checked 5 Nov 2026 Details →
- 10 Apps, desk phones & Microsoft Teams — found from sitemap developer.microsoft.com Checked 5 Nov 2026 Details →
- 11 CRM integration, API & administration — found from sitemap developer.microsoft.com Checked 5 Nov 2026 Details →