How Microsoft Teams Powers Regional Collaboration for a Global Gaming Company: A China Cloud SBC Case Study

Live-service games don't sleep, and neither do the teams that run them. When a live-ops incident hits a title's China servers at 2 a.m. Shanghai time, the studio's engineers in Shenzhen, its publishing team in Singapore, and its community managers in Los Angeles all need to be on the same call, looking at the same dashboards, within minutes. For one global gaming company, that simple expectation kept breaking down — not because the teams weren't talented, but because Microsoft Teams behaves differently once you cross into mainland China.

This is the story of how Brocent helped that gaming company move past the limitations of Microsoft Teams China, roll out the international Teams experience to the people who needed it, and design a cloud-based Session Border Controller (SBC) that finally connected Teams Phone System to the company's existing telephony estate. The result was a single, predictable way to talk, chat, and call across every studio the company operates — and a measurable jump in cross-region productivity.

The Client: A Global Gaming Company Scaling Across Regions

Our client is a mid-to-large multi-studio gaming company with development teams in mainland China, publishing and localization staff across Southeast Asia, and live-operations, marketing, and finance functions in North America and Europe. Like most gaming businesses at this scale, the company runs on tight release cycles, live-service patch windows, and 24/7 player-support rotations — all of which depend on real-time collaboration between people who are rarely in the same room, city, or country.

Microsoft 365 and Teams were already the company's standard for chat, meetings, and file collaboration outside China. The problem was that "outside China" was doing a lot of work in that sentence. Inside mainland China, the studio's staff were either locked out of features their overseas colleagues used every day, or routed through a completely separate version of Teams that didn't talk to the rest of the organization cleanly. Cross-studio standups turned into a patchwork of WeChat groups, phone calls, and manually forwarded screenshots — workable, but slow, and risky for anything security- or compliance-sensitive.

Brocent was brought in for regional IT support already, through our APAC IT Support engagement. When the client's regional collaboration problems started costing real release-cycle time, that relationship extended naturally into a focused Microsoft Teams and telephony project.

The Problem: Why Microsoft Teams Behaves Differently in China

Most companies expanding into China assume Microsoft Teams "just works" the way it does everywhere else. It doesn't, and the reasons are structural, not cosmetic.

A separate operating environment. Microsoft 365 services delivered to mainland China are operated locally under a licensing arrangement with a domestic partner, running on infrastructure inside China rather than on Microsoft's global cloud. That keeps the service compliant with China's data residency and telecom regulations, but it also means the China-operated Teams environment is, in practice, a separate deployment from the global tenant most multinational companies already run.

Feature and update lag. New Teams capabilities — calling features, meeting experiences, app integrations, AI-assisted tools — typically reach the China-operated service later than the global service, if they arrive at all. For a gaming company shipping features and content on a weekly cadence, a communications platform that lags behind its own roadmap becomes a bottleneck rather than an accelerator.

Federation and directory friction. Chat, presence, and calling between a China-based identity and a global-tenant identity is not seamless by default. Employees found themselves toggling between two different "Teams," two different address books, and two different meeting links depending on who they were trying to reach — exactly the kind of friction that turns a five-minute sync into a twenty-minute exercise in app-switching.

No clean path to the phone system. Perhaps the biggest gap for this client: Teams Phone System's calling infrastructure and the client's existing PBX and PSTN carrier relationships in China were never designed to talk to each other out of the box. Legacy desk phones, regional call queues, and support hotlines sat on one side; Teams sat on the other, with no bridge between them.

Compliance and data residency requirements. Under China's Multi-Level Protection Scheme (MLPS) and PIPL data rules, voice and meeting data touching mainland China infrastructure has to stay within approved boundaries. Any integration had to respect those boundaries while still giving the rest of the company a single, coherent Teams experience — a balancing act that ruled out simple, one-tenant shortcuts.

None of this is a flaw in Teams itself — it's the reality of operating a Microsoft cloud service across a regulatory boundary as significant as China's. But for a gaming company where minutes matter during a live incident, "the reality of operating across a regulatory boundary" was translating directly into missed handoffs and delayed fixes.

What We Delivered: The International Microsoft Teams Experience, Delivered Correctly

Brocent's first job was not to fight the China-operated service, but to design around it. Through our Microsoft Teams Solutions and Cloud Solutions practice, we ran a structured assessment of the client's tenant footprint, identity architecture, and calling requirements before touching a single policy.

Identity and tenant architecture. We mapped which staff genuinely needed to operate inside the China-compliant environment (largely the mainland development and operations teams) versus which staff needed full access to the international Teams experience (publishing, live-ops leadership, community, finance, and executives coordinating globally). Rather than forcing a single tenant model that would either violate China's data rules or degrade the experience for everyone else, we designed a governed dual-environment setup with clear, documented rules for identity, guest access, and cross-tenant collaboration.

Deploying the international version where it mattered. For roles that needed the full, current Microsoft Teams feature set — international calling, the latest meeting and collaboration tools, and direct integration with the company's global Microsoft 365 & Entra ID environment — we deployed and configured the standard global Teams service, correctly licensed and access-controlled, so those users got the same Teams experience as their counterparts in Singapore, London, or Los Angeles.

