Which work can move from a virtual desktop to the browser
Work done entirely in web apps moves most easily. Decide how files are handled before moving work that uses local files, and keep desktop-app work on VDI.
A virtual desktop (VDI) runs a computer’s desktop on a server and sends the screen to the person’s device. The work that moves off it most easily is work done entirely in web apps, where no file gets opened on the device. Work that opens files in local software can move once you decide how those files are handled. Work that needs installed desktop software stays on the virtual desktop.
Here, “the browser” means using web apps directly in the browser on the person’s own device. Azure Virtual Desktop, Microsoft’s cloud virtual desktop, can also be opened in a browser, but that’s still a virtual desktop.
What a virtual desktop protects
NIST SP 800-46, NIST’s guide to telework and personal-device security, puts virtual desktops in its portal category. The apps and their data sit on the server, which sends the device screen images. So data typically stays on the device far more briefly than when the device runs the apps itself. When a session ends, the virtual desktop is discarded and the next person gets a clean one. NIST says this helps on personal devices, which are less likely to meet a company’s security rules.
Products add finer controls. In Azure Virtual Desktop, an admin decides which of the person’s local resources the remote session can use. Redirection, Microsoft’s term for this, covers the clipboard (whatever you’ve copied), local drives and USB storage, printers and more. Screen capture protection hides the remote desktop in screenshots and screen sharing on supported apps. Microsoft says it isn’t the strong protection of DRM (copy-protection software). Watermarking lays QR codes over the remote desktop. Each code carries the connection’s ID, so if someone photographs the screen, admins can look up which session it was. Whether you can drop the virtual desktop depends on which of these protections each kind of work relies on.
On cost, Microsoft says Azure Virtual Desktop can share one machine among several people. Its autoscale adds or removes capacity as demand changes, so moving people to the browser may let you run fewer machines.
Sort the work into three kinds
Work done entirely in web apps
This is work that happens on a cloud app’s screens, such as entering data or changing settings. NIST calls this direct application access: the browser connects straight to the app, and the app handles its own security. NIST also warns that some of these apps let people download files to the device, and that browser caches can store data by accident. It says all data sent to a remote worker should fall under the organization’s rules for where data may go and how long it’s kept.
Downloads the virtual desktop used to stop now have to be stopped in the app’s own permissions or in the browser. How to block or limit file downloads from SaaS apps covers both.
Work that moves between web apps and local files
An example is exporting a report as a spreadsheet file, editing it in desktop software and importing it back. The file sits on the device for a while. If the spreadsheet work can also happen in a web app, this moves into the first kind. If it needs local software, you have two choices. Accept the file on the device, with rules on where it goes and when it’s deleted, or keep this work on the virtual desktop.
Work that needs installed desktop software
Some work runs in software installed on the computer. Azure Virtual Desktop can host those programs, including line-of-business software built for Windows. If the program has no version that runs in a browser, a browser can’t replace the virtual desktop.
What the browser side can control
Compare each virtual desktop control with what a managed browser offers. Google lists these in its paid Chrome Enterprise Premium. Copy and paste controls stand in for clipboard redirection, download and upload controls for drive redirection, and print controls for printer redirection. It also lists watermarks and screenshot protection.
These controls apply only to use through the managed browser. If someone opens the same app in another browser or on their phone, none of them apply. What is a secure browser (enterprise browser)? explains how these browsers work.
What stays on the computer
On a virtual desktop, the work runs on the server and the device receives the screen. In a browser, the device keeps browsing history, cookies, passwords saved in the browser and downloaded files. Cookies are small files sites save, including the ones that keep you signed in.
Closing the window doesn’t remove files. Chrome’s help says that once every incognito window closes, site data and the list of sites visited are gone, but downloaded files and bookmarks stay. What work data stays on a personal computer, and how to keep it off goes through each item.
Running both
You don’t have to choose one for everything. Move the first kind of work to the browser, keep the third on the virtual desktop, and decide the second task by task.
Checks before you switch off the virtual desktop
-
List the apps and files each job uses
Sort what people open every day into web apps, local files and installed software.
- Why
- Which of the three kinds a job falls into decides whether it can move to the browser.
-
List the virtual desktop controls you have turned on
Note whether clipboard, drive and printer redirection are off, and whether screen capture protection or watermarks are on.
- Why
- You can then check, one by one, whether the browser side has something to replace each.
-
Find services that accept sign-ins only from your network
Sign-in rules such as Microsoft Entra Conditional Access can allow sign-ins only from IP address ranges you name, such as the office’s. Used directly in a browser from home, those services won’t open.
- Why
- On a virtual desktop, the sign-in comes from the virtual desktop’s network, not each person’s home connection, so a rule tied to that network didn’t get in the way.
-
Decide which computers the browser settings must reach
Choose between company computers only, or also Chrome signed in with a company account on personal computers.
- Why
- Google’s help says Chrome policies reach an enrolled browser or a Chrome signed in with a company-managed account. Reaching personal computers means allowing the second.
-
Check who knows each password
For services that use a username and password, find out whether staff know the password.
- Why
- Someone who knows the password can sign in from another device, outside the managed browser.
-
Try it with one team first
Move one job of the first kind and see whether anything can’t be done in the browser.
- Why
- Moving one job first shows whether anything needs the virtual desktop before everyone depends on the browser.
Frequently asked questions
Will dropping the virtual desktop save money?
It can for a cloud virtual desktop. Azure Virtual Desktop's autoscale raises or lowers capacity with demand, so moving people off it may let you run fewer machines.
What stays on the computer when people use web apps directly?
Browsing history, cookies, passwords saved in the browser and downloaded files. Chrome's incognito window clears site data and history when every incognito window closes, but its help says downloaded files stay.
Can a browser also stop screenshots?
Some managed browsers can. Google lists screenshot protection and watermarks in the paid Chrome Enterprise Premium. They apply only when people use the managed browser.
What about work that needs installed desktop software?
Keep it on the virtual desktop. If the software has no version that runs in a browser, no browser setup can stand in for it.
How Junify handles this
- Doing this by hand
- Single sign-on and multi-factor authentication don't reach apps that can't connect to your identity provider, or accounts that stay shared. Those are left to manual work, and you have to track for yourself which accounts the tools cover.
- With Junify
- Once people reach web apps directly instead of through a virtual desktop, anyone who knows a shared account's password can sign in from any device. Change the password when you add the account to Junify. Only Junify holds it, and Junify signs people in without showing it. So you no longer change and resend it whenever someone leaves. Downloads can be blocked per account, and each use is recorded by person.
Sources
- NIST SP 800-46 Rev. 2: Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security (July 2016)
- Microsoft Learn: What is Azure Virtual Desktop?
- Microsoft Learn: Peripheral and resource redirection over the Remote Desktop Protocol
- Microsoft Learn: Screen capture protection in Azure Virtual Desktop
- Microsoft Learn: Watermarking in Azure Virtual Desktop
- Chrome Enterprise and Education Help: Set Chrome policies for users or browsers
- Google: Chrome Enterprise Premium
- Google Chrome Help: Browse in Incognito mode
- Microsoft Learn: Microsoft Entra Conditional Access
-
What's the difference between an audit log and audit evidence?
An audit log is what a system records. Audit evidence is a log you can rely on: tied to a person, protected from change, kept for a set period, and reviewed.
-
What a browser extension can and can't control in access management
An extension works inside the browser it's installed in, on the sites it's allowed to run on. Other apps, other browsers and other devices are out of its reach.
-
What work data stays on a personal computer, and how to keep it off
History, cookies, saved passwords, password manager copies and downloads. Pair company browser settings with logins that don't show people the password.