Integrations

Operator Connect via Telnyx now in over 40 Countries

Telnyx's Operator Connect offering is expanding significantly. Full details below.

Simon-Verbiest-Avatar
By Simon Verbiest
Operator Connect via Telnyx now in over 40 Countries

Telnyx Operator Connect: Now Available in 50+ Countries

Telnyx Operator Connect for Microsoft Teams is expanding its geographic footprint significantly, bringing enterprise-grade voice connectivity to users in more than 50 countries worldwide. For organizations running Microsoft Teams as their primary communications platform, this expansion fundamentally changes what's possible for global voice deployments.

What This Means for Enterprise Teams Users

Operator Connect is Microsoft's managed framework that allows certified operators like Telnyx to connect directly to Teams' calling infrastructure — without the complexity of traditional Direct Routing configurations. Users get a native calling experience inside Teams, while IT administrators retain centralized management and visibility.

With Telnyx's expansion to 50+ countries, enterprise Teams deployments can now:

  • Provision local numbers in 50+ countries directly through the Teams Admin Center, without per-country carrier contracts
  • Manage global voice infrastructure from a single control plane — the Telnyx Mission Control Portal and Teams Admin Center work together
  • Extend consistent call quality to remote and international offices using Telnyx's owned global IP network
  • Eliminate per-country SIP trunk configurations that traditional Direct Routing requires

This is a particularly meaningful development for multinational organizations that have struggled to unify their Teams voice infrastructure across regions — previously requiring separate carrier relationships in each country.

Geographic Coverage Highlights

Telnyx's 50+ country Operator Connect coverage spans every major business region:

North America: United States, Canada, Mexico

Europe: United Kingdom, Germany, France, Netherlands, Belgium, Spain, Italy, Sweden, Norway, Denmark, Finland, Switzerland, Austria, Poland, Czech Republic, Portugal, Ireland, and more

Asia-Pacific: Australia, New Zealand, Singapore, Japan, Hong Kong

Latin America: Brazil, Colombia, Chile, Argentina, Mexico (listed above)

Middle East: Israel, UAE

Full country availability is listed in the Telnyx Operator Connect product page. Coverage continues to expand quarterly.

How to Get Started

Getting started with Telnyx Operator Connect in new countries is straightforward for existing Teams administrators:

  1. Verify country availability on the Telnyx Operator Connect page or via the Teams Admin Center operator marketplace
  2. Connect Telnyx as your operator in the Teams Admin Center under Voice → Operator Connect
  3. Request numbers in target countries through the Teams Admin Center or the Telnyx Mission Control Portal
  4. Assign numbers to users and enable voice policies as you would for domestic numbers
  5. Test and validate call routing using Telnyx's built-in diagnostics

For organizations new to Telnyx Operator Connect, the onboarding process typically takes less than a day for an initial country deployment. Telnyx's enterprise team provides dedicated onboarding support for complex multi-country rollouts.

Compliance and Regulatory Considerations

Expanding voice infrastructure to new countries comes with regulatory obligations that vary significantly by jurisdiction. Telnyx's Operator Connect expansion accounts for these requirements:

  • Number portability: In most covered countries, Telnyx supports porting existing numbers into the platform, preserving existing business phone numbers during migration.
  • Emergency services compliance: Local emergency calling requirements (e.g., E911 in the U.S., 999/112 in the UK and Europe) are handled per country regulations. Telnyx provides guidance on emergency address registration for each covered jurisdiction.
  • Data residency: For organizations with strict data residency requirements (common in the EU under GDPR), Telnyx provides documentation on call data handling and regional processing.
  • Local regulatory filings: In some countries, operating as a voice carrier requires local regulatory registration. Telnyx manages these filings as part of its Operator Connect certification, so customers don't need to navigate country-specific telecom regulations independently.

Why Telnyx for Global Operator Connect?

Telnyx differentiates from other Operator Connect providers through its owned global IP network — rather than reselling capacity from third-party carriers, Telnyx controls its own infrastructure across key interconnection points worldwide. This translates into:

  • Lower latency on international calls through fewer network hops
  • Competitive per-minute rates driven by owned capacity rather than wholesale margins
  • Greater transparency with real-time analytics and per-call quality metrics in Mission Control