Consistent policy and device configuration. Using Intune and Entra ID-based conditional access (building on foundations similar to what we describe in our Microsoft 365 & Entra ID Security Audits in APAC work), we standardized meeting policies, calling policies, and device compliance rules across both environments, so a meeting invite, a calling number, and a security posture meant the same thing no matter which side of the boundary a user sat on.

Federation and directory alignment. We configured directory synchronization and presence/chat interop between the two environments so that, wherever technically and legally possible, staff could find each other, see accurate presence, and join the same meeting link — closing the "two different Teams" experience that had been quietly costing the client hours every week.

The outcome of this phase alone was a Teams experience that looked and felt the same to end users regardless of where they were logging in from — even though, underneath, two distinct, compliant environments were doing the work.

Building a Cloud-Based Session Border Controller (SBC) to Connect Teams to the Phone System

Fixing the collaboration experience solved half the problem. The other half was voice — and voice was where the client felt the most pain. Support hotlines, regional sales lines, and studio front-desk numbers all still ran through a legacy PBX and a mix of local carriers. None of it connected to Teams Phone System natively, which meant employees carried two devices, two voicemail systems, and two sets of dial habits.

The fix was a cloud-based Session Border Controller, purpose-built to bridge Microsoft Teams Phone System with the client's existing telephony infrastructure using Direct Routing.

Why a cloud SBC. A Session Border Controller is the piece of infrastructure that sits between a Microsoft Teams tenant and the public telephone network (or an existing PBX), translating and securing the SIP signaling and RTP media traffic that carries calls between the two worlds. Deploying it as a cloud service — rather than as physical appliances bolted into a single data center — meant we could:

• Place SBC instances close to the client's China and international carrier connections for lower call latency and better voice quality
• Build in active-active redundancy across regions, so a regional outage didn't take down calling for the whole company
• Scale capacity up during peak live-ops and support-hotline periods without a hardware refresh cycle
• Apply consistent security controls (TLS/SRTP encryption, session limits, fraud and toll-abuse protection) centrally, instead of per-appliance

Integrating with the existing phone system. We connected the cloud SBC to the client's incumbent carrier trunks and legacy PBX using Direct Routing, mapping existing DID numbers, hunt groups, and support hotlines directly into Teams Phone System. Existing published phone numbers kept working. Call queues and auto-attendants that used to live on the PBX were re-platformed onto Teams, with call flows and business-hours logic preserved. Where the client's China operations required calls to stay on domestically approved carrier paths for compliance, we built region-aware routing rules into the SBC configuration so those calls never left approved infrastructure, while international calls routed over the most efficient path available.

Number and carrier migration without downtime. Because live-service support lines can't simply go dark for a migration window, we phased the cutover hotline by hotline and studio by studio, running the legacy PBX and the new Teams Phone routing in parallel until each site's numbers, call quality, and failover behavior were verified.

Why This Beat an On-Premises Appliance Approach

The client had, early on, considered a traditional on-premises SBC appliance at each major site. We recommended against it for three reasons specific to a multi-studio gaming company: on-prem appliances tie capacity to a box that has to be sized for worst-case load (expensive and wasteful most of the year); they create a single point of failure per site unless you buy and maintain a second appliance; and they're slow to reconfigure when a studio opens, closes, or changes carriers — which, in the games industry, happens more often than most IT teams would like. A cloud SBC gave the client carrier-grade reliability with the flexibility to add or retire a site's calling footprint in days, not months.

Security, Compliance, and Governance Along the Way

None of this was worth deploying if it weakened the client's security or compliance posture, so governance was built into the design rather than bolted on afterward. Every SBC instance enforced encrypted signaling and media (TLS/SRTP) end to end, with session border rules limiting which networks could originate or terminate calls. Call detail records and routing logs were retained separately for the China-facing and international paths, satisfying local audit requirements without exposing global call data unnecessarily. On the identity side, conditional access policies distinguished between users who were licensed and permitted to use the international Teams environment and those who were confined to the China-compliant environment, so entitlement — not just network location — determined what a given account could reach. Toll-fraud and abnormal-calling-pattern alerts were configured on the SBC itself, giving the client's security team visibility into voice traffic the same way they already had visibility into email and endpoint activity. The net effect: the client passed its next internal compliance review with the new architecture in place, and gained a voice and collaboration platform that was easier to audit than the legacy PBX-plus-WeChat patchwork it replaced.

The Results: What Better Regional Collaboration Actually Looked Like

Once both pieces — the correctly deployed international Teams experience and the cloud SBC-based phone integration — were live, the operational change was immediate and measurable:

• Faster live-ops incident response. Cross-region incident bridges that used to take 15–20 minutes to assemble (chasing people across WeChat, phone, and mismatched Teams environments) now start inside a single Teams call within minutes, with the right people already reachable through one directory.
• One number, one voicemail, one device. Support and sales staff who previously juggled a desk phone and a Teams client now make and receive every call — internal or external, domestic or international — from Teams, on any device.
• Fewer IT tickets. Helpdesk volume tied to "can't find a colleague," "wrong meeting link," or "call won't connect to China" dropped substantially once directory, presence, and calling behaved consistently across regions.
• Lower telephony cost. Consolidating carrier trunks behind the cloud SBC and retiring redundant PBX hardware reduced recurring telephony spend, while active-active redundancy improved uptime compared with the single-site legacy PBX.
• Faster onboarding for new studios and hires. Standing up a new studio's calling and collaboration footprint became a configuration exercise on the SBC and in Teams admin, not a hardware procurement project.
• Better release-cycle coordination. Cross-studio production reviews and go-live checklists that used to require a dedicated bridge-call coordinator now run as standing Teams meetings with consistent recording, transcription, and follow-up task capture — all previously unavailable to the China-based half of the team.
• More reliable player-support coverage. With call queues and auto-attendants unified inside Teams Phone System, the client's support leads can rebalance agents across regions during launch-week spikes without renumbering hotlines or reconfiguring hardware.

None of these gains came from a single silver-bullet feature. They came from removing the friction that had been quietly taxing every cross-region interaction — the exact kind of friction a fast-moving gaming company can least afford during a live-service incident or a launch week.

What This Means If You're Running Global Teams Operations Across China

Companies operating in mainland China and internationally at the same time run into a version of this problem sooner or later, whether they're in gaming, e-commerce, manufacturing, or financial services. A few takeaways from this engagement apply broadly:

1. Design for two environments, not one workaround. Trying to force a single global Teams tenant to serve mainland China (or vice versa) usually creates either a compliance gap or a degraded user experience. Plan for a governed dual-environment architecture from the start.
2. Voice is often the hardest part, not chat. Messaging and meetings get most of the attention, but phone system integration — carrier trunks, number portability, regional compliance — is usually the piece that actually blocks a company from retiring legacy telephony.
3. A cloud SBC is an operational decision, not just a technical one. The right SBC deployment model should track how often your regional footprint changes, not just your current call volume.
4. Treat this as a collaboration project, not just a comms upgrade. The real payoff shows up in incident response times, release coordination, and support-hotline reliability — metrics that matter to the business, not just to IT.

Frequently Asked Questions

Can international companies use Microsoft Teams in mainland China?

Yes, but Microsoft 365 and Teams delivered inside mainland China run through a locally operated environment rather than the global Microsoft cloud, with its own update cadence and feature availability. Companies with staff both inside and outside China typically need to plan for two connected environments rather than assuming one global tenant covers everyone.

What's the practical difference between Teams in China and the international version of Teams?

The core difference is the underlying operating environment and its compliance boundary. That translates into differences in feature rollout timing, calling capabilities, and how directly staff in China can interoperate with a global tenant's chat, presence, and meetings without additional configuration.

What is a cloud-based Session Border Controller, and why does Teams Phone need one?

An SBC secures and translates the call signaling and media traffic between Microsoft Teams Phone System and the public phone network or an existing PBX. A cloud-based SBC delivers that function as a managed, geographically distributed service rather than physical hardware at each site, which is typically more resilient and easier to scale for multi-region organizations.

How long does a Teams-to-phone-system integration like this usually take?

For a multi-studio organization with legacy PBX infrastructure and China-specific carrier requirements, a phased rollout — assessment, SBC deployment, and studio-by-studio cutover — typically runs several months, timed around each site's tolerance for change and support-line uptime requirements.

Is Direct Routing through a cloud SBC better than Microsoft Calling Plans for a company operating in China?

For organizations with existing carrier relationships, regional compliance requirements, or a need to keep specific call paths on domestic infrastructure, Direct Routing through a cloud SBC generally offers more control over routing, cost, and compliance than relying solely on Microsoft Calling Plans.

Does this approach work for industries outside gaming?

Yes. The same pattern — governed dual-environment Teams architecture plus a cloud SBC bridging Teams Phone System to existing telephony — applies to any multinational organization with real-time operational teams split between mainland China and the rest of the world.

Do we need to replace our existing PBX and carrier contracts to adopt Teams Phone System?

Not necessarily. Direct Routing through a cloud SBC is designed to work alongside existing carrier trunks and numbers, which is why this client kept its published support and sales numbers unchanged. Legacy PBX hardware can be retired on your own timeline once call queues and auto-attendants have been re-platformed onto Teams, rather than as a forced cutover.

Planning Similar Regional Collaboration Work?

If your organization is weighing how to give China-based and international teams a consistent Microsoft Teams experience — or you're still running voice through a legacy PBX that Teams can't reach — it's worth scoping the problem before it costs another release cycle or another missed incident window. Brocent's Managed IT & Cloud Services team has run this exact pattern for multi-region organizations across APAC.

Get in touch for a 15-minute, no-obligation consultation, or explore our Microsoft Teams Solutions and Cloud Solutions pages to see how we approach China-to-global connectivity. You can also review our pricing for managed collaboration and telephony engagements.

Related reading:

• Securing a Multinational's APAC Expansion: An Entra ID & Microsoft 365 Infrastructure Case Study
• Microsoft 365 & Entra ID Security Audits in APAC: What Gets Checked and Why It Matters
• Browse all Case Studies