Intune device management in Chengdu

A Intune device management project in Chengdu looks simple on a spreadsheet and rarely stays that way. The first question is the one nobody asks outside China: the global Microsoft tenant, or the local 21Vianet service? From there it becomes a design exercise — keeping mail flowing, Teams history intact, and an audit trail your head office can actually read.

We run the whole sequence for foreign-owned companies in Chengdu: audit first, then tenant and licence design, then the cutover, then the weeks of settling-in while the small faults surface. Nobody enjoys a migration; the job is to make it unremarkable.

What makes Intune device management in Chengdu a different project

Treat the two clouds as different products, because that is what they are. Licences differ, some features behave differently, and performance comes down to how traffic leaves your office and where it joins Microsoft’s network. Then there is the compliance angle: where personal data may legally sit, and what you can hand to a regulator or a head office when they ask.

Nobody touches a mailbox until the audit is done: what you are licensed for, how Domains and DNS are set, which mail rules exist, how Teams and SharePoint are genuinely used, how identity is configured, and where the devices are enrolled. Most migrations take a few weeks end to end.

What we migrate

• Mailboxes, mail flow and shared mailboxes
• Teams and channels, carrying chat history across where the move supports it
• SharePoint and OneDrive content, with permissions verified on both sides
• Entra ID, groups, sign-in policy and conditional access
• Endpoint policy and Intune device enrolment
• DNS records, domains, and the licence position on the new tenant

Mailboxes go first and collaboration content follows, so the team keeps working while the rest of the estate catches up.

How the project runs, step by step

1. Audit the current tenant and the actual business requirements
2. Design the destination — tenant choice, licensing, routing
3. Run a pilot group and record what actually changes for users
4. Cut over in a planned window; we schedule it for a weekend
5. Hypercare — we stay on for hypercare, while the small faults surface
6. Hand over documentation, and support what we left behind

Where we work

We are not a single-city provider. NETK5 dispatches engineers across mainland China: our own team is based in Shanghai, Beijing, Guangzhou and Hong Kong, and we staff projects elsewhere in the country as clients need them — Xi’an, Chengdu, Taixing and beyond. Outside China we have delivered rack-and-stack work and WiFi surveys in Japan, Korea, Singapore and Taiwan, usually for international companies coordinating several sites from a head office that has never been on site.

For Intune device management in Chengdu that matters in a practical way: work can be planned around a visit rather than a relocation, and the same team that surveys or installs can hand over documentation the head office can actually use.

Our experience

Since 2002 we have looked after IT for international companies in China, and Microsoft 365 sits at the centre of most of it. We have run a pilot migration of Microsoft 365 from the global tenant to 21Vianet for a client operating in China, and we manage cloud estates day to day — including an environment of more than thirty Azure virtual machines with Microsoft 365 alongside it. Our clients include names such as Siemens, Nestlé, McKinsey and JLL, usually alongside the international IT companies whose client sites we support.

The questions that come up every time

Do we have to move to 21Vianet if we are in China?

It is a choice, not a requirement. Many foreign-owned companies stay on the global tenant and live with the trade-offs: performance, routing, and how easy it is to evidence how data is handled. We also handle moves the other way, from 21Vianet back to global, when a business restructures or exits. Your users, your regulator and your head office decide it, which is why the audit comes first.

How long are users without email?

Very little, if the cutover is planned properly: mail flow flips inside a window, users sign in again, work resumes. The time goes into the days afterwards — profiles, devices, shared mailboxes, and the odd Teams channel that behaves differently.

Can you support us after the migration?

Yes, and a good share of our migration work becomes ongoing support — helpdesk in English and Chinese, monitoring, and someone who already knows how your tenant was built.

Talk to us about Intune device management in Chengdu

Tell us what you have now and what you need to end up with — tenant, users, sites, and any deadline driving it. We will tell you what the move involves and what it costs before anyone starts.