How to Integrate Genesys Cloud With Microsoft Teams (The No-SBC Shortcut)

For years, the "siren song" of a unified communication strategy has lured IT leaders into deep, murky waters. You want the powerhouse customer experience (CX) of Genesys Cloud and the ubiquitous collaboration of Microsoft Teams, but the technical bridge between them often felt like building a suspension bridge with toothpicks.

Traditionally, that bridge required a Session Border Controller (SBC): a literal or virtual box that sat in the middle, demanding its own licensing, patching, and hardware overhead. It was a mandatory gatekeeper that added complexity to your stack and gray hairs to your IT team.

But what if you could skip the middleman?

At Dunamis Consulting Inc, we focus on simplifying cloud telephony for our clients. Today, we’re peeling back the curtain on the "No-SBC Shortcut": a direct, cloud-to-cloud integration that connects Genesys Cloud BYOC (Bring Your Own Carrier) directly to Microsoft Teams Direct Routing.

Why the "No-SBC" Path is a Game Changer

In the past, an SBC was the "magic wand" that handled the heavy lifting of SIP signaling and media between two disparate systems. However, Genesys Cloud BYOC Cloud has evolved. It can now establish a direct SIP over TLS connection with Microsoft’s PSTN hubs.

For your IT team, this means:

• Reduced Infrastructure Footprint: No more virtual machines to spin up or hardware appliances to rack and stack.

• Lower Operational Costs: You eliminate the licensing and maintenance costs associated with third-party SBC vendors.

• Faster Deployment: You can stand up the telephony link in a fraction of the time, moving straight from configuration to testing.

• Streamlined Troubleshooting: When a call drops, you only have two platforms to look at: not three.

The Technical Runbook: A 5-Step Shortcut

Integrating these two giants without an SBC requires a specific sequence of moves. If you follow this "no-SBC" shortcut, you can have voice traffic flowing between your contact center agents and your Teams users by the end of the day.

1. Configure the Genesys Cloud External Trunk

The first step happens within your Genesys Cloud Admin panel. You aren't just creating any trunk; you are building a specialized BYOC PBX trunk.

• Protocol: You must use TLS (Transport Layer Security). Microsoft Teams Direct Routing does not accept unencrypted SIP.

• SIP Servers: Add the three Microsoft PSTN hub FQDNs: sip.pstnhub.microsoft.com, sip2.pstnhub.microsoft.com, and sip3.pstnhub.microsoft.com.

• Termination Identifier: This is your FQDN (e.g., gc-teams-trunk.yourcompany.com). Genesys will use this to generate a unique Inbound Request-URI FQDN. Keep this value handy: you’ll need it for Microsoft 365 verification.

2. The Domain Verification "Magic Trick"

This is where most IT teams get stuck, but here is the shortcut: Genesys Cloud can actually host the TXT record required for Microsoft domain verification.

1. In the Microsoft 365 Admin Center, add a new domain that exactly matches your Genesys trunk FQDN.

2. Choose "Add a TXT record" and copy the value provided by Microsoft.

3. Back in Genesys Cloud, go to your trunk's Integrations tab and click Publish TXT Record. Paste the value there.

4. Once Genesys publishes it, Microsoft can "see" the record and verify that you own the trunk endpoint.

3. Setup the SBC in Teams Admin Center

Wait, didn't we say "No SBC"? From Microsoft's perspective, the Genesys Cloud BYOC endpoint is the SBC.

• Navigate to Voice > Direct Routing > SBCs in the Teams Admin Center.

• Add a new "SBC" using the FQDN you just verified.

• Set the SIP signaling port to 5061.

4. Align Your Dial Plans

This is the "human-machine duet" part of the process. You need to ensure both systems speak the same language (E.164 formatting).

• In Genesys: Create a Dial Plan and Outbound Route that identifies calls destined for Teams users and sends them through your new Microsoft Teams external trunk.

• In Teams: Create Voice Routes and PSTN Usages that route contact center-bound calls back to the Genesys FQDN.

5. Presence and Collaboration Integration

Telephony is only half the battle. To truly unify your workforce, you should also deploy the Genesys Cloud for Microsoft Teams app. This allows your contact center agents to see the "Presence" (Available, Busy, Away) of Teams-based subject matter experts in real-time, making transfers seamless.

Common Mistakes to Avoid (The "Don'ts")

• Don't ignore IP Allowlisting: Microsoft uses specific IP ranges for Direct Routing. If you don't add these to your Genesys SIP Access Control (ACL), the connection will fail silently.

• Don't forget the Certificates: Since you are using TLS, ensure your certificates are valid and match the FQDNs you’ve configured.

• Don't skip the "High Capacity" toggle: In Genesys Cloud, ensure you enable the "high capacity outbound platform" on the trunk to handle enterprise-level traffic.

The Dunamis Approach: Expert Guidance for Your Integration

While the "No-SBC Shortcut" simplifies the architecture, the devil is always in the details. At Dunamis Consulting Inc, we have over 15 years of experience navigating the complexities of cloud telephony.

Whether you are struggling with a telephony staffing crisis or need a comprehensive cost analysis before migrating, our team is here to provide personalized consultation. We don't just sell hours; we provide the architectural blueprint to ensure your transition from legacy systems to Genesys Cloud and Microsoft Teams is flawless.

Your Actionable Takeaway: Check your current SBC maintenance contracts. If you are paying for hardware support and licensing just to bridge Genesys and Teams, you are likely overspending. Consider the "No-SBC" model to trim the fat and modernize your stack.

Ready to simplify your telephony stack? Contact Dunamis Consulting today to schedule a project gap analysis and discover how our flexible staffing solutions can accelerate your Genesys Cloud implementation.