Remote Desktop Without Leaving Your PC Switched On: Windows 365, Azure Virtual Desktop or Remote Access?

This question has been published anonymously. Details that could identify the person or organisation have been removed.

The Short Answer

There Are Three Different Ways to Solve This

Before comparing products, it is worth being clear about which model you are actually choosing. There are three fundamentally different approaches.

Option 1 — Remote Control of an Existing PC

Tools such as TeamViewer, LogMeIn and Splashtop let you control your physical PC from another device. The existing PC stays switched on, connected to the internet and running Windows. You see and control that machine remotely.

• Advantages: familiar desktop, existing applications, existing files in place, minimal migration, often quick to configure
• Disadvantages: the physical PC must remain powered on; a local power cut or internet outage stops remote access; a Windows update or unexpected reboot interrupts the session; hardware failure stops access entirely; the remote-access software becomes another security dependency
• Best suited to: occasional access, temporary requirements, remote support, or situations where migrating the desktop is not justified

Option 2 — Cloud PC / Desktop as a Service

Products such as Windows 365 and Amazon WorkSpaces Personal move the desktop itself into a cloud data centre. The user connects from a laptop, desktop, tablet or browser. There is no physical office PC that must remain switched on. Files, applications and settings remain on the hosted desktop.

• Advantages: persistent desktop accessible from different locations; no dependency on a physical PC being powered; central management; easier device replacement; data can remain in the hosted environment; predictable user experience
• Potential disadvantages: recurring monthly cost; internet connection always required; applications must be installed or migrated; peripheral compatibility needs checking; printing and scanning need testing; performance depends on service sizing and the quality of the connecting network

Option 3 — Virtual Desktop Infrastructure

Platforms such as Azure Virtual Desktop (AVD) go further, providing a full virtual desktop environment hosted in Azure. AVD can support personal or pooled desktops, multiple users, shared session hosts, application delivery, autoscaling and custom networking. It is more powerful and more flexible than a straightforward Cloud PC — but also more complex to design, deploy and manage. It is considered separately in its own section below.

Windows 365

Windows 365 provides a persistent Windows Cloud PC hosted by Microsoft. The user receives essentially their own Windows desktop in the cloud — the same environment every time they connect, regardless of which physical device they are using.

Users access their Cloud PC through the Windows App (the current supported client for Windows 365 and Azure Virtual Desktop access). Microsoft has moved away from the older Remote Desktop client for this purpose. Verify the current client name and method at Microsoft Learn before documenting this for users.

• Persistent personal desktop — the same Windows environment every session
• Microsoft ecosystem integration — works naturally with Microsoft 365, Microsoft Entra identity and (depending on edition and licensing) Intune device management
• Predictable per-user monthly licensing — easier to budget than consumption-based Azure infrastructure
• Simpler architecture than a full Azure Virtual Desktop deployment
• No need to manage underlying Azure infrastructure directly

• Fixed recurring cost regardless of usage — the Cloud PC runs continuously
• Licence sizing must match the workload — choose too small and performance suffers; too large and you overpay
• Less infrastructure flexibility than Azure Virtual Desktop for complex requirements
• Local device and peripheral requirements still apply — camera, microphone, printer and peripheral compatibility depend on the connecting device

Azure Virtual Desktop

Azure Virtual Desktop (AVD) is Microsoft's more flexible virtual-desktop platform. Where Windows 365 gives each user a straightforward personal Cloud PC, AVD allows more complex configurations: personal or pooled desktops, multiple users sharing session hosts, published applications, autoscaling, custom networking and tighter integration with the broader Azure platform.

• Flexibility: pooled desktops, application delivery, autoscaling, custom Azure networking
• Potentially efficient for several users sharing resources
• Full control over the underlying Azure infrastructure
• Can be cost-effective at scale with good design

• More design, administration and ongoing management than Windows 365
• Azure cost management requires attention — compute, storage, networking and backup all have separate costs
• Requires decisions about profile design (typically FSLogix), image management, scaling configuration and monitoring
• Skills and ongoing management overhead may outweigh the flexibility for simple requirements

Amazon WorkSpaces Personal

Amazon WorkSpaces Personal provides persistent virtual desktops through AWS. Users receive the same personal desktop each time they connect. AWS offers monthly AlwaysOn pricing options and AutoStop configurations where the WorkSpace suspends when not in use, which can suit intermittent users.

Note on current product availability: Amazon WorkSpaces Pools is no longer available to new customers from July 2026 and is being retired. Amazon WorkSpaces Personal remains the relevant product for persistent individual desktops. Verify current AWS product status at aws.amazon.com/workspaces before recommending.

• Mature Desktop-as-a-Service platform with a long track record
• Persistent desktop accessible from multiple devices
• AutoStop configuration can reduce cost for less frequent users
• Strong fit for organisations already invested in AWS infrastructure

• Introduces a second cloud platform where the organisation otherwise uses Microsoft
• Windows licensing structure differs from the Microsoft model
• Administration tools and identity integration may be less familiar to Microsoft-focused SMEs
• Application and identity integration with Microsoft 365 requires planning

