Latest / The Windows Podcast with Fexingo: Microsoft, PC, and Enterprise Windows Conversations / How Microsoft 365 Copilot Is Changing the Windows Desktop
Transcript
- Lucas: Microsoft is quietly building a feature that could fundamentally change how enterprises deploy Windows, and it has nothing to do with the next major version of the OS. It's called Windows 365 Switch, and it lets users stream a full Windows 11 desktop from the cloud directly onto their local machine, seamlessly switching between their local desktop and the cloud-hosted one. Luna: Wait — so it's like having two Windows desktops running simultaneously on the same physical hardware, one local, one remote? Lucas: Exactly. Windows 365 Switch creates a virtual layer where you can press a keyboard shortcut — I think it's Control+Windows+left or right arrow — and instantly move from your local desktop to a cloud-hosted desktop that lives in Microsoft's Azure data centers. It's not a full virtual machine you manage yourself; it's a pre-configured Windows 11 environment that's assigned to you as a user license. Luna: And this is aimed at enterprises that already have Microsoft 365 subscriptions, right? It's an add-on to the existing licensing. Lucas: Right. You need either Windows 365 Business or Enterprise licensing, which starts at around $31 per user per month for the basic tier — one virtual core, 2 gigs of RAM, 64 gigs of storage. That's per user, per month, on top of whatever you're already paying for Microsoft 365 and Windows licenses. The Switch feature itself rolled out in preview last year, but it became generally available in February of this year, 2026. Luna: So if you're running, say, a hundred users in your accounting department, you're looking at an extra $3,100 a month just for the cloud desktops. That's not pocket change. Lucas: No, it's not. But Microsoft's argument is that you can stop worrying about hardware refresh cycles, security patching, and even data loss because the desktop lives in the cloud. If a laptop gets stolen, the cloud desktop is still there — you just log in from another device. There's no local data to compromise. Luna: That sounds like the classic pitch for desktop virtualization that Citrix and VMware have been making for over a decade. What's different about Microsoft's approach? Lucas: The integration. With Citrix or VMware, you typically need a separate infrastructure team to manage the virtual desktop hosts, the connection brokers, the gateways. Windows 365 is a managed service — Microsoft handles the backend. You just assign licenses through the Microsoft 365 admin center and users get their cloud PC within minutes. And the Switch feature makes it feel less like you're remoting into a separate machine and more like a native desktop experience. Luna: I've heard some early adopter feedback that says the latency can be noticeable, especially if you're not on a wired Ethernet connection. What's the reality? Lucas: It depends heavily on your internet quality. Microsoft recommends a stable connection with at least 10 megabits per second for basic productivity — think Office apps, web browsing — and 20 to 40 megabits for more demanding tasks like video conferencing or software development. If you're on Wi-Fi, it's workable but you'll feel the occasional stutter. One IT manager I spoke with said their users in the Chicago office, which has a dedicated fiber line, reported near-native performance. But their users working from home on cable broadband noticed a half-second delay when switching between windows. Luna: That half-second adds up over a full workday. And if you're running latency-sensitive applications, like CAD software or video editing, it's probably not going to cut it. Lucas: Microsoft knows this. They're positioning Windows 365 for what they call 'knowledge workers' — people who live inside Microsoft 365 apps, browsers, and line of business web applications. Not for engineers running MATLAB or designers using Adobe Premiere. For those heavy workloads, you'd still need a powerful local machine. Luna: So it's a complement to local computing, not a replacement. But I can see the appeal for IT departments that want to standardize on a single desktop image and push updates centrally. Instead of managing 500 physical laptops with different configurations, you manage one cloud desktop image. Lucas: Exactly. And that's where the real cost savings might come from — not on the per-user licensing, but on the productivity gains from zero-downtime updates and consistent user experience. If a critical security patch comes out, IT can update the cloud image and users get it the next time they log in. No weekend patching marathons. Luna: But there's a downside: if your internet goes down, you can't access your cloud desktop at all. Some of Microsoft's competitors, like Parallels, offer local caching that lets you work offline and sync later. Does Windows 365 have anything like that? Lucas: Not yet. The current architecture requires a continuous connection to the cloud PC. Microsoft has talked about offline capabilities in future updates, but for now, if you lose connectivity, you're stuck with whatever local apps you have. That's one reason I think Windows 365 Switch is best used in a hybrid model — users have a local desktop with their basic tools, and they use the cloud desktop for sensitive or standardized work. Luna: So they can fall back to local if the cloud goes down. That makes sense. But it also means you're paying for two desktops essentially — the local hardware plus the cloud subscription. Lucas: Right, which is why I think the target audience right now is specifically organizations with high security or compliance requirements. Think financial services, healthcare, government — where data sovereignty and audit trails are paramount. In those environments, the ability to ensure that no sensitive data ever touches the local device is a huge selling point. Luna: And Microsoft is making it easier to adopt, too. They recently introduced Windows 365 Boot, which lets a device boot directly into the cloud desktop, bypassing the local OS entirely. That seems like a clear signal that Microsoft wants this to be the primary desktop experience eventually. Lucas: Yeah, Windows 365 Boot is interesting. It's essentially turning your physical PC into a thin client. You turn it on, it authenticates to Azure, and you get your cloud desktop immediately. The local Windows installation is still there, but the user never sees it. For organizations that are migrating from legacy thin-client setups, that could be a seamless transition. Luna: But this also raises a bigger strategic question for Microsoft. If you're already paying for Windows 365, do you still need a regular Windows license? The cloud desktop itself includes a Windows license, but the local device still needs an OS to boot into. Lucas: That's the clever part. Microsoft's licensing now effectively charges you twice: once for the device's local Windows license — usually included in the hardware cost — and once for the cloud Windows license embedded in the Windows 365 subscription. For enterprises that already have volume licensing, the cloud desktop license might be covered under certain agreements, but it's complicated. I've seen IT consultants advising clients to audit their licensing carefully before jumping in. Luna: This feels like a precursor to a world where Windows itself becomes a subscription service, not just an add-on. You can already see the outlines: Microsoft 365 gives you the apps, Windows 365 gives you the desktop, and eventually the local OS might just be a thin layer that connects to the cloud. Lucas: That's exactly where this is heading. I'd expect within five years, Microsoft will offer a 'Windows 365 Edition' that essentially replaces the traditional perpetual license model. You won't buy Windows 12 or whatever comes next — you'll subscribe to 'Windows 365 Enterprise' and get your desktop streamed from Azure. The local device becomes a terminal. Luna: And that would be a massive shift for enterprise IT. It means no more managing local images, no more BitLocker recovery keys on lost devices, no more worrying about local malware persistence. But it also means total dependency on Microsoft's cloud infrastructure and internet connectivity. Lucas: And let's not forget the data gravity implications. If your entire desktop is in Azure, it becomes much easier to also move your file storage, your line of business apps, your authentication — everything — into Microsoft's ecosystem. It's a lock-in that goes beyond just the operating system. Luna: So for IT leaders listening right now, what's the practical takeaway? Should they be piloting Windows 365 Switch? Lucas: I'd say yes, but only if you have a clear use case. If you have a workforce that's already fully remote and you're struggling with device management, it's worth testing with a small group. Start with a department that primarily uses web apps and Microsoft 365. Measure the performance, especially on latency. And do a total cost of ownership analysis — factor in the licensing costs, the reduced hardware refresh cycle, and the IT time saved on patching. I've seen one estimate that for a 500-user organization, the break-even point is around three years, assuming you extend hardware life from three to five years. Luna: That's the kind of concrete number that helps decision-makers. And if today's episode gave you something to think about, we'd love to hear from you — our listener support is what keeps this show ad-free and independent. If you found value in this conversation, consider buying us a coffee at buy me a coffee dot com slash fexingo. It's a small gesture that makes a big difference for us. Lucas: Yeah, genuinely — if this episode saved you an hour of research or gave you one insight you'll use, that link is buy me a coffee dot com slash fexingo. We appreciate every single supporter. Luna: And to close out the topic: I think the big question is whether Windows 365 Switch is a stepping stone or a destination. What do you think, Lucas? In five years, will most enterprise desktops be cloud-streamed? Lucas: Not a majority. I think we'll see a bifurcation: high-security, compliance-heavy roles will go cloud-first. Knowledge workers with modest computing needs might also adopt it. But power users — developers, designers, engineers — will keep local desktops for the foreseeable future. The technology isn't ready to replace local computing entirely, and I'm not sure it ever will be. But for a significant slice of the enterprise, Windows 365 Switch is a legitimate option today, and it's only going to get better.