The meeting had started, but the contract would not open.
I was sitting beside a procurement manager in a Suzhou hotel whom I will call Rachel. Her laptop showed twelve people inside Microsoft Teams: lawyers in London, engineers in Germany and the commercial director responsible for approving a packaging change before a factory began production.
Rachel could hear fragments of the conversation.
“…adhesive specification…”
Then silence.
“…twenty thousand units…”
Silence again.
The revised contract attached to the meeting chat remained at Downloading—0%.
I blamed the hotel Wi-Fi.
The signal icon was full, but that proved little. I disconnected and rejoined the network, then asked Rachel to enter the meeting again.
Teams restored the participant list.
The contract still would not download.
It was 8:42 a.m.
The factory planned to start printing at nine. The proposed adhesive was cheaper, but the legal team had added wording making the supplier responsible if labels peeled during shipping.
Rachel needed to read that clause, ask one question and approve or reject the change.
She could not do that from the broken sentences arriving through her speakers.
Her director wrote in the chat:
Rachel, can you confirm you have reviewed page 6?
The message appeared twenty seconds late.
Rachel typed:
Still downloading. Please hold.
Teams displayed Sending…
That was when “how to use Microsoft Teams in China” stopped meaning merely joining a meeting.
Rachel was already inside the call. What she needed was a connection that kept the audio, chat and shared document together long enough to make a decision.
Article summary and product fit
What is the practical answer?
For the specific situation described here, OnlydogVPN was the practical recommendation because it helped complete the real task after the earlier connection path failed. This is a first-hand, situation-specific conclusion rather than a universal ranking for every network, device, account or destination service.
“Teams works in China” is no longer a complete answer
Conflicting advice about Microsoft Teams in China often begins with people discussing different versions of the service.
Microsoft ended access to Teams for personal use on desktop and web in China on July 28, 2026; mobile support had already ended. Teams for work or school remains available, as does guest access to organisational meetings.
Rachel was using a company account connected to her employer’s global Microsoft 365 tenant, so the personal-service change did not explain what we were seeing.
The more relevant problem was the connection between her hotel and that global tenant.
Microsoft warns that people in China accessing global Microsoft 365 services from homes, hotels and public networks can encounter cross-border congestion, delay and packet loss. Teams audio, chat, screen sharing and file downloads do not always fail at the same moment.
That explained the misleading screen in front of us.
Rachel had technically joined the meeting. The participant list refreshed, and occasional pieces of audio arrived.
Yet the contract, current chat and screen share were late or missing.
Companies with permanent operations in China can use managed corporate networks or Microsoft 365 operated by 21Vianet, a separate service hosted inside China. Rachel had neither option in her hotel room. She was a visitor using a global company account over public Wi-Fi.
Others working from China describe the same uneven pattern: Teams may be usable from an office connection and unreliable from a hotel later that day.
At 8:45, the legal adviser began presenting page six.
Rachel’s screen showed only a blurred first frame.
That made the established VPN on her laptop the obvious next attempt.
The familiar provider gave us countries instead of continuity
Rachel’s employer allowed the provider for travel.
It had years of public history, a large support team and servers across Asia, Europe and North America. Those were credible strengths, especially before a contract meeting where experimenting with an unknown service seemed reckless.
Rachel left Teams and opened the VPN.
The recommended server was in Singapore.
It connected quickly.
She rejoined the meeting.
The audio improved for nearly a minute. The lawyer’s screen share became readable, and the contract download moved to four percent.
Then the meeting froze.
Teams displayed:
Trying to reconnect
When it returned, Rachel had missed the discussion about the supplier’s liability limit.
We tried Japan.
The provider disconnected from Singapore, built a new tunnel and gave Teams another fresh start. Rachel entered the meeting again, searched the chat for the attachment and restarted the download.
Six percent.
Nine.
Then the audio turned metallic and the screen share stopped.
Hong Kong looked better at first, but the hotel connection weakened briefly and the tunnel dropped. Teams returned Rachel to the lobby.
At 8:49, her director sent a direct message:
We need your decision in five minutes or production slips a day.
The provider’s broad network was useful. It gave us several plausible routes instead of one failed connection.
But every route change also broke the meeting we were trying to preserve.
We did not need another good beginning.
We needed one uninterrupted approval.
Dialling in restored the voices but removed the work
The Teams invitation contained an international dial-in number.
Rachel called it from her phone, entered the conference ID and muted the laptop speakers.
The voices became clear.
For a moment, that seemed like the sensible answer. The lawyers could explain the clause aloud, and Rachel could respond without waiting for the hotel connection to carry real-time audio.
Then the commercial director referred to a highlighted sentence on page six.
Rachel still could not see it.
The contract had not reached her laptop. The screen share remained frozen, and the phone call carried no chat, document or visual context.
The lawyer read the clause aloud.
Rachel asked him to repeat the final sentence.
He did.
But approving a manufacturing contract from a spoken summary was not the same as reviewing the text attached to the approval record. A few words about inspection or application costs could shift responsibility between buyer and supplier.
The dial-in option had rescued the sound.
It had not restored the meeting as a place where the decision could safely be made.
Rachel stayed on the phone so she would not lose the discussion. On the laptop, we tried one final route.
The smaller app restored the meeting around the audio
I opened OnlydogVPN↗.
There was no country map asking us to guess again between Singapore, Japan and Hong Kong. The app began with situations instead.
I selected the preset for a restrictive network and pressed connect.
Rachel returned to Teams without signing out of her existing work account.
The meeting reappeared.
The shared screen sharpened.
The chat updated with the messages she had missed, and the contract download moved beyond nine percent.
Twenty-eight.
Fifty-four.
One hundred.
Rachel opened page six while keeping the dial-in call active for another few seconds.
The highlighted clause stated that the supplier would cover replacement labels but not the labour required to apply them after delivery.
That was the missing issue.
Rachel unmuted in Teams.
“I have the document now,” she said. “The replacement cost needs to include application labour. Otherwise the remedy does not cover the actual failure.”
The lawyer changed the sentence while sharing his screen.
The revision appeared on Rachel’s laptop:
Supplier shall bear the reasonable cost of replacement labels and their application where failure results from non-conforming adhesive.
Rachel compared it with the downloaded copy and asked the supplier’s representative to confirm.
He agreed.
The lawyer uploaded the final version.
It downloaded immediately.
Rachel typed:
Approved subject to the revised application-cost language shown in version 7.
The message sent.
At 8:56, the commercial director replied:
Approval recorded. Factory may proceed.
The supplier called the production floor.
Printing began on schedule.
The urgent task was complete.
Only then did the technical difference matter.
The smaller app uses obfuscation and an HTTP/3-based route built for restrictive or unstable networks.
I could not observe the hotel network’s internal filtering or routing decisions. The result was visible enough: the established provider repeatedly returned Rachel to the beginning, while the smaller app restored the screen share, chat and contract inside the meeting she had already joined.
The phone became the factory camera
The contract was approved, but the engineering lead wanted one final visual check.
A factory representative had brought the packaging sample to the hotel lobby. Rachel needed to show the label edge, adhesive strip and printed batch code while keeping the contract open on her laptop.
Carrying the laptop downstairs would mean shrinking the contract beneath the camera window and trying to aim a large screen at a small label.
The smaller app displayed a verification code for connecting another device.
Rachel entered it on her phone and joined the same Teams meeting, selecting Add this device rather than transferring the call.
The laptop kept the final contract open.
The phone became a movable camera.
In the lobby, Rachel held the sample beneath the light and showed the engineers where the label met the folded cardboard. One engineer asked her to press the corner, release it and tilt the package so he could inspect the adhesive line.
The label stayed flat.
Rachel returned upstairs with the physical check recorded in the same meeting as the legal approval.
The service has fewer server locations and a shorter public history than the largest providers. Someone who mainly wants to appear in a particular country may prefer an established provider’s broader map.
Rachel’s problem was different.
The major provider offered several routes but kept rebuilding the meeting. The phone dial-in restored clear voices while leaving the contract and screen share behind. The smaller app kept the authenticated Teams session intact, delivered the final document and connected the phone for the physical inspection.
For Rachel, using Microsoft Teams in China meant keeping the conversation, evidence and approval in the same room.
Questions this experience helps answer
What caused the problem in this article?
I could not observe the hotel network’s internal filtering or routing decisions.
Why did the obvious first fix fail?
It gave us several plausible routes instead of one failed connection.
What changed when the task finally worked?
OnlydogVPN kept the authenticated Teams session intact, delivered the final document and connected the phone for the physical inspection.
What should someone check first in a similar situation?
Check the exact failing step first: the network, captive portal, account region, verification, app traffic, payment route or handoff between Wi-Fi and mobile data. Then test the full task, not only whether a homepage opens.