Why You’re Less Locked In Than You Think: Move the Keys First

A phased approach to migrating identities, access, and devices off of Microsoft while retaining the services you depend on.

Written by Lindsey Jenkins on November 20, 2026

Connect

Many IT teams keep their entire operations on Microsoft because making any change can feel too costly and too disruptive. Pull one thread and everything seems to follow, so leaving things alone often feels like the sensible choice.

A day like November 12 puts that decision under harsher light. One Microsoft 365 failure left email out of reach for nearly a full day and reached the collaboration, AI, security, and management tools that share its foundation. Outages happen, so the useful question isn’t who to blame. It’s what this day revealed about your own environment.

When one service fails, how much of your environment fails with it? And if you wanted to reduce that exposure, how much of your environment would have to change?

For many IT leaders, the answer is “most of it.” That means even one change can look like an all-at-once rebuild. It doesn’t have to. 

Identity and access are the keys: they decide who can sign in and what they can reach. With JumpCloud, you can move the keys first. Migrate identity and access, then devices at your own pace, and reduce your Microsoft dependency one layer at a time.

This applies even if you’ve already moved your collaboration tooling to Google Workspace. If you still rely on Entra ID, Active Directory, or Intune to decide who gets in and which devices are trusted, the same phased path applies to you.

What November 12 Revealed

Trouble started around midday on November 12, when Microsoft 365 users reported problems with Outlook, Exchange Online, Teams, and Copilot. Microsoft’s preliminary post-incident report, as BleepingComputer reported, traced the cause to a software bug introduced in July through an update to its networking gateway servers.

Downdetector received outage reports from 74 countries and territories within an hour, according to the Associated Press.

Email was the most visible casualty, but not the only one. Microsoft said Intune device enrollment, check-in, and compliance policies may have been intermittently affected. The tools IT teams use to manage and respond shared a foundation with the thing that broke.

Create Your Continuity Plan. Start with a Dependency Map.

When identity, devices, and email depend on each other, a failure in one place can reach the rest. This isn’t an argument against consolidation. It’s an argument for knowing exactly what your identity and device controls are tied to, and for being able to change them when you need to.

The Disaster Recovery Journal offered a useful test for you to evaluate your own environment. Map your shared dependencies, and know which critical services have no alternate route.

Use this three-layer check to start mapping your own environment:

  • Identity and access: Which apps, Wi-Fi networks, and VPNs authenticate against Entra ID or AD? Where do your access policies currently live?
  • Devices: Which tool enrolls and secures your Windows, macOS, and Linux devices?
  • Productivity and collaboration: Are you relying on Microsoft 365, Google Workspace, or both?

Answer all these questions, and you’ll quickly see which systems are tied together, and where your keys live.

Why Switching Feels Harder Than Staying

The same entanglement that spreads an outage is what makes changing even one piece feel so risky. The hesitation makes sense. Most Microsoft environments grew over years, one sensible decision at a time. Active Directory (AD) sits underneath applications, file shares, and Windows devices. User profiles hold the settings and files people rely on every day. And nobody wants to be the person who broke application access for the whole company.

So the project gets pictured as a rip and replace. Everything moves at once, or nothing does.

That all-or-nothing picture is the real obstacle. 

Identity, devices, and your productivity suite feel like a single project because they were bought and built together. They aren’t. They are separate pieces, and you can move them in a different order, on different timelines.

Move Identity and Devices at Your Pace

JumpCloud is built for this kind of staged move. Keep the Microsoft services you still need while you move the layers you choose.

Here’s how it works, in four steps:

  1. Coexist. Active Directory Integration (ADI) syncs configured users and groups while AD and JumpCloud run side by side.
  2. Move the keys. Move supported applications to JumpCloud single sign-on (SSO) in batches, with multi-factor authentication (MFA) and conditional access. Roll this out to your IT and security team members first, then early adopters, then everyone else.
  3. Move devices at your own pace. The Active Directory Migration Utility (ADMU) migrates eligible Windows accounts to JumpCloud-managed local accounts, preserving user files and supported profile settings. Linux and macOS devices follow migration methods specific to each operating system.
  4. Connect networks and retire AD. Move supported Wi-Fi and VPN sign-in to Cloud RADIUS. Retire AD once its remaining dependencies are addressed. If you keep Microsoft 365, its sign-in still runs through Microsoft Entra ID, even with JumpCloud SSO. Supported device sign-in, non-Microsoft app access and their administration can move to JumpCloud as dependencies are addressed.

Your migration doesn’t have to hinge on a single cutover weekend. The steps can overlap: applications can move in batches, users can roll out in waves, and application and device moves can run in parallel. This phased migration lets you reduce your Microsoft dependencies on a schedule that makes sense for your business.

Already Using Google Workspace? Give IT Its Own Keys

Your productivity suite shouldn’t dictate your IT stack. Google Workspace can keep handling collaboration while JumpCloud replaces overlapping Microsoft tools for identity and device management.

Here’s what that looks like in practice. JumpCloud’s Google Workspace integration handles user provisioning and synchronization. It adds SSO and JumpCloud MFA through the Workspace SSO integration. HR integrations and dynamic groups automate user creation and access changes for supported applications.

Google Workspace stays for collaboration. IT gets its own keys.

Proof from Teams Who’ve Migrated

This phased migration isn’t theoretical. Pivotree, a 600-employee digital commerce company, replaced AD and Okta with JumpCloud. In three months, the team moved all of its applications with the help of JumpCloud’s Professional Services team.

Amplience, an AI content company, migrated its identity and device management operations to JumpCloud after previously relying on a combination of Jamf and Microsoft Entra. The team now manages 140 applications, including Microsoft tools, plus storage and Wi-Fi access, through JumpCloud. And they’ve built an onboarding process that is nearly zero touch.

Two teams. Two starting points. One phased path forward.

You Don’t Have to Stay Locked In

The November 12 outage raised a plain question for every IT team: when one piece fails, or when you change it, how much moves with it? Today, the answer may be more than you’d like. You aren’t stuck, though. 

Identity and access are the keys to everything else, and you can migrate them first. Devices move on your schedule. Active Directory goes last. Each step is smaller than the all-at-once project it can seem to be. Move at your pace, retain the services you need, and make room for the operating systems, applications, and productivity suites that fit your business.

Where to start depends on your applications, devices, and Microsoft dependencies. Book your migration consultation to speak one-on-one with a JumpCloud expert about your configuration and reliance on Microsoft.

Lindsey Jenkins

Lindsey Jenkins is the Content Manager at JumpCloud. She's spent the past 10+ years of her career developing content for B2B tech brands. Outside of work, she enjoys singing, playing basketball, and reading fantasy books.

Continue Learning with our Newsletter