Could I Just Create a Windows Virtual Machine in Azure?

Technically, yes. Azure allows you to create a Windows desktop-class virtual machine. But there is an important distinction between a raw Azure virtual machine and the managed services above.

A raw Azure VM for remote desktop access introduces decisions that Windows 365 and AVD handle for you: operating system licensing for remote access, secure remote connectivity, identity integration, RDP security, endpoint protection, patching, backup, disk configuration, networking, VM start and stop automation, monitoring, and cost management. Each of these is solvable — but each requires a decision and an implementation.

Exposing TCP port 3389 — the default Remote Desktop Protocol port — directly to the internet is strongly inadvisable. It becomes an immediate target for automated credential attacks. A raw Azure VM used as a remote desktop must be protected through a proper approach: Azure Bastion, a VPN gateway, Conditional Access or a similar secure access method. The technically simplest way to build a remote Windows computer is not always the simplest way to operate one securely.

Quick Decision Tree

Work through these questions in order to identify the likely starting point.

• Do you genuinely need the exact same Windows desktop? No → Consider a managed laptop plus Microsoft 365 instead
• Is this mainly one person? Yes → Consider Windows 365 first
• Several users, pooled desktops or shared applications? Yes → Consider Azure Virtual Desktop
• Already heavily invested in AWS, or intermittent use makes usage-based pricing attractive? Yes → Consider Amazon WorkSpaces Personal
• Only need occasional access to an existing physical PC, and leaving it on is acceptable? Yes → Consider TeamViewer, LogMeIn or equivalent remote-access software
• Very specific server-like requirement? Possibly → Azure VM, but only after verifying licensing and designing access security properly

Which Would We Choose?

One user, wants the same desktop every day, Microsoft 365 business

Likely starting point: Windows 365. A persistent Cloud PC that the user can access from any device, without leaving a physical machine running.

One or two users, only need access occasionally, AWS already in use

Consider: Amazon WorkSpaces Personal with an AutoStop configuration so the desktop suspends when not in use.

Several users, shared applications, variable usage

Consider: Azure Virtual Desktop, where pooled resources and autoscaling become worthwhile.

Very specific server-like requirement

Potentially: an Azure VM — but only after confirming licensing is correct and remote access is properly secured.

Occasional access to an existing PC, leaving it switched on is acceptable

Potentially: TeamViewer, LogMeIn or equivalent. Simple to configure for occasional use.

Why Windows 365 Is Often the Right Starting Point Here

For the scenario described — one person, Microsoft 365 environment, wants the same desktop from different locations without leaving a PC running — Windows 365 would usually be the first solution IT Club would price.

It provides a persistent Windows Cloud PC, integrates naturally with the existing Microsoft environment, avoids leaving a physical machine running, has a predictable monthly cost and is substantially simpler to manage than building a full Azure Virtual Desktop deployment.

But before finalising that recommendation, we would want to understand:

• Existing Microsoft licensing — to confirm whether the Windows 365 licence is additive or overlaps with anything already in place
• CPU, memory and disk requirements — particularly for any specialist or resource-intensive applications
• Specialist applications — line-of-business software, design tools, accounting packages and similar applications need compatibility checking
• Printing and scanning requirements — these need testing against the specific devices the user has
• Video conferencing — Teams optimisation and camera and microphone behaviour depend on the configuration
• Authentication and Conditional Access — how the user signs in and what access controls should apply
• Local device — what the user will connect from and whether it meets the requirements
• Backup requirements — what data needs protecting and how
• Data location — where files and application data should reside
• Broadband quality — performance at home and from regular travel locations

The Internet Connection Still Matters

Moving the PC to the cloud removes the dependency on the home or office PC being powered on. It does not remove the dependency on a usable internet connection at both ends.

Cloud desktop sessions typically carry display output, keyboard input, mouse movements, audio and peripheral traffic — not the full desktop application running locally. This means the bandwidth requirement is lower than downloading large files, but latency and connection stability matter significantly for a responsive experience.

Poor connectivity can still cause delayed input response, blurry display, audio quality problems and disconnections. Wi-Fi quality at the connecting location matters as much as the broadband connection itself.

What About Printing?

