How to Integrate Microsoft Teams With Genesys Cloud (Without the SBC Headache)

For years, the "siren song" of a unified communications experience has lured IT directors and customer experience (CX) leaders toward the promise of a single, frictionless workflow. You’ve likely dreamed of a world where your back-office experts on Microsoft Teams and your front-line agents on Genesys Cloud dance in perfect harmony. But often, that dream hits a jagged reef: the SBC headache.

Traditionally, connecting these two powerhouses meant purchasing, deploying, and managing a Session Border Controller (SBC). It was the high-maintenance middleman that required constant patching, specialized knowledge, and a healthy dose of hardware-induced anxiety.

But what if you could throw the middleman overboard?

Today, a "human-machine duet" is possible through cloud-to-cloud integration. You can bridge the gap between Microsoft Teams and Genesys Cloud without ever touching a physical SBC or managing a virtual one in your private cloud. This guide will show you exactly how to achieve that seamless, low-maintenance connection.

1. The "No-SBC" Architecture: A New Paradigm

Before we dive into the "how," let’s look at the "why." In a traditional setup, you would own and operate an SBC (like AudioCodes or Ribbon) that brokers the SIP traffic between Microsoft’s Direct Routing and Genesys Cloud.

The modern alternative is Genesys BYOC Cloud to Teams Direct Routing.

In this model, the SBC functions are handled natively within the Genesys Cloud platform. Microsoft still "sees" an SBC because it communicates via Direct Routing, but you: the organization: never have to deploy, secure, or update a separate box. It is a pure cloud-to-cloud handshake that simplifies your infrastructure and reduces your operational overhead significantly.

Key Benefits of the Cloud-to-Cloud Model:

• Reduced Complexity: No separate SBC licenses, certificates, or firmware to manage.

• Scalability: As your team grows, the cloud infrastructure scales automatically without hardware bottlenecks.

• Lower TCO: You eliminate the capital and operational costs associated with traditional SBC management.

• Reliability: You leverage the global, high-availability infrastructure of two industry giants.

2. Prerequisites: Your Pre-Flight Checklist

Don't reach for the configuration settings just yet. To ensure a smooth landing, verify that your organization has the following components ready:

1. Genesys Cloud CX Licenses: Your organization must have Genesys Cloud and ensure that BYOC Cloud is enabled in your subscription.

2. Microsoft 365 Licenses: Users who will be using Teams for voice must have Teams Phone (formerly Phone System) licenses. This is typically included in E5 plans or available as an add-on for E1/E3.

3. Administrative Privileges: You will need "Telephony Admin" rights in Genesys and both "Teams Admin" and "Global Admin" (or Entra ID Admin) roles in Microsoft 365 to verify domains.

4. A Consistent Numbering Plan: Decide on your E.164 strategy early. Consistency is key when transferring calls between a contact center agent and a back-office Teams user.

3. Step-by-Step: Configuring the Integration

Let’s walk through the actual configuration. Think of this as building a bridge; we need to secure the foundations on both sides before the traffic can flow.

Step A: Create the BYOC Cloud Trunk in Genesys

First, we tell Genesys Cloud how to talk to Microsoft’s hubs.

1. Navigate to Admin > Telephony > External Trunks.

2. Create a new external trunk and select the type as BYOC PBX or Generic BYOC PBX.

3. Set the Protocol to TLS: security is non-negotiable here.

4. Under Outbound SIP Servers, enter the Microsoft Direct Routing hubs: sip.pstnhub.microsoft.com, sip2.pstnhub.microsoft.com, and sip3.pstnhub.microsoft.com.

5. Crucial Step: In the Inbound / SIP Routing section, look for the Termination Identifier. This FQDN (Fully Qualified Domain Name) is the "address" of your Genesys "SBC." Copy this; you’ll need it for Microsoft.

Step B: Verify Your Domain in Microsoft 365

Microsoft won’t accept traffic from just anyone. You have to prove you own the "address" Genesys just gave you.

1. Go to the Microsoft 365 Admin Center and add a new domain. Use the exact FQDN you copied from the Genesys trunk (e.g., company.xxxx.purecloudbyoc.com).

2. Choose verify via TXT record. Microsoft will give you a TXT value.

3. Head back to your Genesys Cloud Trunk settings, go to the Integrations tab, and click Publish TXT Record. Paste Microsoft’s value there.

4. Once published, go back to Microsoft and click Verify.

This digital "handshake" allows Microsoft to recognize Genesys as a trusted partner for your voice traffic.

Step C: Configure Teams Direct Routing

Now we tell Teams that this new "SBC" exists.

1. In the Teams Admin Center, navigate to Voice > Direct Routing.

2. Add a new SBC using the FQDN you verified. Set the port to 5061 (for TLS).

3. Create Voice Routes and PSTN Usages that point to this SBC.

4. Assign these policies to your users. Now, when a Teams user makes a call, Microsoft knows to send it across the bridge to Genesys.

4. Beyond Voice: Directory and Presence

While the "SBC-free" voice connection is a massive win, you shouldn’t stop there. To truly achieve that "human-machine duet," you want your agents to see if a Teams user is available before they transfer a call.

This is where the Genesys Cloud for Teams app and SCIM (System for Cross-domain Identity Management) come into play.

By setting up SCIM, you synchronize your Microsoft Entra ID (formerly Azure AD) users with Genesys Cloud. This allows for:

• Presence Sync: Agents can see "Available," "Busy," or "In a Meeting" status for Teams users within the Genesys interface.

• Simplified Directory Search: Agents can search for back-office experts by name rather than hunting for a phone number.

• Click-to-Dial: Initiate calls directly from the synchronized directory.

This level of integration doesn't require a separate SBC, but it does require a bit of API configuration. It's the difference between a simple phone call and a truly unified workplace.

5. Avoiding the Common Pitfalls

Even without a physical SBC, there are a few "traps" that can derail your project. Keep these recommendations in mind:

• Normalize Your Numbers: Ensure both systems are using the E.164 format (e.g., +15551234567). If one system expects extensions and the other expects full numbers, calls will fail at the finish line.

• Check Your IP Ranges: Microsoft frequently updates its IP ranges for Direct Routing. Ensure your Genesys Cloud Access Control Lists (ACLs) are wide enough to accept traffic from all Microsoft regional hubs.

• Don't Forget Emergency Services: E911 routing requires careful planning when using Direct Routing. Ensure that calls to emergency services are routed through the correct carrier or handled by a specialized E911 provider.

Why Partner with Dunamis Consulting Inc?

Migrating your telephony to the cloud is a journey, and while the "no-SBC" route is significantly easier, it still requires a steady hand on the tiller. At Dunamis Consulting Inc, we’ve spent over 15 years helping organizations navigate the complexities of cloud telephony migration.

Whether you need a comprehensive cost analysis to justify the move, or technical staffing support to handle the configuration, we are here to ensure your integration is a success. We specialize in identifying the gaps in your current infrastructure and building a bridge that actually holds up under pressure.

The dream of a unified Microsoft Teams and Genesys Cloud environment is no longer a complex engineering feat. It’s a strategic choice. By choosing the BYOC Cloud path, you’re not just saving yourself an SBC headache: you’re setting your organization up for a more agile, scalable future.

Ready to unify your communication?Contact us today to learn how we can help you bridge the gap between your contact center and the rest of your business.

---