Learn more about Telnyx Operator Connect and explore how the 50+ country expansion can simplify your global Teams voice infrastructure.

Telnyx is proud to announce the addition of 35 new countries to its Operator Connect offering, bringing our total number of supported locations to 43.


On top of the above, we're also launching competitive pricing Bundles and powering it all with our own MS-certified Session Border Controller.

Read on for tips on getting started as well as a full list of supported countries.

Getting started

You can use our guide to get started with Operator Connect yourself. To begin, you’ll need a Portal account and the appropriate Microsoft Teams licenses.

Notes

  1. If you are considering provisioning >500 seats, we recommend speaking with a Telnyx expert to optimize your setup.
  2. To find out which Bundles are available in your location(s), check out the Bundles section in the Telnyx Portal.
  3. Telnyx also supports Direct Routing, the setup guide for that is here.

List of countries and locations supported

North America (NORTHAM):

  • Canada
  • United States

Europe, Middle East & Africa (EMEA):

  • Albania
  • Austria
  • Belgium
  • Bosnia
  • Bulgaria
  • Czech Republic
  • Cyprus
  • Denmark
  • Estonia
  • Finland
  • France
  • Georgia
  • Germany
  • Greece
  • Croatia
  • Hungary
  • Ireland
  • Israel
  • Italy
  • Lithuania
  • Luxembourg
  • Latvia
  • Netherlands
  • Norway
  • Poland
  • Portugal
  • Romania
  • Serbia
  • Sweden
  • Slovenia
  • Slovakia
  • Spain
  • South Africa
  • Switzerland
  • United Kingdom

Latin America (LATAM):

  • Argentina
  • Brazil
  • Chile
  • Mexico
  • Puerto Rico
  • US Virgin Islands

Upcoming Locations

We’ll continue to increase our Operator Connect coverage as part of our mission to simplify global telecommunications access. Coming soon: APAC and additional LATAM countries!

FAQ

What is WebRTC and why is it useful for healthcare? WebRTC is an open standard that lets browsers and mobile apps stream real-time audio, video, and data without plugins, which makes virtual visits and triage simple to launch. It supports secure, interactive care experiences while avoiding complex installs for patients and clinicians.

Can WebRTC be HIPAA compliant? WebRTC encrypts media in transit, but HIPAA compliance depends on the full implementation, including secure signaling, authentication, audit logging, and a Business Associate Agreement. Teams must manage PHI carefully, obtain consent, and enforce strict access controls and retention policies.

Which cloud platform is best for healthcare WebRTC? The best choice depends on existing systems, budget, regional needs, and compliance goals, and AWS, Azure, and GCP all offer viable HIPAA-ready patterns. Many teams pair their chosen cloud with communications APIs to handle real-time signaling, media relays, and EHR or CRM integrations.

How does WebRTC support the four types of telehealth? WebRTC powers live video visits and can carry data channel exchanges, while asynchronous education and instructions often use MMS messaging for non-PHI outreach. Remote patient monitoring can trigger real-time escalation to a WebRTC visit, and mHealth apps embed it to connect users with clinicians when needed.

What bandwidth and latency do WebRTC telehealth sessions require? Plan for 300–500 kbps per stream for voice and SD video, and 1–2 Mbps for HD with stable upload. Target round-trip latency under 150 ms and jitter under 30 ms to keep conversations natural.

How should healthcare teams handle recording and consent in WebRTC visits? Always obtain explicit consent and show clear indicators, then record server-side or via secure client capture to limit PHI exposure. Encrypt stored recordings, restrict access by role, and align retention with policy and state two-party recording laws.

How can SMS and MMS complement WebRTC in healthcare workflows? Use SMS for scheduling and logistics and send visual prep or post-visit materials via MMS, and one-to-many notifications should follow broadcast messaging patterns to protect recipient privacy. Keep clinical specifics out of consumer messaging unless policy and consent clearly permit it, and route sensitive issues back into the secure telehealth session.

Share on Social

Related articles

Sign up and start building.