Printing from a cloud desktop is usually solvable but worth testing before deployment rather than assuming it will work automatically. Possible approaches include local printer redirection through the remote desktop session, cloud printing, Universal Print (Microsoft's cloud print management service where available under the appropriate licence) and application-specific printing.

Compatibility depends on the platform, printer manufacturer, driver requirements, session security configuration and what the user is printing from. Some driver-heavy printers are straightforward to redirect; others are less predictable.

Video Calls

Teams, Zoom and other video conferencing tools can be more demanding on a virtual desktop than standard productivity applications. Unoptimised video conferencing inside a cloud desktop can consume significant bandwidth and processing on the host, and may produce lower quality than expected.

Windows 365 supports Teams optimisation, which offloads media processing to the local device rather than running it through the cloud desktop. This produces a substantially better Teams experience when properly configured. Verify current Teams optimisation support and configuration requirements with Microsoft documentation. Camera and microphone compatibility depend on the connecting device and session configuration.

Files, OneDrive and the Question You Should Ask First

If the user already has Microsoft 365, OneDrive and SharePoint are likely already in use — or could be. This raises an important question before building a cloud desktop at all.

If the requirement is access to Word, Excel, Outlook, Teams, OneDrive, SharePoint, a browser and standard Microsoft 365 applications, a properly configured laptop may provide everything the user needs without creating a cloud desktop infrastructure at all. The user logs into Microsoft 365, files are in OneDrive and SharePoint, email and calendar are in Outlook, and collaboration happens in Teams — from any suitable device.

The Better Question: Do They Need the Same Desktop — or Just the Same Work?

There are four genuinely different requirements that can all feel like the same problem:

• The same applications and files accessible from anywhere → A managed laptop plus Microsoft 365 may be sufficient. No cloud desktop needed.
• The exact same Windows environment with personalised settings and application state → A Cloud PC (Windows 365 or equivalent) makes sense.
• Specialist software that must remain centralised and cannot be installed locally → AVD, Windows 365 or another virtual desktop may be appropriate.
• Access to a specific physical machine with specific local data or peripherals → Remote-control software remains relevant, accepting the dependency on that machine being on.

Establishing which of these is the actual requirement usually changes the answer significantly.

Security

A Cloud PC can reduce local data exposure — if sensitive files stay in the hosted environment rather than on a travelling laptop, the risk of a lost or stolen device creating a data breach may be lower. But moving Windows into the cloud does not automatically create a secure environment.

• Multi-factor authentication is essential — ideally phishing-resistant (passkeys or FIDO2 security key) for administrator accounts
• Conditional Access policies should control which devices and locations can access the Cloud PC
• Device compliance — the connecting device should meet defined security standards
• Endpoint security should be applied to the Cloud PC itself
• Least privilege — users should not have local administrator rights on the Cloud PC unless genuinely required
• Session controls — clipboard, drive redirection, USB redirection and printer redirection should be configured deliberately, not left at permissive defaults
• Patching — Windows Update and application updates on the Cloud PC need active management
• Monitoring and session timeout policies should be in place
• Administrator accounts should be separate from day-to-day user accounts

Cost

We do not publish specific pricing because it changes and depends on configuration choices. But the cost models are worth understanding:

• Windows 365 — predictable monthly per-user Cloud PC licence. Size determines cost. Runs continuously.
• Azure Virtual Desktop — combination of Azure infrastructure consumption (compute, storage, networking) and relevant Microsoft licensing. Autoscaling can reduce costs for pooled desktops during off-peak periods.
• Amazon WorkSpaces Personal — monthly AlwaysOn pricing, or AutoStop configuration where the desktop suspends when inactive. AutoStop can suit intermittent users.
• Azure VM as a desktop — compute cost (which runs unless you stop it), storage, networking, backup, licensing and management overhead all add up separately.
• Remote-access software — software licence cost plus the electricity and hardware cost of maintaining the physical PC that must remain running.

The total cost of any of these options includes setup, ongoing support, patching and update management, backup, monitoring, licensing, user downtime from problems and any hardware dependency. A managed Cloud PC that requires very little IT intervention each month may be better value than a raw Azure VM that requires regular attention.

The IT Club Answer

For the scenario described, I would probably price Windows 365 first rather than jumping straight to a normal Azure virtual machine.

Windows 365 gives the user a persistent Windows Cloud PC without requiring the existing computer to remain switched on, and it is usually simpler to operate than a bespoke Azure desktop. It sits within the Microsoft ecosystem the business already uses, has a predictable cost and requires less infrastructure design than a full Azure Virtual Desktop deployment.

Azure Virtual Desktop becomes more attractive when there are several users, shared resources, pooled desktops or more complex requirements that justify the additional design and management overhead.

Amazon WorkSpaces Personal is also a genuine alternative — particularly where AWS is already part of the business environment, or where intermittent use makes an AutoStop model attractive.

But before doing any of those things, I would challenge the requirement. If the user simply needs Outlook, Office, Teams, OneDrive, SharePoint and web applications, a properly managed laptop may provide everything they need without creating another desktop at all.

If you are assessing IT support providers to help design or manage a cloud desktop or remote-working setup, our UK IT support buyer's guides cover the questions worth asking before you appoint someone.

How to Choose an IT Support Company in Manchester — Buyer's Guide →

How to Choose an IT Support Company in Bristol — Buyer's Guide →

How to Choose an IT Support Company in London — Buyer's Guide →

How to Choose an IT Support Company in Leeds — Buyer's Guide →

How to Choose an IT Support Company in Birmingham — Buyer's Guide →

How to Choose an IT Support Company in Edinburgh — Buyer's Guide →

How to Choose an IT Support Company in Sheffield — Buyer's Guide →

How to Choose an IT Support Company in Glasgow — Buyer's Guide →

How to Choose an IT Support Company in Cardiff — Buyer's Guide →

How to Choose an IT Support Company in Newcastle — Buyer's Guide →

How to Choose an IT Support Company in Nottingham — Buyer's Guide →

Related Questions