Get the newsletter
Microsoft · Security · Filed Mar 20, 2026 · USPTO published Oct 1, 2026 · Oct 1 release

Microsoft Patents a System That Adjusts What You Can Do Remotely Based on Your Device's Condition

When you connect to a company computer from home, Microsoft's new patent wants the system to automatically check what kind of device you're using and how secure it is before deciding how much access you actually get.

A system diagram shows a client device connecting to a virtual computing device in a cloud environment via an authentication service. Drawing from patent filing US 2026/0303584 A1.
A system diagram shows a client device connecting to a virtual computing device in a cloud environment via an authentication service.All 8 drawings ↓
Publication number
US 2026/0303584 A1(US20260303584A1)
Applicant
Microsoft Technology Licensing, LLC
Filed · Published
Mar 20, 2026 · Oct 1, 2026
Inventors
Shilei LIU, Jie LIU, Xiangyi DENG, Na LI, Lavanya KASARABADA, Yizhong WU, Jun SHI
Status when we published
Waiting for an examiner
Document
20 claims
US classification
726/1
Parent application
Continuation of PCT/CN2025/086079 (filed Mar 31, 2025)(PCTCN2025086079)

How Microsoft's cloud desktop lock-down actually works

A worker opens a remote desktop app from a personal laptop late on a Friday. That laptop has no company security software installed, and the session it opens grants full clipboard and file-transfer access to sensitive company data. This is a real, common problem.

Microsoft's patent describes a way to fix that by having the remote session read a "passport" your device picks up during login. That passport describes who you are and what shape your device is in, including whether it meets security requirements. The remote session then decides, on the spot, what you're allowed to do.

So if your device passes all the checks, you might get full access to copy files and redirect USB drives. If you're logging in from a personal or unmanaged machine, the session could automatically block those features, keeping company data from leaking out through your hardware.

From the filing · CLAIM 1
receiving, from a client device, a request to establish a session with a virtual computing device implemented in a cloud computing environment, wherein the request comprises an authentication context received by the client device from an authentication service …

Translation: Your computer asks to connect to a cloud desktop while sending your login details and device health status.

How the authentication context shapes each session's permissions

The system works in three steps, each tied to claim 1 of the patent.

First, when a user tries to connect to a virtual computing device (a cloud-hosted desktop or workstation), the client app bundles an authentication context into the connection request. That context is a data package issued by a separate authentication service (think of it as a security certificate handed out during login) that records the user's account details and the operational state of the device, meaning facts like whether its disk is encrypted, whether a security agent is running, or whether it is managed by the organization.

Second, the cloud environment establishes the remote session normally.

Third, and most importantly, the system reads that context and controls redirection features based on what it finds. Redirection features are the conduits that let a remote session reach back into your local machine, things like clipboard sharing, local printer access, USB device pass-through, and local drive mapping. By tying those conduits to the device's reported security posture, the system can grant or block them without requiring a human administrator to intervene each time.

  • High-trust device: full redirection allowed
  • Partially compliant device: limited clipboard only
  • Unmanaged personal device: all redirection blocked

The claim is broad in that it covers any redirection feature controlled by any aspect of the authentication context, which gives Microsoft wide latitude over how the enforcement logic is actually implemented.

From the filing · THE ABSTRACT
… controlling one or more redirection features of the session based on the authentication context.

Translation: The system decides which files or peripherals you can access based on how secure your computer is.

What this means for remote workers and IT departments

For IT departments, this is a meaningful shift. Today, remote desktop policies are usually set per user group or per virtual machine, a blunt instrument that ignores whether the person connecting is on a locked-down company laptop or an unpatched home computer. A system like this one could make session permissions dynamic, changing automatically based on real-time device state without a helpdesk ticket.

For you as a remote worker, the practical effect could be invisible on a compliant device and restrictive on a personal one. Microsoft has been filing around cloud identity and remote-access security since at least 2023, and this patent fits that pattern: tighter integration between the identity layer and the session layer, so what you're allowed to do follows the security facts on the ground, not a fixed policy set months ago.

Microsoft's 459th filing in our Microsoft coverage since May adds to a security AI thread that includes a three-AI patch system and behavior-based attack detection.

Source: US 2026/0303584 A1 at the USPTO (PDF). Full patent text and figures are in the official publication.

Get our take in your Top Stories

Liked this breakdown? Add Patentlyze as a preferred source on Google, and our plain-English take shows up more often in your Top Stories the next time Microsoft patent news breaks.

There are more where this came from

We read every patent application Big Tech publishes and send you the ones worth knowing. Plain English, free, every week.

The drawings · 8 sheets

8 drawing sheets from US 2026/0303584 A1 · click any drawing to enlarge

Remote access system overview., drawing sheet 1 from US 2026/0303584 A1
Sheet 1 Remote access system overview.
Steps for establishing a remote session., drawing sheet 2 from US 2026/0303584 A1
Sheet 2 Steps for establishing a remote session.
Steps for applying connection policies., drawing sheet 3 from US 2026/0303584 A1
Sheet 3 Steps for applying connection policies.
Steps for applying default restrictions., drawing sheet 4 from US 2026/0303584 A1
Sheet 4 Steps for applying default restrictions.
Steps for updating connection policies., drawing sheet 5 from US 2026/0303584 A1
Sheet 5 Steps for updating connection policies.
Client device authentication and session., drawing sheet 6 from US 2026/0303584 A1
Sheet 6 Client device authentication and session.
Computer system components., drawing sheet 7 from US 2026/0303584 A1
Sheet 7 Computer system components.
Cloud service provider architecture., drawing sheet 8 from US 2026/0303584 A1
Sheet 8 Cloud service provider architecture.
Patent filing page

Reader comments

No comments yet

Start the discussion

Real name or a handle, either is fine. Comments are read by a person before they appear, so allow a little time. Keep it about the filing.