CLIENTS

Windows 365 best deployment practice guidance: Choose the best connectivity methods for your user base.

Overview

Windows 365 supports multiple methods for connecting users to their Cloud PCs. The base of all of these methods is Windows App, which is integrated with Microsoft cloud management, delivers a consistent end-user experience across devices, and aligns to Zero Trust principles.

Windows App provides a unified experience across Windows, macOS, iOS, and Android, and provides the foundation for dedicated devices such as Windows 365 Link, and partner thin clients building on our SDK.

Connecting to Windows 365

There are several ways to connect to Windows 365, depending on your scenario.

  • Windows App – gives users a unified access experience for Windows 365 and other Windows cloud experiences on users existing devices.
  • Windows 365 Boot – allows users to sign directly into their Cloud PC from a physical Windows device, reducing reliance on the local desktop experience.
  • Windows 365 Link – provides a purpose-built Windows 365 endpoint experience for direct Cloud PC access.

You can compare the capabilities and functionalities of the options here.

The cloud-native step by step approach

The goal is to provide the best possible user experience, delivering simplicity to the end user and IT admin, whilst maintaining zero trust principles.

  • Determine the best endpoint device for your scenarios. Existing corporate devices, mobile devices, BYOD or dedicated clients such as Windows 365 Link or Partner Thin Clients.
  • Ensure Network optimisation from all client networks. Utilise the health check capabilities within Windows App to validate from corporate, remote, and partner network locations.
  • Ensure Automatic Updates are in place. Windows App is regularly updated, so ensure that clients are able to retrieve the updates from the Microsoft Store.
  • Review device redirection against your security requirements. Redirection of local drives, printers, cameras, microphones, and the clipboard is what makes a Cloud PC feel like a local device. Decide deliberately which are permitted, because the defaults may be more or less permissive than your policy intends.
  • Point users at Windows 365 Switch if they use both a physical PC and a Cloud PC. No configuration is required once Windows App is installed, but users won't discover it in Task view unless told. Include it in onboarding material.

Decision guidance

Scenario Guidance
New Windows 365 deployment Start with Windows App for broad access and evaluate Link, Boot, or Thin Clients by persona.
Existing thin-client estate Avoid expanding the thin-client footprint by default. Ensure your Thin Client vendor utilises the Windows App SDK, and ensure these are kept updated as per the vendor support timelines.
Shared or frontline device scenario Evaluate Windows 365 Boot or Windows 365 Link to simplify sign-in and reduce local device dependency.
Highly controlled kiosk-like endpoint Evaluate Link or Boot. Ensure all connectivity from other solutions uses the Windows App.
Legacy VDI transition Use Windows 365 to move access, management, and security toward cloud-native operations while preserving flexibility for exceptions.

Related content

Next steps

After the client path is validated, review how the recommended deployment model improves day-two operations and support.

Supportability: operational benefits of a cloud-native deployment

  • Last updated on